Prerequisites to migrating data (Watson Knowledge Catalog)

1. In Cloud Pak for Data, go to Administration > Catalogs.
2. Open the Catalog Setup tab and check which catalog is configured for sharing assets with Information Governance Catalog. It is usually Default Catalog.
3. Go to Catalogs > All catalogs and find this catalog.
4. From the menu, select Delete.

1. In Cloud Pak for Data, go to Administration > Catalogs.
2. Open the Catalog Setup tab and check which catalog is configured for sharing assets with Information Governance Catalog. It is usually Default Catalog.
3. On the Overview tab, find this catalog and open it.
4. Go to the Settings tab and clear the option Automatically create profiles for data assets. If the option is disabled, enable and disable it again to make sure it is disabled.

1. Log in to the wdp-db2 pod:

   ./oc exec -it c-db2oltp-wkc-db2u-0 /bin/bash

2. Run the following commands:

   su - db2inst1
   
   db2 connect to BGDB
   db2 "set schema bg"
   db2 "drop table \"flyway_schema_history\""
   db2 "update GLOSSARY_STORAGE_VERSION set version = '0.0'"
   db2 "delete from SCHEMAVERSION"

3. Restart the wkc-glossary-service pod. For example:

   oc delete wkc-glossary-service-849fdd8cd7-6nq52

• oc login
• oc edit
• oc delete
• oc get pods
• oc cp
• oc exec
• oc set

1. Edit the value of the maxmemory property in the redis.conf file. Run this command:

   oc edit cm redis-ha-configmap

   Change the value to "1573741824". It must be enclosed in double quotation marks.
2. Increase the Redis memory limit to 2 GB by running this command:

   oc set resources sts redis-ha-server -c redis --limits=memory=2Gi

3. Update the CAMS OMRS cache TTL setting by running this command:

   oc set env deploy catalog-api -c catalog-api omrs_cache_ttl_days=1

https://<target_host_name>/k8s/ns/wkc/deployments/catalog-api/environment

1. Log in to the Red Hat® OpenShift cluster with this command:

   oc login

2. Modify the HEAP SETTINGS section of the Cassandra JVM options.
   1. Run this command:

      oc -n ${PROJECT_CPD_INSTANCE} edit cm cassandra-jvm-options

   2. Modify the values. The -Xms and -Xmx options must have the same value. The value of the -Xmn option must be four times smaller than the value of the -Xmx option. The following excerpt shows recommended values. If you have more resources, you can increase the values.

      #################
      # HEAP SETTINGS #
      #################
      
      # Heap size is automatically calculated by cassandra-env based on this
      # formula: max(min(1/2 ram, 1024MB), min(1/4 ram, 8GB))
      # That is:
      # - calculate 1/2 ram and cap to 1024MB
      # - calculate 1/4 ram and cap to 8192MB
      # - pick the max
      #
      # For production use you may wish to adjust this for your environment.
      # If that's the case, uncomment the -Xmx and Xms options below to
      # override the automatic calculation of JVM heap memory.
      #
      # It is recommended to set min (-Xms) and max (-Xmx) heap sizes to
      # the same value to avoid stop-the-world GC pauses during resize, and
      # so that we can lock the heap in memory on startup to prevent any
      # of it from being swapped out.
      #-Xms1024M
      #-Xmx1024M
      -Xms4096M
      -Xmx4096M
      # Young generation size is automatically calculated by cassandra-env
      # based on this formula: min(100 * num_cores, 1/4 * heap size)
      #
      # The main trade-off for the young generation is that the larger it
      # is, the longer GC pause times will be. The shorter it is, the more
      # expensive GC will be (usually).
      #
      # It is not recommended to set the young generation size if using the
      # G1 GC, since that will override the target pause-time goal.
      # More info: http://www.oracle.com/technetwork/articles/java/g1gc-1984535.html
      #
      # The example below assumes a modern 8-core+ machine for decent
      # times. If in doubt, and if you do not particularly want to tweak, go
      # 100 MB per physical CPU core.
      #-Xmn256M
      -Xmn1024M

3. Modify the resource requests and limits for the Cassandra StatefulSet.
   1. Run this command:

      oc -n ${PROJECT_CPD_INSTANCE} edit sts cassandra

   2. Modify the values. The memory request value must be equal to the value of the -Xmx option. The memory limit value must be four times bigger than the request value. The following excerpt shows recommended values.

        resources:
          limits:
            cpu: 2
            memory: 16Gi
          requests:
            cpu: 1
            memory: 4Gi
      

   3. Restart the Cassandra pod by running this command:

      oc -n ${PROJECT_CPD_INSTANCE} delete pod cassandra-0

