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.
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.
The MONITOR and COGNOSCS databases can be located on the same server as the IBM Business Monitor server or on a different server. For profile creation to create the databases automatically, your database server must be local to the machine where you run the Profile Management Tool or the manageprofiles command. Otherwise, use the database script files to create the databases. Also use the database script files 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.
If you want to
configure clustering, your DB2 for z/OS system must be
running in data-sharing mode.
Database scripts
When you create a stand-alone or deployment manager profile, database scripts are generated that match the values entered during profile creation, ensuring that names are consistent between the IBM Business Monitor server and the IBM Business Monitor database.
- Configure the values using the database design tool (DbDesignGenerator) that is installed with the IBM Business Monitor server. One advantage of using the database design tool is that you can design the MONITOR database, the IBM Cognos BI database, the Business Space database, and the databases for the messaging engines for IBM Business Monitor and the common event infrastructure (CEI) all at the same time. See Creating or configuring database scripts using the database design tool for instructions.
- Configure the values manually. See Configuring MONITOR database scripts manually for instructions.
After the database scripts are generated or customized, run the scripts using the procedures described in Installing the MONITOR database manually.
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.
- Create the script using the database design tool (DbDesignGenerator). See Creating or configuring database scripts using the database design tool for instructions.
- Create the tables manually. See Creating messaging engine tables manually for instructions.
For DB2 for z/OS, you must edit
the messaging engine database scripts to either make each service
integration (SI) bus database name unique or make their table spaces
unique.
Business Space tables
For dashboards, you must also configure the Business Space tables, using either the scripts that were generated during stand-alone profile creation or the database design tool. For more information, see Configuring Business Space database tables.
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 MONITOR database environment and Configuring IBM Cognos BI security.