Creating a service instance for Cognos Analytics programmatically

Information you need to complete this task

Review the following information before you create a service instance for Cognos Analytics:

Version requirements

All of the components that are associated with an instance of Cloud Pak for Data must be installed or created at the same release. For example, if Cognos Analytics is installed at Version 4.7.4, you must create the service instance at Version 4.7.4.

Important: Cognos Analytics uses a different version number from Cloud Pak for Data. This topic includes a table that shows the Cognos Analytics version for each refresh of Cloud Pak for Data. Use this table to find the correct version based on the version of Cloud Pak for Data that is installed.

Environment variables

The commands in this task use environment variables so that you can run the commands exactly as written.

• If you don't have the script that defines the environment variables, see Setting up installation environment variables.
• To use the environment variables from the script, you must source the environment variables before you run the commands in this task. For example, run:

  source ./cpd_vars.sh

Before you begin

This task assumes that the following prerequisites are met:

You must have sufficient resources for the plan size that you select. If you do not have sufficient resources, the instance cannot be created.

Procedure

Complete the following tasks to create a service instance:

1. Creating a service instance
2. Validating that the service instance was created
3. What to do next

Creating a service instance

To create a service instance:

1. Change to the directory on your workstation where you want to create the JSON file that defines the service instance payload.
2. Set the environment variables that are used to populate the JSON payload for the service instance:
   1. Set the INSTANCE_NAME environment variable to the unique name that you want to use as the display name for the service instance:

      export INSTANCE_NAME="<display-name>"

      This name is displayed on the Instances page of the Cloud Pak for Data web client.

      The display name is a string and can contain alphanumeric characters (a-z, A-Z, 0-9), spaces ( ), dashes (-), underscores (_), and periods (.). Make sure that you surround the display name with quotation marks, as shown in the preceding export command.

   2. Set the INSTANCE_VERSION to the version that corresponds to the version of Cloud Pak for Data on your cluster:

      export INSTANCE_VERSION=<version>

      Use the following table to determine the appropriate value:

      Cloud Pak for Data version	Service instance version
      4.7.4	24.3.0
      4.7.3	24.3.0
      4.7.2	24.0.0
      4.7.1	24.0.0
      4.7.0	24.0.0

   3. Set the INSTANCE_PROJECT to the project where you want to create the service instance:

      ---

      Create the service instance in the operands project

      export INSTANCE_PROJECT=${PROJECT_CPD_INST_OPERANDS}

      The command uses the PROJECT_CPD_INST_OPERANDS variable, which is already defined in your installation environment variables script.

      ---

      Create the service instance in a tethered project

      Important: If multiple tethered projects are associated with this instance of Cloud Pak for Data, make sure that the ${PROJECT_CPD_INSTANCE_TETHERED} environment variable is set to the correct project name before you run the export command:

      echo $PROJECT_CPD_INSTANCE_TETHERED

      export INSTANCE_PROJECT=${PROJECT_CPD_INSTANCE_TETHERED}

      ---

      Remember: You can create only one service instance in each project.
   4. Set the CPD_ROUTE environment variable:

      export CPD_ROUTE=$(oc get route cpd -n ${PROJECT_CPD_INST_OPERANDS} -o jsonpath={".spec.host"})

      The command uses the PROJECT_CPD_INST_OPERANDS variable, which is already defined in your installation environment variables script.

   5. Set the CONTENT_STORE_CONNECTION_NAME environment variable to the name of the platform connection that you created to connect to the content store for the service instance.

      export CONTENT_STORE_CONNECTION_NAME=<connection-display-name>

   6. Set the AUDIT_DB_CONNECTION_NAME environment variable to the name of the platform connection that you created to connect to the audit database for the service instance.

      export AUDIT_DB_CONNECTION_NAME=<connection-display-name>

   7. Set the INSTANCE_SIZE environment variable. The size determines the resources that are allocated to the service instance.

      export INSTANCE_SIZE=<size>

      Valid values are:

      • fixedminimum
      • small
      • medium
      • large

      For more information about the resources associated with each size, see the component scaling guidance PDF, which you can download from the IBM® Entitled Registry.

   8. Set the FIPS_MODE environment variable based on whether FIPS is enabled on the cluster:
      • If FIPS is not enabled on the cluster, set:

        export FIPS_MODE=""

      • If FIPS is enabled on the cluster, set:

        export FIPS_MODE=FIPS_140

