Migration from InterPlay 2.2.1 to InterPlay 2.3.0

This section explains how to migrate an InterPlay 2.2.1 installation to InterPlay 2.3.0, keeping all the data and preferences.

Caution   Before migrating InterPlay 2.2.1, you must migrate PassPort to version 4.6.0 SP12.

The following graphic is an overview of the process:

InterPlay 2.2.1 to 2.3 migration


The InterPlay version must be 2.2.1, with any SP installed.

Make sure you perform the following actions before you migrate:

  1. Back up the InterPlay 2.2.1 database. The migration will update the databases to the new structure.
  2. Deploy the configuration from the Designer to the Repository and InterPlay if the installation contains Datastore. InterPlay and Datastore must have the same application version because the application will be migrated.
  3. Export the project's configuration from Designer 2.2.1 by clicking Export project.
    • Each application should be exported in a corresponding folder.
    • Common application names are default and interaction.
  4. Retrieve the runtime application name and version for InterPlay 2.2.1:
    1. Start the Repository console in [Install_path_2.2.1]/AIS/Repository/startConsole.
    2. Run the following command: listRegistry
    3. Note the runtimeApplicationName and runtimeVersion for InterPlay.
  5. Export preferences, report templates and registry.xml:
    Use [Install_path_2.2.1]/AIS/Repository/extra/export as value for [exportFolder] in the steps below.
    1. Start the Repository console in [Install_path_2.2.1]/AIS/Repository/startConsole
    2. Run the following command: exportRegistry [exportFolder]
    3. Run the following command: exportReportTemplates [exportFolder]
    4. Run the following command: exportPreferences [exportFolder]
  6. You should check all your exits. There might be changes in the API.

Perform the migration

To migrate InterPlay 2.2.1 to InterPlay 2.3.0:

  1. Stop all the products in AI Suite 2.2.1.
  2. The database must be running.
  3. Make an InterPlay 2.3.0 installation in a new folder and new database schemas for all components exceptInterPlay, choosing the same component names as the ones from 2.2.1.
    • Perform the InterPlay 2.3.0 installation using the InterPlay 2.2.1 schema.
    • When configuring the new components, make sure that they have the same component names as the ones from the 2.2.1 installation.
    • When performing the 2.3.0 installation, select the Migrate from 2.2.1 option for the component, and use 2.2.1 schemas.
  4. Migrate the Designer configuration from 2.2.1 to 2.3.0 as described in this step.
    There are several application names (such as default and interaction) and each has its own configuration. Follow this procedure for each application configuration:
    1. Ensure that the [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.2 folder exists and is empty.
    2. Ensure that the [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.3 folder exists and is empty.
    3. Copy the Designer configuration that you exported in Prerequisites to [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.2.
    4. Run the command [Install_path_2.3.0]/AIS/Designer/extra/Tools/ant migrateConfiguration
    5. Import the migrated configuration from [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.3 into Designer.
  5. Deploy the configuration from Designer to Repository without cleaning.
  6. Migrate the Repository exported from InterPlay 2.2.1 to InterPlay 2.3.0:
    1. Specify the applications to be migrated from 2.2.1 to 2.3.0. To do this, configure the file [Install_path_2.3.0]/AIS/Repository/extra/migration/migrateTo_230/migration.xml.
    2. This file must contain the 2.2.1 application name and version in order to force the same version in the new installation.
    3. Sample XML file for a default application:
    4. <?xml version="1.0" encoding="UTF-8"?>















    5. Start the Repository console in [Install_path_2.3.0]/AIS/Repository/startConsole
    6. Run the following command: migrate -from 2.2.1.
  7. Import the exported report templates into Repository 2.3.0 using the command importReportTemplates [exportFolder]
  8. Import the exported preferences into Repository 2.3.0 using the command importPreferences [exportFolder]


Related Links