4. Modify the HEAP SETTINGS section of the iis-services configuration.
   1. Run this command:

      oc -n ${PROJECT_CPD_INSTANCE} edit cm iis-server

   2. Search for the -Xmx option and change its value. The recommended value is -Xmx16384m.
   3. Find the name of the iis-services pod. Run this command:

      oc get pods | grep iis-services

   4. Restart the iis-services pod. Use the name that was returned by the command in previous step. For example:

      oc -n ${PROJECT_CPD_INSTANCE} delete pod iis-services

5. Modify the resource requests and limits for the Solr StatefulSet.
   1. Run this command:

      oc -n ${PROJECT_CPD_INSTANCE} edit sts solr

   2. Modify the values. The following excerpt shows recommended values.

        resources:
          limits:
            cpu: 2
            memory: 4Gi
          requests:
            cpu: 1
            memory: 1Gi
      

   3. Restart the Solr pod by running this command:

      oc -n ${PROJECT_CPD_INSTANCE} delete pod solr-0

6. Modify the resource request and limit values for the event consumer StatefulSet.
   1. Run this command:

      oc -n ${PROJECT_CPD_INSTANCE} edit sts shop4info-event-consumer

   2. Modify the values. The following excerpt shows recommended values.

        resources:
          limits:
            cpu: 3
            memory: 4Gi
          requests:
            cpu: 200m
            memory: 1Gi
      

   3. Restart the event consumer pod by running this command:

      oc -n ${PROJECT_CPD_INSTANCE} delete pod shop4info-event-consumer-0

7. Modify the resource limits for the conductor StatefulSet.
   1. Run this command:

      oc -n ${PROJECT_CPD_INSTANCE} edit sts is-en-conductor

   2. Modify the values. The following excerpt shows recommended values.

        resources:
          limits:
            cpu: 6
            memory: 16Gi 
      

   3. Restart the conductor pod by running this command:

      oc -n ${PROJECT_CPD_INSTANCE} delete pod is-en-conductor-0

1. Search for the Db2 pod (wdp-db2-0) name, use ‘db2’ as the search string.

   oc get pods | grep db2

2. Log in to the Db2 pod.

   oc exec -it wdp-db2-0 bash

3. Switch to the db2inst1 user:

   su - db2inst1

4. Run the following command:

   db2 "update db cfg for ilgdb using logsecond max_num_allowed"

   The value you set for max_num_allowed is the maximum number of secondary log files that can be created and is usually calculated as 256 minus the number of primary log files. For more information about the logsecond configuration parameter, see the Db2 documentation.

1. Search for the conductor pod (is-en-conductor-0) name, use ‘conductor’ as the search string.

   oc get pods | grep conductor

2. Log in to the conductor pod.

   oc exec -it is-en-conductor-0 bash

3. Navigate to /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.iis.client/iis.client.site.properties. Open the file and add the following property:

   com.ibm.iis.http.soTimeout=36000000

4. Search for the iis-services pod (iis-services) name, use ‘services’ as the search string.

   oc get pods | grep services

5. Log in to the iis-services pod.

   oc exec -it iis-services bash

6. Run the following commands:

   /opt/IBM/InformationServer/ASBServer/bin/iisAdmin.sh -set -key com.ibm.iis.gov.vr.setting.maxObjectsInMemory -value 4000000
   /opt/IBM/InformationServer/ASBServer/bin/iisAdmin.sh -set -key com.ibm.iis.gov.xFrameOptions -value SAMEORIGIN

7. Change the value of the Xmx option in the configMap file.
   1. Run the following command:

      oc -n ${PROJECT_CPD_INSTANCE} edit cm iis-server

   2. Modify the -Xmx option to have the -Xmx16384m value.
   3. Find the name of the iis-services pod. Run this command:

      oc get pods | grep iis-services

   4. Restart the iis-services pod. Use the name that was returned by the command in previous step. For example:

      oc -n ${PROJECT_CPD_INSTANCE} delete pod iis-services

8. Stop the Information Server server by running the following command:

   /opt/IBM/InformationServer/wlp/bin/server stop iis

9. Navigate to the opt/IBM/InformationServer/wlp/usr/servers/iis/server.xml file. Open the file and configure the options to the following values:

   <httpSession ... invalidationTimeout="3600" ... />
   <ltpa expiration="7600m"/>
   <transaction ... clientInactivityTimeout="36000" propogatedOrBMTTranLifetimeTimeout="72000" totalTranLifetimeTimeout="72000" ... />

10. Start the Information Server server again by running the following command:

    /opt/IBM/InformationServer/wlp/bin/server start iis

1. In Cloud Pak for Data, go to Administration > User management.
2. Click New user.
3. Provide the required information and save the changes.

• Db2 connector
• Netezza® connector