Migrating InfoSphere Metadata Workbench, Versions 8.5 and 8.7

Use this procedure to migrate assets from InfoSphere® Metadata Workbench, versions 8.5 and 8.7 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. Migrate extended data sources and extension mapping documents::
    1. Export extended data sources from the source computer by using the istool command line.
    2. Import the extended data sources by using the workbench extension source import command.
    3. Export extension mapping documents from the source computer by using the InfoSphere Metadata Workbench user interface.
    4. Import extension mappings by using the workbench extension mapping import command.

    You can also use the InfoSphere Metadata Workbench user interface to export extended data sources and extension mapping documents and the InfoSphere Information Governance Catalog to import them.

    Export of extended data sources and extension mapping documents does not include steward assignments or term assignments. Import of these types of assets is limited to files of 5 MB in size. When you export the assets, you can use the -maxArchiveSize parameter to create multiple files no larger than 5 MB. Warnings are issued if a mapping does not reconcile to an existing source or target asset.

  2. Migrate data lineage:
    1. An InfoSphere Information Governance Catalog administrator must identify the InfoSphere DataStage projects and jobs that it is necessary to detect relationships and report data lineage for. The administrator must edit each selected project by selecting each asset, editing it, and selecting Include for Lineage. By default, the Include For Lineage settings for a job have the same value of the transformation project, and can be manually edited and changed to a different value.
      For more information, see Detecting lineage relationships.
    2. Map any required data connection mappings (previously referred to as database alias mappings) on the new computer. The mapping should be identical to that of the old system (this is a manual step).
    3. For Version 8.7: Export custom attributes from the source computer by using the from the InfoSphere Metadata Workbench user interface. Import them on to the target computer by using the Information Governance Catalog user interface. You can also use istool to export and import custom attributes.
      Note: You must have the custom attributes and the assets that the custom attributes refer to on your target computer before you import the custom attribute definitions.
      For more information, see Extending the asset meaning by using custom attributes.
    4. 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.
    5. Optional: Include or exclude InfoSphere FastTrack mapping specifications for lineage.
      For more information, see Configuring assets for lineage and business lineage reports.
    6. Optional: Reconfigure business lineage according to the settings of the old system. Include or exclude assets from business lineage.
    7. Optional: On the target computer, redefine the database schemas so they match the database schemas on your source computer.
    8. Remap the data source identities.
    9. On the target computer, import environment variables by using the command-line interface or a batch file.
  3. 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 later versions. You can recreate the queries in the Manage Queries window.