Migration from AI Suite 2.1.0 to Datastore 2.3.0

This section explains how to migrate an AI Suite 2.1.0 installation to Datastore 2.3.0, keeping all the data, queries, and all non-history entries preferences.

Caution   Before migrating AI Suite 2.1.0, you must migrate PassPort to version 4.6.0 SP12.

The following graphic is an overview of the process:

Migration AI-Suite 2.1 to Datastore 2.3

There are two methods to migrate your Datastore products:

  • Installing the 2.3.0 version into a new folder.
  • Replacing the existing installation with the 2.3.0 version (UNIX / Linux only).


The AI Suite version must be 2.1.0 with the latest service pack applied.

Make sure you use an Oracle database.

Back-up all database schemas.

Make sure you have online databases.

Perform the following actions before you migrate:

  1. Back up the AI Suite 2.1.0 databases. The migration will update the Datastore Runtime database to the new structure.
  2. Update Datastore Runtime database user permissions: Add create sequence permission to the database user DSVIEW
  3. If InterPlay is installed in the same repository, the configuration versions need to synchronize. Deploy the configuration from the Designer to InterPlay and Datastore.
  4. Export the project's configuration from Designer. If the button Export project is available go to the next step, otherwise, run the following commands in [Install_path_2.1.0]/AISuite/Repository/startConsole:
    • cleanDesigner
    • setupDesigner
    • updateComponent AISuiteDesigner
  5. Click Export project.
    • Each application should be exported in a corresponding folder.
    • Common application names are default and interaction.
  6. Retrieve the runtime application name and version for Datastore Runtime:
    1. Start the Repository console in [Install_path_2.1.0]/AISuite/Repository/startConsole.
    2. Run the following command: listRegistry
    3. Note the runtimeApplicationName and runtimeVersion of the component AISuiteDatastoreRuntime that will be used during migration. For example: application: default and version: 8.
  7. Export preferences, queries, report templates and registry.xml:
    Ensure that the [Install_path_2.1.0]/AISuite/Repository/extra/export folder exists and is empty. Use this folder as value for [exportFolder] in the steps below.
    1. Start the Repository console in [Install_path_2.1.0]/AISuite/Repository/startConsole
    2. Run the following command: exportRegistry [exportFolder]
    3. Run the following command: exportReportTemplates [exportFolder]
    4. Run the following command: exportPreferences [exportFolder]
    5. Run the following command: exportQueries -f[exportFolder]/[queryFile] -c [component_name]
    6. Note: The default component name is AISuiteDatastoreClient.
  8. Make sure that the queries have been correctly exported:
    • Start the Datastore Client Tools console in: [Install_path_2.1.0]/AISuite/DatastoreClient/extra/client-tools/startConsole
    • Run the command clean.


In Datastore Client, the history of queries is not kept during migration.

Perform the migration

To migrate AI Suite 2.1.0 to Datastore 2.3.0:

  1. Stop all the products in AI Suite 2.1.0.
  2. The database must be running.
  3. Make a Datastore 2.3.0 installation. You have two options:
    • In UNIX only, you can reuse 2.1.0 folders, rename the folders and install the product in the previous folder.
    • Install Datastore 2.3.0 in a new folder.
  4. Use  new database schemas for all components except Datastore Runtime, choosing the same component names as the ones from the AI Suite 2.1.0 installation.
  5. Use the Verify database configuration option from the Installer.
  6. Perform the Datastore Runtime 2.3.0 installation using:
    • The AI Suite 2.1.0 schemas.
    • no value as DATA tablespaces (default user tablespace is used as DATA tablespace)
    • 2.1.0 INDEX tablespaces as INDEX tablespaces
    • 2.1.0 LOB tablespaces as LOB tablespaces
  7. When configuring the new components, make sure that they have the same component names as the ones from the 2.1.0 installation.
  8. Update the installation with the latest service pack.
  9. Start the application server.
  10. Migrate the Designer configuration from 2.1.0 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.1 folder exists and is empty.
    2. Ensure that the [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.2 folder exists and is empty.
    3. Ensure that the [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.3 folder exists and is empty.
    4. Copy and unzip the Designer configuration that you exported in Prerequisites to [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.1.
    5. Run the command [Install_path_2.3.0]/AIS/Designer/extra/Tools/ant migrateConfiguration -DPrefix=MigrateToPreviousVersion
    6. Run the command [Install_path_2.3.0]/AIS/Designer/extra/Tools/ant migrateConfiguration
    7. Compress the configuration in a zip file.
    8. Import and deploy the configuration from [Install_path_2.3.0]/AIS/Designer/extra/work/
      on the current application with the option Repository only checked.
  11. Migrate the Repository exported from AI Suite 2.1.0 to Datastore 2.3.0:
    1. Specify the preferences to be migrated from 2.1.0 to 2.2.1. To do this, configure the file [Install_path_2.3.0]/AIS/Repository/extra/migration/migrateTo_221/migration.xml.
    2. This file must contain:
      • The full path of the query file exported from 2.1.0.
      • The full path of the preference file exported from 2.1.0.
      • A temporary folder that will contain temporary query and preference files.
    3. Sample XML file for a default application:
    4. <?xml version="1.0" encoding="UTF-8"?>








    5. Specify the applications, queries and registry to be migrated from 2.1.0 to 2.3.0. To do this, configure the file [Install_path_2.3.0]/AIS/Repository/extra/migration/migrateTo_230/migration.xml.
    6. This file must contain:
      • The Datastore Runtime 2.1.0 application name and version in order to force the same version in the new installation.
      • The full path of the temporary query file created in step 6a.
      • The folder of the registry file exported from 2.1.0.
      • The full path of the temporary preference file created in step 6a.
      • Note: Use [Install_path_2.3.0]/AIS/Repository/extra/import as value for [importFolder].
    7. Sample XML file for a default application:
    8. <?xml version="1.0" encoding="UTF-8"?>


























    9. Start the console in [Install_path_2.3.0]/AIS/Repository/startConsole and run the following command: migrate -from 2.1.0.
    10. Type the command in the console rather than copying-pasting from this document. Use the standard hyphen character on your keyboard. This command sets the specific application and version used by Datastore Runtime, migrates the applications, queries, registry and preferences, and automatically imports them in the new installation.
    11. Import the report templates using the command importReportTemplates [exportFolder]
  12. Update the configuration in Designer:
    1. Update the Import Reader of the Collection Type AUDIT_COLLECTION as follows:
      • Type: FixedFlatFile
      • Name: AccountingIntegratorReader
      • Statistic Reader: AccountingIntegratorStatReader
      • Single Line: Yes
      • Input/output Event name: {
    2. Deploy the configuration from Designer to Datastore Runtime
  13. Verify that the migrated queries exist and can be executed on the 2.3.0 installation, and that the migrated preferences also work as expected.
  14. Copy the settings customizations from the 2.1.0 datastoreConfiguration.properties file into the 2.3.0 component.
  15. Note: You can use the following dstools command to get all the default settings: dstools setting list
  16. If the 2.1.0 installation was done with PassPort, update the users. The role product names have changed. The products now have the prefix AIS instead of AISuite. For example: AISuiteDesigner in 2.1.0 has changed to AISDesigner in 2.3.0.
  17. Note: It is not possible to deploy a property type that is defined as inherited and audited. Set the Audit criterion to YES to deploy without error.


Related Links