Creating the databases

IBM® Business Monitor requires two databases, one for the IBM Business Monitor configuration and one for the IBM Cognos® Business Intelligence content store.

MONITOR and COGNOSCS databases

By default, the database for IBM Business Monitor is named MONITOR and the database for the IBM Cognos BI content store is named COGNOSCS. The MONITOR and COGNOSCS databases can be located on the same server as the IBM Business Monitor server, or on a different server.

If you have an existing IBM Cognos BI server, you do not need to create a COGNOSCS database because the content store is already defined.

Tip: If your database product is MS SQL Server, and the COGNOSCS database is remote from the IBM Cognos BI server, you must install a database client on the IBM Cognos BI server machine. See the details in the database-specific database consideration topics.

You can create the MONITOR and COGNOSCS databases by running database scripts that are populated with the required configuration settings for the databases to be created:

You can manually create the databases before profile creation. To do so, you must use the database script templates that are supplied with the installed IBM Business Monitor product. These templates contain symbolic variables that must be replaced with your actual database settings. You can run the database scripts after editing them.
You can automatically create the databases when you create a stand-alone or deployment manager profile. When you run the Profile Management Tool or the manageprofiles command to create these profiles, database scripts are generated that are populated with the database configuration values that you specified during profile creation. You can choose to automatically run the generated scripts to create the databases, or you can delay the execution of the scripts and run them later.
Important: You must choose to create the databases automatically only if your database server is local to the computer where you run the Profile Management Tool or the manageprofiles command. Otherwise, delay the execution of the scripts and manually run them later to create the databases. If you are using z/OS®, or if the database server contains multiple versions of the database or multiple database instances, you must also manually run the scripts to create the databases.
You can manually create the databases after profile creation. To do so, use the generated database scripts that are populated with the database configuration values that you specified during profile creation. If required, you can further edit the scripts before you run them.

In a network deployment environment, it is best to create the databases before starting the deployment manager and creating custom profiles.

Business Space tables

Business Space is automatically installed and configured when you create a profile.

Business Space database scripts are also generated either when you create a stand-alone profile or deployment environment. These scripts are used to configure the Business Space database tables that are required for dashboards. The Business Space database scripts are generated for the same database product as for IBM Business Monitor.

Stand-alone server

When you create a stand-alone profile, you can also automatically run the generated scripts to configure the Business Space database tables, or you can delay the execution of the scripts and run them later. If you do not choose to delay the execution of the scripts, the MONITOR and COGNOSCS databases, and Business Space tables are all automatically created as part of profile creation.

Important: You can choose to automatically configure the Business Space database and tables only if your database server is local to the computer where you run the Profile Management Tool or the manageprofiles command. Otherwise, delay the execution of the scripts and manually run them later to configure the databases and tables. If you are using z/OS, or if the database server contains multiple versions of the database or multiple database instances, you must also manually run the scripts to create the databases and tables.

By default, the Business Space database tables are created in the MONITOR database and are assigned the MONITOR schema name, but you can choose to use another database for the tables and assign a different schema name.

Network deployment environment

Business Space database scripts are not generated when you create a deployment manager or custom node profile. Instead, these scripts are generated when you create the deployment environment, and you must run them manually to configure the Business Space database tables.

By default, the Business Space database tables are created in the MONITOR database, but you can choose to use another database for the tables and assign a different schema name.

Messaging engine tables

The messaging engines for the IBM Business Monitor service integration bus and the common event infrastructure (CEI) bus require database tables. Except on z/OS, these tables can be created automatically by WebSphere® Application Server if the IBM Business Monitor database user has sufficient privileges and the option to create tables automatically is set in the service integration bus message store options. This option is set to true by default unless you are using DB2® for z/OS.

The database scripts for the messaging engine tables can also be generated by creating the tables manually. See Creating messaging engine tables manually for instructions.

Database security

When the databases are created, the runtime database user is granted privileges to administer database objects by default, which simplifies the creation of the databases and enables the IBM Business Monitor server to automatically manage the monitor model database schema when models are deployed and removed. If you must secure the databases, see Securing the database environment and Configuring IBM Cognos BI security.