3. Create the cognos-analytics-instance.json payload file:

   cat << EOF > ./cognos-analytics-instance.json
   {
       "addon_type": "cognos-analytics-app",
       "display_name": "${INSTANCE_NAME}",
       "addon_version": "${INSTANCE_VERSION}",
       "namespace": "${INSTANCE_PROJECT}", 
       "create_arguments": {
           "deployment_id": "",
           "parameters": {
               "global.cp4dWebUrl": "https://${CPD_ROUTE}:443/cognosanalytics/bi/v1/disp", 
               "global.cp4dWebUrlBase": "${CPD_ROUTE}",
               "global.icp4Data": "true",
               "global.tls.enabled": "false", 
               "global.icp4DataVersion": "${INSTANCE_VERSION}",
               "global.cs.databaseExternal": "true",
               "global.cs.databaseConnectionName": "${CONTENT_STORE_CONNECTION_NAME}",
               "global.cs.databaseProvider": "", 
               "global.cs.databaseHost": "",
               "global.cs.databasePort": "",
               "global.cs.databaseName": "",
               "global.cs.databaseUser": "",
               "global.cs.databasePass": "",
               "global.cs.databaseTlsEnabled": "",
               "global.audit.databaseExternal": "true", 
               "global.audit.databaseConnectionName": "${AUDIT_DB_CONNECTION_NAME}",
               "global.audit.databaseProvider": "",
               "global.audit.databaseHost": "",
               "global.audit.databasePort": "",
               "global.audit.databaseName": "",
               "global.audit.databaseUser": "",
               "global.audit.databasePass": "",
               "global.audit.databaseTlsEnabled": "",
               "pvc.pvProvisioning": "NamedStorageClass",
               "pvc.storageClassName": "${STG_CLASS_FILE}",
               "pvc.blockStorageClassName": "${STG_CLASS_BLOCK}",
               "metadata.planSize": "${INSTANCE_SIZE}",
               "metadata.storageType": "storage-class",
               "metadata.storageClass": "${STG_CLASS_FILE}",
               "metadata.cryptoConformance": "${FIPS_MODE}",
               "metadata.autoScaleConfig": "true"
           }
       }
   }
   EOF

   The following environment variables use the values that are already defined in your installation environment variables script:

   • ${STG_CLASS_BLOCK}
   • ${STG_CLASS_FILE}
4. Set the PAYLOAD_FILE environment variable to the fully qualified name of the JSON payload file on your workstation:

   export PAYLOAD_FILE=<fully-qualified-JSON-file-name>

5. Set the environment variables that are used to connect to the instance of Cloud Pak for Data where you want to create the service instance:
   1. Set the AUTH_TOKEN environment variable to the authentication token that you created:

      export AUTH_TOKEN=<your_authorization_token>

6. Create the service instance from the payload file.

   The command that you run depends on whether the instance of Cloud Pak for Data where you want to create the service instance uses a self-signed certificate or a certificate signed by a trusted certificate authority.

   ---

   The instance uses a certificate signed by a trusted certificate authority

   curl --request POST \
   --url "https://${CPD_ROUTE}/zen-data/v3/service_instances" \
   --header "Authorization: Bearer ${AUTH_TOKEN}" \
   --header 'Content-Type: application/json' \
   --data @${PAYLOAD_FILE}

   ---

   The instance uses a self-signed certificate (default)

   curl -k --request POST \
   --url "https://${CPD_ROUTE}/zen-data/v3/service_instances" \
   --header "Authorization: Bearer ${AUTH_TOKEN}" \
   --header 'Content-Type: application/json' \
   --data @${PAYLOAD_FILE}

   ---

   If the request was successful, the command returns one of the following HTTP response codes:

   • 200 - The request was successfully completed and the service instance was provisioned.
   • 202 - The request was successfully submitted. The service instance is being provisioned.

   If the request was not successful, use the HTTP response code to determine the reason.

Validating that the service instance was created

To validate that the service instance was created:

1. Set the INSTANCE_ID environment variable to the ID that was returned by the POST cURL command:

   export INSTANCE_ID=<ID-from-response>

2. Run the following command to get the status of the service instance:

   curl --request GET \ 
     --url "https://${CPD_ROUTE}/zen-data/v3/service_instances/${INSTANCE_ID}" \ 
     --header "Authorization: Bearer ${AUTH_TOKEN}" \ 
     --header 'Content-Type: application/json'

   • If the request was successful, the command returns the following HTTP response code: 200
     Find the provision_status parameter in the JSON response.

     • If the value is RUNNING, the service instance was successfully created.
     • If the value is PROVISION_IN_PROGRESS, wait a few minutes and run the command again.
     • If the value is FAILED, review the pod logs for the ibm-cognos-addon-sp-deployment-*, ibm-ca-operator-controller-manager-*, zen-core-api, and zen-watcher pods for possible causes.
   • If the request was not successful, use the HTTP response code to determine the reason.

What to do next