Configuring an ODBC connection

Before you install Cloud APM reports, you must configure an ODBC connection between the Tivoli® Common Reporting server and the Cloud APM Db2® machine. The purpose of this configuration is to enable Tivoli Common Reporting to retrieve the required data from the Cloud APM Db2 database by using a local Db2 client.

1. On the Tivoli Common Reporting server, connect to the Cloud APM Db2 database by using the Db2 client and catalog a node. Run the following command:

   su - local_db_instance_User 
   db2 catalog tcpip node apm_db2_node_name remote apm_db2_ip_address server apm_db2_instance_port

   Example:

   su - dbinst1
   db2 catalog tcpip node DB2_SRVR remote 123.456.789.123 server 50000

   The apm_db2_node_name must be no longer than 8 characters.
2. On the Tivoli Common Reporting server, connect to the local Db2 instance and catalog the Cloud APM Db2 WAREHOUS and DATAMART databases:

   If you want to create a connection to generate reports for the WebSphere® Applications agent, run the following command:

   su - local_db_instance_User db2 catalog db WAREHOUS as WAREHOUS at node apm_db2_node_name

   Example:

   su - dbinst1
   db2 catalog db WAREHOUS as WAREHOUS at node DB2_SRVR

   If you want to create a connection to generate reports for the Synthetic Playback agent or the Response Time Monitoring Agent, you must catalog the Db2 DATAMART. Run the following command:

   su - db2inst1
   db2 catalog db DATAMART as DATAMART at node apm_db2_node_name

   Example:

   su - dbinst1
   db2 catalog db DATAMART as DATAMART at node DB2_SRVR

   If you're using custom database names instead of the default database names WAREHOUSE and DATAMART, catalog WAREHOUS and DATAMART as shown here:

   su - local_db_instance_User
   db2 catalog db CUSTOM_WAREHOUS_DBNAME as WAREHOUS at node apm_db2_node_name
   db2 catalog db CUSTOM_DATAMART_DBNAME as DATAMART at node apm_db2_node_name