Contents

Popular

Overview

Migration can be executed from any one of the following installations to the latest one:

  • Fiorano 2007 SP7
  • Fiorano 2007 SP7 Update1
  • Fiorano 9.0.0
  • Fiorano 9.0.1
  • Fiorano 9.0.2
  • Fiorano 9.1.0
  • Fiorano 9.1.1
  • Fiorano 9.2.0
  • Fiorano 9.2.1
  • Fiorano 9.2.2
  • Fiorano 9.3.0
  • Fiorano 9.4.0
  • Fiorano 9.4.1
  • Fiorano 9.4.2
  • Fiorano 9.5.0
  • Fiorano 9.5.1
  • Fiorano 10.0.0
  • Fiorano 10.1.0
  • Fiorano 10.2.0
  • Fiorano 10.3.0
  • Fiorano 10.3.1
  • Fiorano 10.3.2
  • Fiorano 10.3.3
  • Fiorano 10.4.0
  • Fiorano 11.0.0
  • Fiorano 12.0.0
  • Fiorano 12.1.0

The migration steps need to be performed soon after installing the latest Fiorano version.

Icon

To migrate from other versions of Fiorano Platform to the latest version, please send an email to presales@fiorano.com.

Icon
  • Please make sure that all the servers and tools are stopped before performing the migration.
  • JAVA_HOME needs to be specified in $FIORANO_HOME/fiorano_vars.sh/bat or globally under environment variables for the utility to work
Icon

For API Management migration, refer to the Migrating from an older version section present in the API Management documentation.

 Types of Migration

Migrating the entire Fiorano environment 

After Installation of the Fiorano latest version, to migrate the whole Fiorano environment to a newer version, the below-listed migrations need to be performed:

  • Profile Migration: To copy the changes made to profiles or files used by servers from the older to the newer version of Fiorano.
  • Runtimedata Migration: To copy the changes made to runtimedata or files used by servers from the older to the newer version.
  • Scripts Migration: To copy the edited script or configuration files from the older version to the newer one.
  • Component Resources Migration: To copy the changes made to the microservices and resources of the prebuilt microservices.
Icon

Each migration is explained in detail in the following sections.

Migrating a specific Fiorano server

To carryout migration on FES/FPS/eStudio server, all four migrations mentioned above need not be performed. The below list describes the migration required for the respective server.

Server on which the script is runMigration type required
FES / HA FES (Active)
  • Profile Migration
  • Runtimedata Migration
  • Scripts Migration
  • Component Resources Migration
FPS / HA FPS (Active)
  • Profile Migration
  • Runtimedata Migration
  • Scripts Migration
HA FES (Passive)
  • Profile Migration
  • Scripts Migration
HA FPS (Passive)
  • Profile Migration
  • Scripts Migration
eStudio
  • Runtimedata Migration

Modes of Migration

Migration can be performed in the following ways:

  • Non-interactive mode
  • Interactive mode

Non-interactive Mode

This mode carries out migration individually by configuring various property files. Refer to the respective section from the below as per the migration requirement:

Interactive Mode

The Interactive mode works on a command line interface (console or command prompt). This console prompts for user inputs based on which migrations get executed.

To perform the migration using interactive mode,

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

    Windows
    Linux

  2. The script will run in the console mode, prompting for user inputs. Provide the values by carefully following the interactive prompts.

    Icon

    The values that have to be provided will be the same as provided in the Properties files while performing the non-interactive mode. Hence refer to the Non-interactive Mode section above for the same.

Adaptavist ThemeBuilder EngineAtlassian Confluence