Post-migration tasks

Tasks performed in the Cloud Pak for Data experience

• On the Manage users page, the ${LINEAGE_ADMIN_USERNAME} user with System admin role needs to verify that all owners of migrated metadata imports have Lineage Administrator role added.

  

• Log in as the ${DSD_ADMIN_USERNAME} user and go to the Data > Connectivity page. In the Data source definitions tab, verify that the data source definitions created by the migration are listed.

  

• Verify that a new project with a name "MantaDataLineage" is available on the Projects page. All connections and metadata import configurations migrated from IBM Automatic Data Lineage will be migrated to this project.

  

• Open "MantaDataLineage" project and verify created connections and metadata imports. The connection name will be same as the dictionary identifier in the IBM Automatic Data Lineage. A metadata import will be created for each migrated connection with the format of the name "Migrated MDI_XXXX_{MANTA connection dictionary ID}". For example, "Migrated MDI_0c03e1d5-e626-4df0-588a-9e845a1ec8a2_DataStageCP4D". The owners of migrated metadata import can verify that the lineage metadata import can be run successfully.

  

• After completing the post-migration tasks and verifying the migrated metadata import jobs, delete the data folder under ${MIGRATION_DATA_PATH}/${MIGRATION_INSTANCE_NAME}/standalonemanta2cpd/.

Updating connections with TLS certificates

Some of the connections migrated from IBM Automatic Data Lineage needs to be configured with proper TLS certificate details. The administrator has to perform this task after running the migration.

1. Identify connections that need TLS certificate configured.

2. Get the details of certificate mapping from export.log file.

   NAMESPACE=<namespace>
   MIGRATION_INSTANCE_NAME=<migration instance name>
   CPD_AUX_POD=`oc get pods -n ${NAMESPACE} -o custom-columns=POD:.metadata.name | grep cpd-aux`
   oc rsh $CPD_AUX_POD
   NAMESPACE=<namespace>
   MIGRATION_INSTANCE_NAME=<migration instance name>
   cd  /data/cpd/data/exports/${NAMESPACE}/${MIGRATION_INSTANCE_NAME}/20*/mdi-lineage-migration/standalonemanta2cpd/logs
   cat export.log | grep "Alias:"
   

   An example of logs showing the certificate alias name and corresponding file which contains certificate details:

   bash-3.2# cat export.log | grep "Alias:"
   18:10:34.322 [main] INFO com.ibm.mdilineage.migration.MdiLineageExporter -- Alias: https://conops-tableau-server1.fyre.ibm.com/_0, exported to file: 23575322-98c6-4040-9481-48fe9f40f35d.txt
   18:10:34.323 [main] INFO com.ibm.mdilineage.migration.MdiLineageExporter -- Alias: a, exported to file: d849b741-c457-41d4-9016-98a06c729a1c.txt
   18:10:34.323 [main] INFO com.ibm.mdilineage.migration.MdiLineageExporter -- Alias: hive, exported to file: 8bd467cd-984f-4e14-9ed8-3075cd9d4b17.txt
   

3. Identify the alias name used in IBM Automatic Data Lineage for the connection and get the corresponding certificate file name in the path. The certificates are stored inside the folder data/certificates. Find the name of the corresponding certificate file.

   bash-3.2# ls -ltr data/certificates/
   -rwxrwxrwx@ 1 root  staff  1179 Apr 23 06:40 d849b741-c457-41d4-9016-98a06c729a1c.txt
   -rwxrwxrwx@ 1 root  staff  1321 Apr 23 06:40 8bd467cd-984f-4e14-9ed8-3075cd9d4b17.txt
   -rwxrwxrwx@ 1 root  staff  1345 Apr 23 06:40 23575322-98c6-4040-9481-48fe9f40f35d.txt
   

4. View contents of the corresponding file, for example:

   cat data/certificates/d849b741-c457-41d4-9016-98a06c729a1c.txt
   

5. Go the Cloud Pak for Data UI and edit the corresponding connection in the project. Enter the contents of the certificate file in the SSL certificate property and save the connection.