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.

Migration of changed credentials


In case usernames and passwords used to run the profile have been changed in profile configurations for the previous release installer, it is mandatory to migrate the entire runtimedata as well. In case runtimedata is not migrated for the server, the profile will be using a set of user credentials that are not present in the new installer and hence will not work unless the credentials are reset back to default in the profile configurations.

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.

Migration Steps


Ensure that you have closed the Fiorano Servers.

Step 1: Set the required parameters in file

Before running the utility, perform the following actions:

  1. Go to the location $FIORANO_HOME/esb/FioranoMigration/bin/ to find the file.

  2. Open the file from the location and provide values for the below properties in the Profile Migration properties file:



    The values entered for these parameters are case sensitive.

Descriptions for the parameters in the Profile Migration properties file are in the table below.


The 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


It is important to provide correct build number of the installer as the set of changes done to Configs.xml file (to make it compatible with current version) depend on this value.


Check OLD_FIORANO_HOME\ for the build number.


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.


Refer to the section below to know how to create Profile.lstfiles.

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_HOME\esb\FioranoMigration\bin):


Specify the old value for Fiorano profiles directory here.


Specify Fiorano profile name to be migrated.


Specify mode of the old profile.

Legal Value




Specify the type of the old profile.


Legal value for the standalone type of server is 'Standalone'.



Step 2: Execute the Migration Script

Open console from the location $FIORANO_HOME/esb/FioranoMigration/bin and execute the following script:


API profiles can also be migrated using the above-mentioned process. Refer to the Profile Migration section for details.

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" 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".

After Migration

Configure HA server profiles to specify ‘BackupRMIServerPort’, ‘LockFile’ and ‘GatewayServerIPAddress’ (if not already specified).


Please note that GatewayServerIPAddress should be the address of the machine holding the lock file and BackupRMIServerPort is the RMI port of back up HA server.

How does the utility work?

While migrating the profile, the utility performs the following operations for each profile being migrated:

  1. 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.
  2. 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 overwritten:
    • $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

  3. 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.
  4. 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.

SBW Migration

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.


While migrating Replicated HA runtimedata from the lower versions of 9.1.0 (Build #9190) to Shared HA in the latest version, Shared HA FES has to be started with Apache Derby server as these lower versions will be using Apache Derby DB. Please update ‘sbwdb.cfg’ file of shared enterprise server accordingly before starting the servers.

Adaptavist ThemeBuilder EngineAtlassian Confluence