Contents

Popular
 Contents

There could be changes in the runtimedata structure from one release to another or in the content of the essential files used by servers. So, Runtimedata Migration is essential whenever there is a need to migrate from a previous installation to the new one.

The three types of migration explained in this section are:


Migrating Standalone Profile Runtimedata

Preliminary Steps

Ensure that the below exercise is completed before you start with executable steps:

  1. Stop all running  Event Processes and Fiorano servers in the old installer.

  2. Clear runtimedata of the new Installation present in the $NEW_FIORANO_HOME directory. If required, take a backup of the runtimedata.

    Icon

    This step is mandatory, not following which may lead to the following problems:

    • The MQ database of the ESB and Peer server may get corrupted.
    • The repository will be overwritten. So, any Event Process with the same name gets overwritten.

Executable Steps

Step 1: Set the required parameters in RunTimeDataMigration.properties file

To migrate a runtimedata from previous version to the new Fiorano installation, you have to first configure the RunTimeDataMigration properties file. Hence, perform the following actions before running the utility:

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



  2. Open the RunTimeDataMigration.properties file and provide values for the below properties in the file:
    1. FIORANO_HOME: 
    2. OLD_INSTALLER_BUILD
    3. NEW_ESTUDIO_WORKSPACE
    4. OLD_ESTUDIO_WORKSPACE
    Icon

    The values entered for these parameters are case sensitive.


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

PropertyDescription
OLD_FIORANO_HOME

Path to old Fiorano Installer from which runtimedata is being migrated.

Example
OLD_INSTALLER_BUILD

Provide the installer Build number of the previous installation from which runtimendata is being migrated

Icon

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.

Example
NEW_ESTUDIO_WORKSPACE

Path to the new eStudio workspace; location to which eStudio data is to be migrated.

Example
OLD_ESTUDIO_WORKSPACE

Path to the old eStudio workspace. Location from which eStudio data is to be migrated.

Example

Step 2: Execute the Migration Script

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

Windows
Linux

The runtimedata containing the migrated data will be present in the new installation.

Icon

API runtimedata (if present) will get migrated with the above-mentioned process.

Migrating Shared HA Profile Runtimedata

For migrating Shared HA Profile Runtimedata, follow the same steps as illustrated in the Migrating Standalone Profile Runtimedata section, but provide the following values too in the RunTimeDataMigration.properties file:

  • EXISTING_SHARED_HA_FES_DATABASES
  • EXISTING_SHARED_HA_FPS_DATABASES

Descriptions for the parameters in the RunTimeDataMigration properties file are in the table below.

PropertyDescription
EXISTING_SHARED_HA_FES_DATABASES

Path to the SHARED HA FES Database(s).

Icon

Multiple entries can be made separated bycomma(s) in case there are more than one shared HA database folder.

Example
Icon

For the above example, Shared HA FES database for the new installer will be:

    • C:/DBFPS1_${NEW_INSTALLER_BUILD}
    • C:/DBFPS2_${NEW_INSTALLER_BUILD}
EXISTING_SHARED_HA_FPS_DATABASES

Path to the SHARED HA FPS Database(s).

Icon

Multiple entries can be made separated by comma(s) in case there are more than one shared HA database folder.

Example
Icon

For the above example, Shared HA FES database for the new installer will be:

    • C:/DBFPS1_${NEW_INSTALLER_BUILD}
    • C:/DBFPS2_${NEW_INSTALLER_BUILD}

Migrating Runtimedata from Replicated HA profiles to Shared HA

This migration is used when user wants to use Replicated HA profile Runtimedata for Shared HA profiles.

For migrating Shared HA Profile Runtimedata, follow the same steps as illustrated in the Migrating Standalone Profile Runtimedata section, but provide the following values too in the RunTimeDataMigration.properties file:

  • REPLICATED_HA_FES_PROFILES
  • REPLICATED_HA_FPS_PROFILES
  • SHARED_HA_FES_DATABASE
  • SHARED_HA_FPS_DATABASE

Descriptions for the parameters in the RunTimeDataMigration properties file are in the table below.

PropertyDescription
REPLICATED_HA_FES_PROFILES

Replicated FES HA profile for which Shared HA Database to be created.

Icon
  • Multiple entries can be made separated by comma(s) in case there are more than one shared HA database folder.
  • Specify either Primary or Secondary. As both primary and secondary databases are in sync at all time, it won't matter as to which database is copied.
Example
REPLICATED_HA_FPS_PROFILES

Replicated FPS HA profile for which Shared HA Database to be created.

Icon
  • Multiple entries can be made separated by comma(s) in case there are more than one shared HA database folder.
  • Specify either Primary or Secondary. As both primary and secondary databases are in sync at all time, it won't matter as to which database is copied.
Example
SHARED_HA_FES_DATABASE

Path to SHARED HA FES Database.

Example
SHARED_HA_FPS_DATABASE

Path to SHARED HA FPS Database.

Example

The runtimedata containing the migrated data will be present in the new installation.

Post Migration Activities

After Migration, perform the following actions to ensure and confirm a proper migration:

  • 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)
Icon

For Cassandra Server Traffic data Migration, refer to the Cassandra Migration section.

Adaptavist ThemeBuilder EngineAtlassian Confluence