- Steps to execute Profile Migration
- How does the utility work?
- SBW Migration
There could be changes in the profile structure from one release to another or in the content of the essential files used by servers. So, Profile Migration is essential whenever there is a need to migrate the profiles configured in the previous installation to new installation.
Steps to execute Profile Migration
The two types of Profile migrations are:
Migrating Standalone Profile
Follow the steps in the below sections to carry out migration individually by configuring the corresponding property files.
Step 1: Set the required parameters in ProfileMigration.properties file
Before running the utility, perform the following actions:
- Go to the location $FIORANO_HOME/esb/FioranoMigration/bin/ to find the ProfileMigration.properties file.
Open the ProfileMigration.properties file from the location and provide values for the below properties in the Profile Migration properties file:
Descriptions for the parameters in the Profile Migration properties file are in the table below.
Path to old Fiorano Installer from which profiles are being migrated.
Provide the installer Build number of the previous installation from which profiles are being migrated
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.
Configuring .lst files for Profile_Files property
Read the following to know how to create Profile.lst:
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_HOMEesb\FioranoMigration\bin):
Specify old value for Fiorano profiles directory here.
Specify Fiorano profile name to be migrated.
Specify mode of the old profile.
Specify type of the old profile.
Step 2: Execute the Migration Script
Open console from the location $FIORANO_HOME/esb/FioranoMigration/bin and execute the following script:
Post Migration Activities
After Migration, perform the following actions to ensure and confirm a proper migration:
- If the password for admin user is changed in previous versions, after FES profile migration, the password needs to be changed in the FES profile by navigating through the following nodes using Profile Manager perspective in eStudio:
FES > Fiorano > ESB > Transport > FESTransportManager > MQProvider
- Add the latest license to the license folder present at Fiorano_Home
- After running the servers, there should not be any errors on the server console and server status should be shown in the Server Status Tab of the Dashboard (Fiorano Web Console)
Migrating HA profiles
To migrate the previous installation’s HA server profiles to the new Fiorano version, follow the same procedure as explained above for Standalone Migration, except for the following changes.
The legal values for profile types are "HARplPrimary" for Primary Replicated HA profile, "HARplSecondary" for Secondary Replicated HA profile, "HASharedPrimary" for primary Shared HA profile, and "HASharedSecondary" for Secondary Shared HA profile in place of "Standalone".
Configure HA server profiles to specify ‘BackupRMIServerPort’, ‘LockFile’ and ‘GatewayServerIPAddress’ (if not already specified).
How does the utility work?
While migrating the profile, the utility performs 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, following files will be over-written:
$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 old profile to the corresponding file in duplicated profile. According to the example values considered above in point 1, 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 across versions, the same must be changed in the respective .conf file.