Creating a service instance for Cognos Analytics from the web client

After you install Cognos Analytics, you must create at least one Cognos Analytics service instance. Each service instance must be in a different Red Hat® OpenShift® Container Platform project. You can create a service instance in the operands project or in a project that is tethered to the operands project. If you are a Cloud Pak for Data user, you can use the web client to create service instances. The web client guides you through the process of creating service instances.

Who needs to complete this task?
To create a service instance from the web client, you must have the Create service instances permission in Cloud Pak for Data.
When do you need to complete this task?
Complete this task only if you want to create a service instance from the web client.
Alternative methods for creating a service instance

Before you begin

This task assumes that the following prerequisites are met:

Prerequisite Where to find more information
Cognos Analytics is installed. If this task is not complete, see Installing Cognos Analytics.
The content store is configured. You can also use the content store for your audit content. If this task is not complete, see Configuring the content store for Cognos Analytics.

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

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 are rounded up to the next whole number.
Plan size Minimum required resources Maximum required resources Largest pod
Fixed Minimum Across the cluster, you must have at least:
  • Cores: 10
  • Memory: 40 Gi (Approximately 42 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 22 Gi (Approximately 24 GB)
 At most, the instance uses:
  • Cores: 10
  • Memory: 40 Gi (Approximately 42 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 22 Gi (Approximately 24 GB)
 The largest pod requires up to:
  • Cores: 2.6
  • Memory: 13 Gi (Approximately 14 GB)
Small Across the cluster, you must have at least:
  • Cores: 9.4
  • Memory: 40.5 Gi (Approximately 43 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 21.6 Gi (Approximately 23 GB)
 At most, the instance uses:
  • Cores: 16
  • Memory: 57 Gi (Approximately 61 GB)
  • Storage: 2.2 Gi (Approximately 2.4 GB)
  • Ephemeral Storage: 37.2 Gi (Approximately 39.9 GB)
 The largest pod requires up to:
  • Cores: 2.6
  • Memory: 13 Gi (Approximately 14 GB)
Medium Across the cluster, you must have at least:
  • Cores: 9.4
  • Memory: 40.5 Gi (Approximately 43 GB)
  • Storage: 4.2 Gi (Approximately 4.5 GB)
  • Ephemeral Storage: 21.6 Gi (Approximately 23 GB)
 At most, the instance uses:
  • Cores: 18
  • Memory: 75 Gi (Approximately 80 GB)
  • Storage: 4.2 Gi (Approximately 4.5 GB)
  • Ephemeral Storage: 47.6 Gi (Approximately 51 GB)
 The largest pod requires up to:
  • Cores: 2.6
  • Memory: 13 Gi (Approximately 14 GB)
Large Across the cluster, you must have at least:
  • Cores: 16
  • Memory: 77 Gi (Approximately 82.6 GB)
  • Storage: 8.2 Gi (Approximately 8.8 GB)
  • Ephemeral Storage: 57 Gi (Approximately 61 GB)
 At most, the instance uses:
  • Cores: 25
  • Memory: 103 Gi (Approximately 110 GB)
  • Storage: 8.2 Gi (Approximately 8.8 GB)
  • Ephemeral Storage: 103 Gi (Approximately 110 GB)
 The largest pod requires up to:
  • Cores: 2.6
  • 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 provision only one instance of the Cognos Analytics service in a Red Hat OpenShift Container Platform project (Kubernetes namespace). If you want to provision extra Cognos Analytics service instances, you must configure an extra 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 make sure 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 Tethering projects to the IBM Cloud Pak® for Data control plane.
  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. Select the Crypto Conformance FIPS option for your instance, then click Next.
  9. Select the Content Manager Database connection that you previously defined.
  10. Select the Audit Database connection that you previously defined, then click Next.

    You can use the same database connection as the one that you selected for the Content Manager Database.

  11. Update the SMTP Settings. For more information, 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. Optional: 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 information, see Specify a connection to an email server.

  12. Click Next.
  13. 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.
You must give users access to the service instance. For more information, see Managing users (Cognos Analytics).