The Cognos
Analytics content store is a database
that is used to store configuration data, global settings, data server connections, and
product-specific content. You can also use this database to store audit content.
Before you begin
The Cognos
Analytics service must be configured to
reference or store content in an external content store. Valid content store databases are IBM
Db2 Database, Microsoft SQL
Server, and Oracle.
If you want to use a content store that is located outside of Cloud Pak for Data such as Db2, Microsoft SQL
Server, or Oracle, refer to Guidelines for creating the content store.
If you want to use the Db2 service on
Cloud Pak for Data and the Db2 service is not installed, complete the steps in the
Db2 Advanced Edition on Cloud
Pak for Data topic.
Note: If you configured the
Db2 database
server to use
Oracle compatibility mode, you
must temporarily disable the
Oracle
compatibility mode before you create the content store. After you create the content store,
configure the
Db2 database server to use
Oracle compatibility mode again. For more
information, see
https://www.ibm.com/support/pages/node/515565.
About this task
Each Cognos
Analytics service instance must have its own
content store. Even if you have a content store for other service instances on Cloud Pak for Data, you must create a new content store for each
specific Cognos
Analytics service instance.
Procedure
-
Collect the following details from your database administrator:
- Database name
- Deployment ID
- Username
- Password
- JDBC Connection URL
- Log in to your Red Hat®
OpenShift®
cluster.
oc login OpenShift_URL:port
-
Run the following commands from the console:
#
# USE VALUES from STEP 2
#
export NAMESPACE=<Namespace of your CPD Installation>
export DB2USERNAME=<USERNAME>
export DB2PASSWORD=<PASSWORD>
export DB2DEPLOYMENTID=<DEPLOYMENTID>
#
# Connect to DB2U Pod
#
export CMD="env DB2USERNAME=$DB2USERNAME DB2PASSWORD=$DB2PASSWORD bash"
oc exec -ti c-$DB2DEPLOYMENTID-db2u-0 -n $NAMESPACE -- $CMD
-
From the Db2 container, run the following
commands from the console:
cd /mnt/blumeta0/home/db2inst1/sqllib
. ./db2profile
db2 CONNECT to BLUDB user $DB2USERNAME using $DB2PASSWORD
db2 UPDATE DATABASE CONFIGURATION USING APPLHEAPSZ 1024 DEFERRED;
db2 UPDATE DATABASE CONFIGURATION USING LOCKTIMEOUT 240 DEFERRED;
db2 CREATE BUFFERPOOL CMDB_08KBP IMMEDIATE SIZE 1000 PAGESIZE 8K;
db2 CREATE BUFFERPOOL CMDB_32KBP IMMEDIATE SIZE 1000 PAGESIZE 32K;
db2 CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_CMDB IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32K BUFFERPOOL CMDB_32KBP;
db2 CREATE USER TEMPORARY TABLESPACE TSN_USR_CMDB IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8K BUFFERPOOL CMDB_08KBP;
db2 CREATE REGULAR TABLESPACE TSN_REG_CMDB IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8K BUFFERPOOL CMDB_08KBP;
db2 CREATE SCHEMA db2COGNOS AUTHORIZATION $DB2USERNAME;
db2 ALTER BUFFERPOOL ibmdefaultbp size 49800;
exit
Your database is created. Complete the next steps to connect to a data source.
-
Connect to a IBM
Db2 Database, Microsoft SQL
Server, or Oracle data source:
Note: IBM
Db2 Warehouse database is not a
supported data source.
-
Log in to the Cloud Pak for Data web client.
-
From the menu, select Connections.
-
Click New connection.
-
Enter a name and a description for the connection.
-
Select Db2, Microsoft SQL
Server, or Oracle for the Connection
type.
-
On the New connection page, enter the connection information.
For example, specify the following connection information:
- Host
- Port
- Database name
- Username
- Password
Important: If you selected Db2 for
the Connector on Cloud Pak for Data,
you must set Username and Password Security Mechanism to Clear
text.
-
To test the connection, click Test connection on the New
connection page.
-
Click Create.
The connection is saved.