Preparing for migration in IBM Cloud Pak for Data

Make sure that the prerequisites listed in Prerequisites to migrating data are met. Then, complete the following tasks in Cloud Pak for Data 5.0.x before you import the InfoSphere Information Server content.

1. Installing the migration toolkit
2. Installing the latest version of the cpd-cli command-line interface
3. Setting up the export-import utility
4. Setting environment variables
5. Increasing the expiry time for tokens
6. Increasing the ephemeral storage for the wkc-data-rules pod
7. Providing connection information for storing rule output

The export-import utility needs to be set up for migration. Follow the sections in Migrating data between instances of Cloud Pak for Data to ensure that the utility is properly set up and initialized:

• Preparing to use the Cloud Pak for Data export and import utility
• Migrating data between Cloud Pak for Data installations

After the initialization is complete, run the following command to check if the utility is set up for migration:

cpd-cli export-import list aux-modules --namespace=${NAMESPACE} --profile=${PROFILE_NAME} --arch=${CPU_ARCH}

Set the following environment variables.

CP4D_HOST=<cp4d host>
CP4D_USERNAME=<default platform administrator user: cpadmin or admin>
CP4D_PASSWORD=<cp4d password>

If a large amount of data is to be migrated, increase the expiry time for tokens before you start the migration.

1. Check whether a token expiry time is set by running the following command:

   oc get configmap product-configmap --namespace=${NAMESPACE} -o custom-columns=test:.data.TOKEN_EXPIRY_TIME | sed '1d'

   If the parameter TOKEN_EXPIRY_TIME is set, note the original setting to be able to reset the value after the migration is complete.

2. Change the TOKEN_EXPIRY_TIME setting to a large value, such as 48 hours, by running the following command:

   oc patch configmap product-configmap --namespace=${NAMESPACE} --type=merge --patch="{\"data\": {\"TOKEN_EXPIRY_TIME\": \"48\"}}"

3. Check whether a token refresh period is set by running the following command:

   oc get configmap product-configmap --namespace=${NAMESPACE} -o custom-columns=test:.data.TOKEN_REFRESH_PERIOD | sed '1d'

   If the parameter TOKEN_REFRESH_PERIOD is set, note the original setting to be able to reset the value after the migration is complete.

4. Change the TOKEN_REFRESH_PERIOD setting to a large value, such as 48 hours, by running the following command:

   oc patch configmap product-configmap --namespace=${NAMESPACE} --type=merge --patch="{\"data\": {\"TOKEN_REFRESH_PERIOD\": \"48\"}}"

5. Restart the usermgmt pods by running the following command:

   oc delete pods --namespace=${NAMESPACE} -l component=usermgmt

Remember to revert this change after the migration is complete.

To avoid eviction of the wkc-data-rules pod when migrating data quality rules, increase the pod's ephemeral storage. You can revert this setting after migration or continue working with the increased storage settings.

1. Log in to the Red Hat® OpenShift® Container Platform as a user with administrator rights.
2. Check whether a value for the ephemeral-storage parameter is set for the wkc-data-rules pod and whether the value is less than 2Gi.

   oc get deployment wkc-data-rules --output="jsonpath={.spec.template.spec.containers[*].resources.limits.ephemeral-storage}" && echo -e "\n"

3. If the ephemeral-storage parameter values is less than 2Gi, run the following command to set the value to 2Gi:

   oc patch wkc wkc-cr -n ${NAMESPACE} --type merge -p '{"spec":{"wkc_data_rules_resources":{"requests":{"cpu":"100m","memory":"800Mi","ephemeral-storage":"50Mi"},"limits":{"cpu":1,"memory":"2048Mi","ephemeral-storage": "2Gi" }}}}'

If the InfoSphere Information Server engine tier and Cloud Pak for Data system cannot communicate over port 443, you must retrieve the details of the connection for storing the output of data rules to a JSON file and transfer that file to the InfoSphere Information Server system. To create the dq_rule_connection.json file, run the following command:

${TOOLKIT_PATH}/get_dq_rule_connection.sh --url https://${CP4D_HOST} -u ${CP4D_USERNAME} -p ${CP4D_PASSWORD} -name ${DQ_RULES_CONNECTION_NAME}