Watson Knowledge Catalog and InfoSphere Information Server migration to IBM Knowledge Catalog: What's new

Migration from InfoSphere Information Server 11.7.1.4 or 11.7.1.5 to IBM Knowledge Catalog in IBM Cloud Pak for Data 5.0.1

Toolkits:

• InfoSphere Information Server 11.7.1.x migration toolkit for Cloud Pak for Data 5.0.1

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to the IBM InfoSphere Information Server 11.7.1.x installation (Part 1 of 2)

• Cloud Pak for Data 5.0.1 migration toolkit

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to a new IBM Knowledge Catalog 5.0.x installation (Part 2 of 2)

Release date: 10 August 2024

New and changed features

SQL virtual tables are now migrated as SQL-based data assets. You can use the new migrate_sql_vt_as_sql_asset option of the DQ_PERF_CONFIG export parameter to revert to the previous behavior and have SQL virtual tables migrated as SQL-based data quality rules instead.

Migration from InfoSphere Information Server 11.7.1.4 or 11.7.1.5 to IBM Knowledge Catalog in IBM Cloud Pak for Data 5.0.0

Toolkits:

• InfoSphere Information Server 11.7.1.4 SP2 migration toolkit for Cloud Pak for Data 5.0.0

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to the IBM InfoSphere Information Server 11.7.1.x installation (Part 1 of 2)

• Cloud Pak for Data 5.0.0 migration toolkit

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to a new IBM Knowledge Catalog 5.0 installation (Part 2 of 2)

Release date: 3 July 2024

New and changed features

During the import, an import-summary.json file is written, which contains details about the assets imported with the latest run.

In-place upgrade and migration to IBM Knowledge Catalog in IBM Cloud Pak for Data 4.8.5

Toolkit: Migration toolkit for migrating from Cloud Pak for Data 4.6 to Cloud Pak for Data 4.8.5
For download and installation instructions, see In-place upgrade and migration to Cloud Pak for Data 4.8.5. 

New and changed features for the toolkit released in August 2024

SQL virtual tables are now migrated as SQL-based data assets. You can use the new migrate_sql_vt_as_sql_asset option of the DQ_PERF_CONFIG export parameter to revert to the previous behavior and have SQL virtual tables migrated as SQL-based data quality rules instead.

New and changed features for the toolkit released in July 2024

During the import, an import-summary.json file is written, which contains details about the assets imported with the latest run.

New and changed features for the toolkit released in June 2024

No new features were introduced with this toolkit.

New and changed features for the toolkit released in April 2024

Migration from InfoSphere Information Server 11.7.1.4 to IBM Knowledge Catalog in IBM Cloud Pak for Data 4.8.5

Toolkits:

• InfoSphere Information Server 11.7.1.4 SP2 migration toolkit for Cloud Pak for Data 4.8.5

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to the IBM InfoSphere Information Server 11.7.1.x installation (Part 1 of 2)

• Cloud Pak for Data 4.8.5 migration toolkit

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to a new IBM Knowledge Catalog 4.8.x installation (Part 2 of 2): Cloud Pak for Data 4.8.5

New and changed features for the toolkit released in August 2024

SQL virtual tables are now migrated as SQL-based data assets. You can use the new migrate_sql_vt_as_sql_asset option of the DQ_PERF_CONFIG export parameter to revert to the previous behavior and have SQL virtual tables migrated as SQL-based data quality rules instead.

New and changed features for the toolkit released in July 2024

During the import, an import-summary.json file is written, which contains details about the assets imported with the latest run.

New and changed features for the toolkit released in June 2024

No new features were introduced with this toolkit.

New and changed features for the toolkit released in April 2024

• Support of additional platforms and metadata repository types

  InfoSphere Information Server operating system	InfoSphere Information Server metadata repository	IBM Cloud Pak for Data version
  Red Hat® Enterprise Linux® 8.x	Db2®	4.8.0 and later
  Red Hat® Enterprise Linux® 8.x	Oracle	4.8.3 and later
  AIX 7.x	Db2®	4.8.3 and later
  SUSE Linux Enterprise Server (SLES) 15	Db2®	4.8.4 and later
  Red Hat Enterprise Linux on System z®	Db2®	4.8.4 and later
  SUSE Linux on System z	Db2®, Oracle	4.8.4 and later
  Microsoft Windows	Db2®, Oracle, Microsoft SQL Server	4.8.5 and later

In-place upgrade and migration to IBM Knowledge Catalog in IBM Cloud Pak for Data 4.8.4

Toolkit: Migration toolkit for migrating from Cloud Pak for Data 4.6 to Cloud Pak for Data 4.8.4
For download and installation instructions, see In-place upgrade and migration to Cloud Pak for Data 4.8.4. 

