Migrating InfoSphere Information Analyzer

Use these procedures to migrate InfoSphere® Information Analyzer. You need to export the InfoSphere Information Analyzer assets that are on the source computer, and then import the assets to the target computer to complete the migration.

Before you begin

Review the InfoSphere Information Analyzer files and assets that cannot be migrated.

The following conditions must be met before you begin this task:

The analysis database must exist on the target computer, and a JDBC data source for the analysis database must exist in WebSphere® Application Server. If the analysis database that you are planning to use was created during the installation process of InfoSphere Information Analyzer, version 11.5, then this JDBC data source was created automatically. If the analysis database that you are planning to use is a different database, that was not created during the installation process of InfoSphere Information Analyzer, version 11.5, then follow the instructions in Configuring a JDBC data source for the InfoSphere Information Analyzer analysis database to create this JDBC data source.
Data sources that contain the data that you want to analyze and that correspond to the data sources that were used in the earlier release must exist and be accessible locally or over a computer network.
You must create a data connection for the analysis database by using IBM® InfoSphere Metadata Asset Manager to create an import area with no data imported. See Defining a connection to the analysis database.
If you use custom java classifiers, you must move the custom JAR file from the source system to the target system. You can move the JAR file before or after you move data classifications that depend on the JAR file.

Before you start migrating InfoSphere Information Analyzer by using the istool command-line, decide how you want to migrate your common metadata assets. You have the following options:

Migrate all common metadata for the entire suite all at once. When you migrate the common metadata, you can include all data connections to the databases, data files, and data files folders that you are migrating, with the exception of data connections that are created in InfoSphere DataStage. After you migrate all common metadata, then you can export all of the InfoSphere Information Analyzer projects by using the InfoSphere Information Analyzer commands for istool.
Migrate only InfoSphere Information Analyzer assets by using the InfoSphere Information Analyzer export commands for istool, and specifying the -includeCommonMetadata option when you export. When you use this method, you move InfoSphere Information Analyzer assets that are related to InfoSphere Information Analyzer projects. For example, -ia '-projects=* -includeCommonMetadata' -cm '-includeDataConnection -includeAnnotation'. This command exports InfoSphere Information Analyzer projects, all common metadata related to the projects, all data connections related to the common metadata that is exported, and annotations related to the common metadata.
To determine which common metadata assets that InfoSphere Information Analyzer uses, open each InfoSphere Information Analyzer project and click on Project Properties. Review the Data Sources tab and document the names of all databases used in the project. Repeat this for each InfoSphere Information Analyzer project and gather the names of all databases used in the projects. You then export them by using the -cm parameter and specifying the database for each project.

Note: When you use istool to export projects, you can use the -includeCommonMetadata option to transfer common metadata assets that are used by the projects, including data connections. However, depending on your migration strategy, you might prefer to transfer all common metadata assets by using the -commonmetadata parameter in a separate export command.

About this task

You migrate InfoSphere Information Analyzer, Versions 8.5 and later by using istool.

High-level analysis summaries, which include high-level details of column analysis such as maximum values, minimum values, total number of records for a column, and so on, are exported and imported with InfoSphere Information Analyzer projects. Data rules are exported and imported as part of the common metadata.

You export assets by using the version of the istool command-line that corresponds to your source computer. You import assets by using Version 11.5 of the istool command-line.

Procedure

Use one of the following procedures to migrate InfoSphere Information Analyzer:

Table 1. Procedures for migrating InfoSphere Information Analyzer
Version	Procedure
Version 11.5	Exporting InfoSphere Information Analyzer assets by using istool Importing by using istool
Version 11.3	Exporting InfoSphere Information Analyzer assets by using istool Importing by using istool
Version 9.1	Exporting InfoSphere Information Analyzer assets by using istool Importing by using istool
Version 8.7	Exporting InfoSphere Information Analyzer assets by using istool Importing by using istool
Version 8.5	Exporting InfoSphere Information Analyzer assets by using istool Importing by using istool
Version 8.1.1 and 8.1.2	Deploying quality components Only the rule definitions are exported or imported.

What to do next

After exporting and importing InfoSphere Information Analyzer by using istool, you must perform some configuration tasks and rerun some types of analyses.

You must perform the following configuration tasks:

Configure the analysis database settings. You can configure global analysis database settings, which are inherited by all projects, or you can configure analysis database settings for each project. See Configuring global analysis database settings or Modifying project analysis database settings.
Configure the analysis settings, such as thresholds. You can configure global analysis settings, which are inherited by all projects, or you can configure analysis settings for each project. See Configuring global analysis details settings or Modifying project analysis settings.

If you want results of primary key, foreign key, or natural key analyses, you must rerun these analyses.