Migrating from IBM Automatic Data Lineage to IBM Manta Data Lineage

In Cloud Pak for Data Version 5.4.x, the MDI Lineage Migration Toolkit is available, enabling the migration of connections, alias mappings and SSL certificates from IBM Automatic Data Lineage to IBM Manta Data Lineage.

Since migration is a one-time task, it is important to review the list of connectors that are supported in the current release before proceeding. See, Supported connectors for migration. During the migration process, data source definitions, metadata imports and jobs are created automatically for each migrated connection.

Migration Process

The process is broken up into these phases:

  1. Export from IBM Automatic Data Lineage: The MDI Lineage Migration Toolkit creates an archive tar.gz which contains connections, alias mappings, SSL certificates and backup of configuration files. This archive needs to be copied to the Cloud Pak for Data.

  2. Import to the Cloud Pak for Data with installed IBM Manta Data Lineage: The MDI Lineage Migration Toolkit automatically creates data source definitions, metadata imports, jobs and alias mappings.

  3. Post-migration tasks: Migrated connections need to be reviewed and manually updated with SSL certificates included in the exported instance. See, Updating connections with TLS certificates.

Prerequisites for IBM Automatic Data Lineage

  • You can perform migration only from IBM Automatic Data Lineage 42.10 and later.
  • You can perform migration both on the RedHat and Windows OS, however, you must execute the migration process only on a RedHat environment. If you use Windows, you must transfer the required files to the RedHat system before enabling the migration process.
  • Use Java 17 or above to perform migration.
  • All the services of IBM Automatic Data Lineage should be up and running.
  • There should be enough space to store the exported instance and the archive.