Migrating and removing legacy governance features

If you have the legacy components of Watson™ Knowledge Catalog installed in a previous version of Cloud Pak for Data and want to preserve and use that data after you upgrade to Cloud Pak for Data 4.7, you must migrate your data.

You can migrate data from these previous versions:
  • From IBM Cloud Pak® for Data 4.5
  • From IBM Cloud Pak for Data 4.6
Important: Before you upgrade, work with your IBM representative to determine the best timeline for your migration based on the legacy features you need to migrate. You can migrate the features and data described in Migration scope.

As soon as you start the actual export process, the legacy system metadata is frozen and you should complete the migration. The legacy features are no longer supported after that point and must be removed.

Migration overview

Up to IBM Cloud Pak for Data 4.6, you could choose between two main Watson Knowledge Catalog configurations.

The base configuration included legacy features that are based on Information Server components. In IBM Cloud Pak for Data 4.7, the legacy features are being retired. If you have the base configuration of Watson Knowledge Catalog installed, the upgrade to IBM Cloud Pak for Data 4.7 involves migrating data from the legacy components to replacement features in Watson Knowledge Catalog. For more information about the replacement features, see Where you can find the migrated data.

The following features are removed and can no longer be used after the upgrade and removal of the legacy features:
  • Automation rules
  • Custom attribute administration
  • Information assets view including lineage, administration of lineage reports, and customization of asset display
  • Data discovery (automated discovery and access to quick scan results)
  • Data quality projects
  • Metadata import with a bridge or connector
These menu entries will be gone after the upgrade and removal of the legacy features:
Legacy features in the Cloud Pak for Data menu

The permissions that were required to access and work with these features except for the Manage asset discovery permission are also removed. The replacement features require different permissions.

Migration flow

Before you start the upgrade and the migration, make sure to also read the information in Migration scope.

The image depicts the migration process in general:
Migration flow chart
The process is broken up into these phases:
  • Preparation
    1. Complete all required preparation tasks in your IBM Cloud Pak for Data 4.5 or 4.6 deployment. For more information, see Completing setup tasks.
    2. Apply the patches that are required for the migration in your IBM Cloud Pak for Data 4.5 or 4.6 deployment. For more information, see Applying required Version 4.5 or 4.6 patches.
    3. Run the export in inspect mode to determine whether your installation allows for migration:
      • Yes: Proceed to the next step.
      • No: Postpone the upgrade right away and remove the migration patches.

      For more information, see Running the export in inspect mode.

    4. To see what data exactly will be migrated and to validate the export process, execute a test run of the data export for migration.
      • If the export was successful and your installation is ready for migration, proceed with the next step.
      • If the export was not successful, or your installation isn't ready for migration, postpone the upgrade right away and remove the migration-related patches.

      For more information, see Running an export test.

  • Upgrade
    1. Back up your IBM Cloud Pak for Data 4.5 or 4.6 installation.
    2. Upgrade to IBM Cloud Pak for Data 4.7.
  • Migration
    1. Check for patch updates or additional patches, and apply or reapply any required patches. For more information, see Applying Version 4.7 patches.
    2. Run the export and check the export logs.
    3. Run the import and check the import logs.
    4. Verify migration results. For more information, see Verifying successful migration.
    5. After successful migration of your data, run the cleanup tool to remove the legacy components from your IBM Cloud Pak for Data deployment. For more information, see Migration cleanup.
    6. Complete all required post-migration task. For more information, see Post-migration tasks.
    Important: Removing the legacy components and completing required post-migration tasks is mandatory (steps 5 and 6). An IBM Cloud Pak for Data system where the legacy components were not removed and required post-migration tasks were not completed is a non-supported environment and must not be used in production.