Contents

Popular

Versions Compared

Key

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

...

  1. Stop all running API projects 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

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

    • The MQ database of the AMS and AGS server may get corrupted.
    • The repository will be overwritten. So, any API Projects with the same name gets overwritten.
Info
titleHA Migration

 

 

 

Warning
titleNote

Not letting the previously active HA server profiles to reach the standalone state will lead to loss of:

  • user/group information, repository content (including but not limited to API projects, policies, notifications, reports, etc.) on HA AMS setup.
  • pending analytics data and user-defined custom queues/topics on HA AGS setup.

 

Passive servers do not need runtimedata migration because the start of the passive server after the active server reaching standalone state will synchronise the entire data from the active to the passive server. Even if data from passive servers get migrated due to the data's presence in the same runtimedata as that of the active server, there won't be any issue as this data gets overwritten with the data from the active server once the passive server is started after the previously active server is in the standalone state.

 

Executable Steps

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

...

Adaptavist ThemeBuilder EngineAtlassian Confluence