New and changed features

• Enhanced inspect command to understand the type of legacy data that exists in Cloud Pak for Data.
• Improvements for rerunning the import command when the initial import failed or is stuck:
  • No need to delete the projects created by the initial import. The migration tool will identify failed (or partially imported) projects and delete them before rerunning the import.
  • If the fix for the import failure requires exporting the data again, you do not need to reimport all the data. You can provide a filter to reimport only the previously failed data archives.

Migration from InfoSphere Information Server 11.7.1.4 to IBM Knowledge Catalog in IBM Cloud Pak for Data 4.8.4

Toolkits:

• InfoSphere Information Server 11.7.1.4 SP2 migration toolkit for Cloud Pak for Data 4.8.4

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to the IBM InfoSphere Information Server 11.7.1.x installation (Part 1 of 2)

• Cloud Pak for Data 4.8.4 migration toolkit

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to a new IBM Knowledge Catalog 4.8.x installation (Part 2 of 2): Cloud Pak for Data 4.8.4

New and changed features

• Support of additional platforms and metadata repository types

  InfoSphere Information Server operating system	InfoSphere Information Server metadata repository	IBM Cloud Pak for Data version
  Red Hat® Enterprise Linux® 8.x	Db2®	4.8.0 and later
  Red Hat® Enterprise Linux® 8.x	Oracle	4.8.3 and later
  AIX 7.x	Db2®	4.8.3 and later
  SUSE Linux Enterprise Server (SLES) 15	Db2®	4.8.4 and later
  Red Hat Enterprise Linux on System z®	Db2®	4.8.4 and later
  SUSE Linux on System z	Db2®	4.8.4 and later

• Enhanced inspect command to understand the type of data that exists in InfoSphere Information Server.
• Improvements for rerunning the import command when the initial import failed or is stuck:
  • No need to delete the projects created by the initial import. The migration tool will identify failed (or partially imported) projects and delete them before rerunning the import.
  • If the fix for the import failure requires exporting the data again, you do not need to reimport all the data. You can provide a filter to reimport only the previously failed data archives.
• The MEMBER parameter is no longer required when you import the data exported from InfoSphere Information Server.
• You can now perform rehoming by passing the import parameter "force_rehome", instead of manually running the commands.
• If InfoSphere Information Server is not configured with LDAP, you can now migrate users and groups by using commands. You no longer need to create the users and groups manually in Cloud Pak for Data.

In-place upgrade and migration to IBM Knowledge Catalog in IBM Cloud Pak for Data 4.8.3

Toolkit: Migration toolkit for migrating from Cloud Pak for Data 4.6 to Cloud Pak for Data 4.8.3
For download and installation instructions, see In-place upgrade and migration to Cloud Pak for Data 4.8.3.

New and changed features

• If you rerun import when the first import attempt failed or got stuck, only the failed or skipped metadata of asset types are now imported on rerun, instead of all the assets. For more information, see Rerunning the import in case of a failed or stuck initial run.

Migration from InfoSphere Information Server 11.7.1.4 to IBM Knowledge Catalog in IBM Cloud Pak for Data 4.8.3

Toolkits:

• InfoSphere Information Server 11.7.1.4 SP2 migration toolkit for Cloud Pak for Data 4.8.3

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to the IBM InfoSphere Information Server 11.7.1.x installation (Part 1 of 2)

• Cloud Pak for Data 4.8.3 migration toolkit

  For more information, see Migration from IBM InfoSphere Information Server to IBM Knowledge Catalog: Applying patches and toolkit to a new IBM Knowledge Catalog 4.8.x installation (Part 2 of 2): Cloud Pak for Data 4.8.3

New and changed features

• Support of additional platforms and metadata repository types

  InfoSphere Information Server operating system	InfoSphere Information Server metadata repository	IBM Cloud Pak for Data version
  Red Hat® Enterprise Linux® 8.x	Db2®	4.8.0 and later
  Red Hat® Enterprise Linux® 8.x	Oracle	4.8.3 and later
  AIX 7.x	Db2®	4.8.3 and later

• You can now migrate users from an internal or local operating-system user registry to Cloud Pak for Data. For more information, see Migrating users and groups.
• The new parameters CP_CONSOLE_HOST and IDENTITY_TOKEN are required for importing users and groups to a Cloud Pak for Data system where the Identity Management Service is enabled. For more information about how to create and use these parameters, see Importing users and groups to Cloud Pak for Data.
• The export parameter env was removed from the export command.
• If you rerun import when the first import attempt failed or got stuck, only the failed or skipped metadata of asset types are now imported on rerun, instead of all the assets. For more information, see Rerunning the import in case of a failed or stuck initial run.