Configuring the reporting data source in IBM Cognos BI

When you publish cube packages for your first monitor model, a reporting data source named WBMONITOR_DB is automatically created in IBM® Cognos® BI. The WBMONITOR_DB data source is used to connect to the MONITOR database for dimensional reporting.

About this task

The WBMONITOR_DB data source is configured based on the values copied from the WebSphere® Application Server JDBC data source named Monitor_database.

If you cannot publish cube packages because of database connectivity issues, or if you change the user name or password for the IBM Business Monitor database, you must reconfigure the WBMONITOR_DB data source connection using the IBM Cognos Administration client. Alternatively, you can delete the WBMONITOR_DB data source in the IBM Cognos Administration client and republish a cube package from the IBM Business Monitor administrative console, using the Manage Cognos Cubes page, to automatically regenerate the WBMONITOR_DB data source based on the latest configuration values in the WebSphere Application Server JDBC data source named Monitor_database.

Procedure

  1. Start the IBM Cognos Administration client at http://host_name:port_number/p2pd/servlet/dispatch/ext.
  2. Go to IBM Cognos Administration > Configuration > Data Source Connections > WBMONITOR_DB. From there, you can configure and test the connection, and edit the user name and password.
    Tip: When you are testing the WBMONITOR_DB connection, you should see two Succeeded messages.
    • The first message is of the type "IBM DB2 / Compatible" (or "Oracle / Compatible" or "SQL Server / Compatible"). This message is for the connection that uses the native database client. This connection is required to publish cube packages.
    • The second message is of the type " / Dynamic." This message is for the Type 4 JDBC connection. This connection is required to run IBM Cognos BI reports.
    If either of these connection types show Failed, edit the configuration or sign-on information and retest. You can safely ignore failures for other connection types.