IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse solution using DB2 for Linux, UNIX, and Windows > Step 2: Install and configure communications for the Warehouse Proxy Agent

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

---

Cataloging a remote data warehouse

Perform this procedure on a computer where a DB2 for Linux, UNIX and Windows client is installed to enable communication between the client and a remote DB2 for Linux, UNIX and Windows server where the data warehouse is installed.

For example, use this procedure to set up communication to a remote DB2 data warehouse server from:

• The DB2 for Linux, UNIX and Windows client on the computer where the Tivoli Enterprise Portal Server is installed (on any platform)

• The DB2 client on a Windows computer where a Warehouse Proxy Agent installed

Do not perform this procedure on the computer where the data warehouse (DB2 server) is installed or on a computer where there is no DB2 client (for example, on a computer where a Type 4 DB2 for Linux, UNIX and Windows JDBC driver is used to communicate with the remote DB2 server).

Complete the following steps on the computer where the DB2 for Linux, UNIX and Windows client is installed (the local computer):

1. Catalog the remote TCP/IP node where the warehouse database is installed:

   db2 catalog tcpip node node_name remote host_name server port
   db2 terminate

   where the indicated variables identify the location and port of the remote DB2 for Linux, UNIX and Windows server. For host_name, specify the host name or IP address. The default port for a DB2 server is 60000. For example:

   db2 catalog tcpip node amsc2424 remote 8.53.36.240 server 60000
   db2 terminate

2. Catalog the remote Tivoli Data Warehouse database:

   db2 catalog db db_name as db_alias at node node_name
   db2 terminate

   where

   • db_name is the name of the remote warehouse database.

   • db_alias is the nickname or alias used to identify the remote warehouse database on the local computer. The local alias for the warehouse database must match the name that you specify in the configuration procedure for the portal server, Warehouse Proxy Agent, or Summarization and Pruning Agent.

   • node_name is the name of the node where the warehouse database is located.

   Example:

   db2 catalog db WAREHOUS as WAREHOUS at node amsc2424
   db2 terminate

3. Test the connection to the remote warehouse database:

   db2 connect to db_alias user user_name using user_password

   where:

   db_alias

   Is the nickname or alias used to identify the remote warehouse database on the local computer.

   user_name

   Is the user ID that the local DB2 client uses to access the warehouse database.

   user_password

   Is the password for that user_name.

   These values must match the values that you specify in the configuration procedures for the portal server, Warehouse Proxy Agent, or Summarization and Pruning Agent.

   Example:

   db2 connect to WAREHOUS user itmuser using itmpswd1

Parent topic:

Step 2: Install and configure communications for the Warehouse Proxy Agent

---

+

Search Tips   |   Advanced Search