Provisioning the Cognos Analytics service

After the Cognos® Analytics service is installed, an IBM Cloud Pak® for Data administrator must provision an instance of Cognos Analytics.

Before you begin

Required permissions: To complete this task, you must have the Create service instances permission. Typically, Cloud Pak for Data administrators have this permission.

Ensure that the content store is configured. For more information, see Configuring the content store for Cognos Analytics.

Use the following table to determine which size plan to use when you create the instance. The information in the table represents the total resources that are required by all of the pods that comprise the Cognos Analytics instance. The resources can be distributed across the nodes in your cluster. However, the nodes must have sufficient capacity to run the pods.

Note: The memory and storage requirements are provided in both Gi and GB. The values in GB have been rounded up to the next whole number.

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

Plan size Minimum required resources Maximum required resources Largest pod
Fixed Minimum Across the cluster, you must have at least:
  • Cores: 6
  • Memory: 9 Gi (Approximately 10 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 5 Gi (Approximately 5.4 GB)
 At most, the instance will use:
  • Cores: 11
  • Memory: 26 Gi (Approximately 28 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 22 Gi (Approximately 24 GB)
 The largest pod requires up to:
  • Cores: 2
  • Memory: 13 Gi (Approximately 14 GB)
Small Across the cluster, you must have at least:
  • Cores: 11
  • Memory: 21 Gi (Approximately 23 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 5 Gi (Approximately 5.4 GB)
 At most, the instance will use:
  • Cores: 18
  • Memory: 49 Gi (Approximately 53 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 22 Gi (Approximately 24 GB)
 The largest pod requires up to:
  • Cores: 2
  • Memory: 13 Gi (Approximately 14 GB)
Medium Across the cluster, you must have at least:
  • Cores: 11
  • Memory: 25 Gi (Approximately 27 GB)
  • Storage: 4.2 Gi (Approximately 4.5 GB)
  • Ephemeral Storage: 5 Gi (Approximately 5.4 GB)
 At most, the instance will use:
  • Cores: 22
  • Memory: 54 Gi (Approximately 58 GB)
  • Storage: 4.2 Gi (Approximately 4.5 GB)
  • Ephemeral Storage: 22 Gi (Approximately 24 GB)
 The largest pod requires up to:
  • Cores: 2
  • Memory: 13 Gi (Approximately 14 GB)
Large Across the cluster, you must have at least:
  • Cores: 12
  • Memory: 25 Gi (Approximately 27 GB)
  • Storage: 8.2 Gi (Approximately 8.8 GB)
  • Ephemeral Storage: 7 Gi (Approximately 7.5 GB)
 At most, the instance will use:
  • Cores: 27
  • Memory: 56 Gi (Approximately 61 GB)
  • Storage: 8.2 Gi (Approximately 8.8 GB)
  • Ephemeral Storage: 37 Gi (Approximately 40 GB)
 The largest pod requires up to:
  • Cores: 2
  • Memory: 13 Gi (Approximately 14 GB)

About this task

Create an instance of the Cognos Analytics service so that users can interact with the Cognos Analytics interface.

You can only provision one instance of the Cognos Analytics service in a Red Hat OpenShift Container Platform project (Kubernetes namespace). If you want to provision additional Cognos Analytics service instances, you must configure an additional tethered project for each service instance that you want to provision.

Procedure

To create a service instance:

  1. Log in to Cloud Pak for Data as an administrator.
  2. Find the Cognos Analytics service and ensure that it is Available.
  3. From the action menu, click New instance.
  4. Select an Instance Name Space. Select either the control plane namespace or any tethered namespaces that were created after the installation. For more information, see Setting up projects (namespaces) on Red Hat OpenShift Container Platform.
  5. Select a Shared File Volume Storage class.
  6. Select a Shared Block Volume Storage class.
  7. Select the plan size for the instance.
  8. Click Next.
  9. Select the Content Manager Database connection that you previously defined.
  10. Select the Audit Database connection that you previously defined.
  11. Click Next.
  12. Update the SMTP Settings. For more details, see Specify a connection to an email server.
    1. Enter the SMTP Server Address.
    2. Enter the SMTP Port.
    3. Select the Default Sender field and type an email address for the default sender for notifications.
    4. Optionally, enter a SMTP Username and SMTP Password.
    5. If you specified a secure SMTP port, select Use TLS connection so that Cloud Pak for Data can connect with your SMTP server.

      If you specify a TLS connection, you must add a certificate so the Cognos mail client can verify trust with the mail server. For more details, see Specify a connection to an email server.

  13. Click Next.
  14. Review the summary and click Create.

Results

It can take approximately 30 minutes for the provisioning process to complete. You can continue to use other services in Cloud Pak for Data while the process completes.

For a list of the drivers that Cloud Pak for Data provisions with Cognos Analytics, refer to Cognos Analytics on Cloud: Supported Software Environments.

What to do next

Important: Limit user access to the content store. See Updating the security settings.

Give the appropriate users access to the instance. See Managing users (Cognos Analytics).