Contents

Popular

Versions Compared

Old Version 2

changes.mady.by.user Prathewraj M

Saved on

compared with

New Version 3

changes.mady.by.user Prathewraj M

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Runtimedata Migration Procedure

Expand
titleContents

Table of Contents
indent15px
stylenone

Anchor
Migrating Standalone Profile Runtimedata
Migrating Standalone Profile Runtimedata
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.

    Warning
    titleCaution

    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 runtimedata from previous version to the new Fiorano installation, you have to first configure the build.properties file in $NEW_FIORANO_HOME/migration/runtimedatamigration directory (The file is self explanatory, please follow the instructions given in file carefully).
You can do following kind of migrations by configuring build.properties file:

  • Migration of standalone profiles runtimedata.
  • Migration of replicated profiles runtimedata.
  • Migration of sharedHA profile runtimedata.
  • Migration of replicated HA profiles to Shared HA profiles.

After configuration, run one of the following script present in the directory $NEW_FIORANO_HOME/migration/runtimedatamigration

  • migration.sh for UNIX environment
  • migrate.bat for Windows environment

The script will migrate runtime data from previous version to the new Fiorano installation and take care of cleaning unnecessary and unwanted data from $NEW_FIORANO_HOME/runtimedata directory.

...

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.

    Image Added

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

    The values entered for these parameters are case sensitive.


    Image Added

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

PropertyDescription
OLD_FIORANO_HOME

Path to old Fiorano Installer from which profiles are being migrated.

Code Block
titleExample
FIORANO_HOME=C:/Fiorano/Fiorano10.3.1
OLD_INSTALLER_BUILD

Provide the installer Build number of the previous installation from which profiles are being migrated

Info

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.

Code Block
titleExample
OLD_INSTALLER_BUILD=10350
NEW_ESTUDIO_WORKSPACE

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

Code Block
titleExample
NEW_ESTUDIO_WORKSPACE=C:\Fiorano\10.3.3\runtimedata\eStudio\workspace
OLD_ESTUDIO_WORKSPACE

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

Code Block
titleExample
OLD_ESTUDIO_WORKSPACE=C:\Fiorano\10.3.1\runtimedata\eStudio\workspace

Step 2: Execute the Migration Script

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

Code Block
titleWindows
migration.bat -runtimedata
Code Block
titleLinux
migration.sh -runtimedata

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

Tip

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

Warning
titleCaution

Please stop all running Event Processes and Fiorano servers in the old installer before migration. Also delete runtimedata (if already exists) from $NEW_FIORANO_HOME before running migration scripts otherwise it may result in some inconsistencies.

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

Image Added

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

PropertyDescription
EXISTING_SHARED_HA_FES_DATABASES

Path to the SHARED HA FES Database(s).

Tip

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

Code Block
titleExample
EXISTING_SHARED_HA_FES_DATABASES=C:/DBFES1,C:/DBFES2
Info

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

Tip

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

Code Block
titleExample
EXISTING_SHARED_HA_FPS_DATABASES=C:/DBFPS1,C:/DBFPS2
Info

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

Image Added

 

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

PropertyDescription
REPLICATED_HA_FES_PROFILES

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

Tip
  • 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.
Code Block
titleExample
REPLICATED_HA_FES_PROFILES=haprofile1/primary
REPLICATED_HA_FPS_PROFILES

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

Tip
  • 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.
Code Block
titleExample
REPLICATED_HA_FPS_PROFILES=haprofile1/primary
SHARED_HA_FES_DATABASE

Path to SHARED HA FES Database.

Code Block
titleExample
#SHARED_HA_FES_DATABASE=C:/DBFES
SHARED_HA_FPS_DATABASE

Path to SHARED HA FPS Database.

Code Block
titleExample
#SHARED_HA_FPS_DATABASE=C:/DBFPS
Adaptavist ThemeBuilder EngineAtlassian Confluence