...
Descriptions for the parameters in the Profile Migration properties file are in the table below.
| Property | Description | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| OLD_FIORANO_HOME | Path The path to old Fiorano Installer from which profiles are being migrated.
| |||||||||
| OLD_INSTALLER_BUILD | Provide the installer Build number of the previous installation from which profiles are being migrated
| |||||||||
| PROFILES_FILES | Provide the names of .lst files* in CSV format with each of the file containing the required properties representing the respective profile to be migrated.
|
...
For each profile to be migrated, create a new .lst providing the following parameter values (replicate the profile1.lst file at the location $NEW_FIORANO_HOMEesbHOM\Eesb\FioranoMigration\bin):
| Property | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| OldProfilesDir | Specify the old value for Fiorano profiles directory here.
| ||||||||||
| OldProfileName | Specify Fiorano profile name to be migrated.
| ||||||||||
| ProfileMode | Specify mode of the old profile.
| ||||||||||
| ProfileType | Specify the type of the old profile.
|
...
While migrating the profile, the utility performs the following operations for each profile being migrated:
- Makes a duplicate copy of the corresponding profile in this installation. The profile to be duplicated is determined by the parameters 'ProfileType', 'ProfileMode' and 'OldProfileName' as specified in sampleprofile.lst file.
Example: If ProfileType=HARplPrimary, ProfileMode=FES and OldProfileName=testprofile/pri, then the directory $NEW_FIORANO_HOME/esb/servers/profiles/haprofile1/primary/FES will be duplicated as $NEW_FIORANO_HOME/esb/servers/profiles/testprofile/pri/FES. - Over-writes the configuration files ('Configs.xml' & *.cfg files present in conf directory of the profile) from the old profile present in old installation to the duplicated profile. According to the example values considered above in point 1, the following files will be over-writtenoverwritten:
$OldProfilesDir/testprofile/pri/FES/conf/Configs.xml will overwrite $NEW_FIORANO_HOME /esb/servers/profiles/testprofile/pri/FES/conf/Configs.xml
$OldProfilesDir/testprofile/pri/FES/conf/*.cfg will overwrite $NEW_FIORANO_HOME /esb/servers/profiles/testprofile/pri/FES/conf/*.cfg
- Overwrites the value of the 'name' attribute as present in $OldProfileHome/$OldProfileName/$ProfileMode/profile.xml from the old profile to the corresponding file in duplicated profile. According to the example values considered above in point 1, the following operation will be performed:
- Reads the value of 'name' attribute from $OldProfileHome/testprofile/pri/FES/profile.xml and over-write the value in $NEW_FIORANO_HOME /esb/servers/profiles/testprofile/pri/FES/profile.xml.
- Implements changes in configs.xml at $NEW_FIORANO_HOME /esb/servers/profiles/testprofile/pri/FES/conf/Configs.xml to make the old configurations compatible with the new version.
...
If an external database is being used for document tracking, the configuration would be migrated as part of the FES profile migration. However, any jars that have been added to the server classpath in server.conf or fes.conf files should be placed in the appropriate location, Script Migration after the profile migration will handle the jar addition to the .conf files. If there is any change in the jdbc jar the JDBC jar across versions, the same must be changed in the respective .conf file.
...