Migrating InfoSphere Metadata Workbench, Versions 8.1 and 8.1.1

Use this procedure to migrate from InfoSphere® Metadata Workbench, Versions 8.1 and 8.1.1 to InfoSphere Information Governance Catalog in InfoSphere Information Server,Version 11.7. You export the InfoSphere Metadata Workbench assets that are on the source computer, and then import the assets to the target computer to complete the migration.

Review the InfoSphere Metadata Workbench files and assets that cannot be migrated.
Transfer the following types of assets in order before you migrate InfoSphere Metadata Workbench assets:
  1. Migrate common metadata assets, such as databases, data files, and BI reports.
  2. Migrate InfoSphere DataStage® projects, including jobs, table definitions, and related job assets. Verify that you use the same host name for the engine, the same project names, and so on.
  3. Migrate InfoSphere DataStage project user environment variables by using IBM InfoSphere DataStage and QualityStage® Administrator.

All of the former InfoSphere Metadata Workbench functionality exists in InfoSphere Information Governance Catalog, however, the way you access that functionality has changed.

You can export and import the following InfoSphere Metadata Workbench assets:
  • Extension mapping documents and their contained mappings
  • All types of extended data sources
  • Custom attribute definitions
  • Published queries and user queries
When you choose an export method, review the metadata that each method supports.
  1. To migrate data lineage:
    1. Map any required database alias mappings on the target computer. The mapping should be identical to that of the old computer (this is a manual step).
    2. Optional: Manually bind InfoSphere DataStage and QualityStage stages to the data source or stage that they read from or write to. This process re-creates the manual bindings of the old system. InfoSphere Information Governance Catalog is able to determine some information about the asset, and display some lineage. Manual binding is recommended if the data flow relationships cannot be automatically detected in InfoSphere Information Governance Catalog.
    3. Optional: Include or exclude InfoSphere FastTrack mapping specifications for lineage.
    4. Optional: Reconfigure business lineage according to the settings of the old system. Include or exclude assets from business lineage.
    5. Remap the data source identities.
    6. On the target computer, import environment variables by using the command-line interface or a batch file.
  2. Manually take note of and update custom attributes.
  3. Recreate all custom attribute definitions on extension mapping documents on the new computer. This is a manual step.
  4. Export and import user-defined and published queries.
    Note: Due to changes in the attributes of assets, not all queries that are imported from earlier versions of InfoSphere Information Server work in version 11.3. You can recreate the queries in the Manage Queries window.