Migration from Datastore 2.2.1 to Datastore 2.3.0

This section explains how to migrate a Datastore 2.2.1 installation to Datastore 2.3.0, keeping all the data, queries, registry, report templates, and all non-history entries preferences.

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

The following graphic is an overview of the process:

Datastore 2.2.1 to 2.3 migration


The Datastore version must be 2.2.1 with the latest service pack applied.

Make sure you are using 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 Datastore 2.3.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 2.2.1 by clicking Export project.
    • Each application should be exported in a corresponding folder.
    • Common application names are default and interaction.
  5. Retrieve the runtime application name and version for Datastore Runtime:
    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 of the component DatastoreRuntime that will be used during migration. For example: application: default and version: 8.
  6. Export preferences, queries, report templates and registry.xml:
    Ensure that the [Install_path_2.2.1]/AIS/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.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]
    5. Run the following command: exportQueries -f [exportFolder]/[queryFile] -c [component_name]
    6. Note: The default component name is DatastoreClient.
  7. Ensure that the queries have been correctly exported:
    1. Start the Datastore Client Tools console in [Install_path_2.2.1]/Datastore/DatastoreClient/extra/client-tools/startConsole.
    2. Run the command: clean.


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

Perform the migration

To migrate Datastore 2.2.1 to Datastore 2.3.0:

  1. Stop all the products in Datastore 2.2.1.
  2. The database must be running.
  3. Make a Datastore 2.3.0 installation in a new folder and new database schemas for all components except Datastore Runtime, choosing the same component names as the ones from the Datastore 2.2.1 installation.
    • You must use the Verify database configuration installer option.
    • Perform the Datastore Runtime 2.3.0 installation using:
      • the Select tools and Database option
      • the Datastore Runtime 2.2.1 schemas
      • no value as DATA tablespaces (default user tablespace is used as DATA tablespace)
      • 2.2.1 INDEX tablespaces as INDEX tablespaces
      • 2.2.1 LOB tablespaces as LOB tablespaces
    • When configuring the new components, make sure that they have the same component names as the ones from the 2.2.1 installation.
  4. Update the installation with the latest service pack.
  5. 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 and unzip the Designer configuration that you exported in Prerequisites to [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.2.
    4. Depending on your OS, run the ant command as follows:
      • On UNIX, run the commands:
        • cd [Install_path_2.3.0]/AIS/Designer/extra/Tools
        • ./ant.sh migrateConfiguration
      • On Windows, run the command:
        • [Install_path_2.3.0]\AIS\Designer\extra\Tools\ant migrateConfiguration
    5. Compress the configuration in a zip file.
    6. Import and deploy the configuration from [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.3 on the current application without clean to Repository only.
    7. To back up the configuration, execute export configuration from Designer on disk.
    8. Delete the configuration from [Install_path_2.3.0]/AIS/Designer/extra/work/migration/ImportFiles_2.3.
  6. Migrate the Repository exported from Datastore 2.2.1 to Datastore 2.3.0:
    1. Specify the applications, queries and registry 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 Datastore Runtime application name and version in order to force the same version in the new installation
      • The full path of the query file exported from version 2.2.1
      • The full path of the 2.2.1 registry file export folder
      • The full path of the preference file exported from version 2.2.1
      • An [importFolder] file with value [Install_path_2.3.0]/AIS/Repository/extra/import.
    3. Sample XML file for a default application:
    4. <?xml version="1.0" encoding="UTF-8"?>


























    5. Start the console in [Install_path_2.3.0]/AIS/Repository/startConsole and run the following command: migrate -from 2.2.1.
      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.
    6. Import the report templates using the command importReportTemplates [exportFolder]
  7. Update the configuration in Designer:
    1. For Collection Types that use an aiPackedMVSReader import reader, update the import reader name from aiPackedMVSReader to aiMVSReader.
    2. Deploy the configuration from Designer to Datastore Runtime.
  8. 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.
  9. Copy the settings customizations from the 2.2.1 datastoreConfiguration.properties file into the 2.3.0 component.
  10. Note: You can use the following dstools command to get all the default settings: dstools setting list


Related Links