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 previous installation to new installation.
The two types of migration explained in this section are:
Migrating Standalone Profile
Follow the steps in the below sections to carryout migration individually by configuring the corresponding property files.
Migration Steps
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:
- OLD_FIORANO_HOME
- OLD_INSTALLER_BUILD
- PROFILES_FILES
Descriptions for the parameters in the Profile Migration properties file are in the table below.
| Property | Description |
|---|---|
| OLD_FIORANO_HOME | Path to old Fiorano Installer from which profiles are being migrated. Example |
| OLD_INSTALLER_BUILD | Provide the installer Build number of the previous installation from which profiles are being migrated Example |
| 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. Example |
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):
| Property | Description |
|---|---|
| OldProfilesDir | Specify old value for Fiorano profiles directory here. Example |
| OldProfileName | Specify Fiorano profile name to be migrated. Example |
| ProfileMode | Specify mode of the old profile. Example |
| ProfileType | Specify typeof the old profile. Example |
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.
During Migration
The legal values for profile types are HARplPrimary, HARplSecondary,HASharedPrimary, and HASharedSecondary in place of 'Standalone'.
After Migration
Configure HA server profiles to specify ‘BackupRMIServerPort’, ‘LockFile’ and ‘GatewayServerIPAddress’ (if not already specified).