After the Planning Analytics service is installed,
an IBM® Cloud Pak for Data administrator must provision an
instance of Planning Analytics.
Before you begin
You must have sufficient resources to provision and run the Planning Analytics service, as described by the following deployment
recommendations.
- Supported storage classes
- Network file sytem (NFS), OpenShift Container Storage (ocs-storagecluster-cephfs), Portworx
(portworx-shared-gp3)
- Minimum disk size, Planning Analytics Workspace
- 20 GB
- Minimum disk size, Planning Analytics database (TM1)
- 20 GB
- Recommended resources, Planning Analytics database
(TM1)
- 8 - 256 GB, 8 - 64 cores
About this task
Create an instance of the Planning Analytics service
so that users can interact with the Planning Analytics
interface.
Procedure
To create a service instance:
-
Log in to Cloud Pak for Data as an
administrator.
- From the toolbar, click the Services icon.
- Click the Planning Analytics tile on the Cloud Pak for Data services catalog.
- On the Planning Analytics page, click
Instances.
- Click Configure.
- On the Instance details page, enter an Instance
name for this instance of Planning Analytics.
The name you assign to the instance is also used as the default name for your Planning Analytics internal TM1 database. You can specify a unique
internal TM1 database name later during later during the provisioning procedure.
Optionally, enter a description for the instance.
- Click Next.
- On the Planning Analytics Workspace page, select the storage
class to use for the Planning Analytics Workspace instance.
Note: The only storage classes supported in Planning Analytics
are Network file system (NFS), OpenShift Container Storage (ocs-storagecluster-cephfs), and Portworx
(portworx-shared-gp3). You must use one of these classes.
- Specify the Disk size storage capacity for Planning Analytics Workspace.
- On the TM1 database configuration page, choose which type of TM1
database that Planning Analytics Workspace connects to: internal or
external.
Note: The the following limitations apply to the internal TM1 database on IBM Cloud Pak for Data:
- no ODBC support
- you can provision a single TM1 database
- the internal TM1 database is limited to 256 GB memory
- the internal TM1 database cannot be used in combination with an external TM1 database
The internal TM1 database is recommended only for non-production environments.
If you choose to connect to a TM1 database external to IBM Cloud Pak for
Data, complete these configuration items.
- Enter the TM1 Admin Server URI.
- To enable access to TM1 Web, enter the IBM Planning Analytics Spreadsheet
Service URI.
- If your external TM1 database is configured to use SSL, select the Enable
SSL Certificate option and paste the contents of the SSL certificate authority into the
text box. See Custom SSL Certificates for Planning Analytics for details on
configuring SSL certificates for the TM1 database.
If you choose to connect to an internal TM1 database on IBM Cloud Pak for
Data, complete these configuration items.
- Enter a TM1 database name for the internal TM1
database.
- Specify the number of Cores and the amount of
Memory you want to allocate to the TM1 database.
- Select the storage class to use for the TM1 database. The server supports the same
storage classes as Planning Analytics Workspace: NFS, OpenShift
Container Storage (ocs-storagecluster-cephfs), and Portworx (portworx-shared-gp3).
- Specify the Disk size storage capacity for the TM1 database.
- Optionally, select the Provision IBM Planning Analytics Spreadsheet
Services option to provision TM1 Web and the Evaluation service.
- Specify the number of Cores and the amount of
Memory you want to allocate to the TM1 Web.
- Specify the number of Cores and the amount of
Memory you want to allocate to the Evaluation service.
The
Evaluation service provides a common set of spreadsheet capabilities for TM1 Web and Planning
Analytics for Excel.
- Click Next.
- Review your selections on the Summary page, then click
Create.
Results
It can take up to 60 minutes for the provisioning process to complete. You can continue to
use other services in Cloud Pak for Data while the process
completes.
What to do next
Give the appropriate users access to the instance. See Adding users in Cloud Pak for Data.