You must establish connectivity from the warehouse agent sites to the warehouse sources and targets.
To access your warehouse sources and targets, you need the Data Warehouse Center ODBC drivers or DB2 Connect, connectivity software (such as TCP/IP), and database clients on your warehouse agent sites.
Data Warehouse Center ODBC drivers for several non-DB2 databases are installed when you install a warehouse agent. Your DB2 Universal Database CD-ROM also includes ODBC drivers for DB2.
Install the connectivity products that are needed to access remote warehouse sources and targets. This might include TCP/IP or NetBIOS customization, SNA Client for Windows NT, or SNA Server for Windows NT.
You need to install the connectivity products on the warehouse server (if you are using a local warehouse agent) and on your warehouse agent sites. For example, you can access a DB2 family database through TCP/IP or NetBIOS. You can also access a DB2 for MVS/ESA database through TCP/IP or NetBIOS if a DB2 Connect gateway is accessible on the network with connectivity to the host database that you need.
For more information about non-DB2 source databases and defining warehouse sources and targets within the Data Warehouse Center, see the Data Warehouse Center Administration Guide.
See the Data Warehouse Center Administration Guide for connectivity requirements when you are using IBM Classic Connect to access IMS databases or VSAM data sets on MVS.
Install the client component of a remote non-DB2 database on your warehouse agent sites and on your warehouse server (if you are using a local warehouse agent). See the Data Warehouse Center Administration Guide for more information, or refer to the documentation for the database.
For the DB2 family of databases, the necessary DB2 client function is included with DB2 Universal Database.
Test TCP/IP connectivity between the following workstations:
To test the connectivity, enter ping hostname where hostname is the TCP/IP host name of the warehouse server, Data Warehouse Center administrative client, or warehouse agent site. On AIX and Windows 32-bit operating systems, you will see several messages in the window that verify the TCP/IP connection, similar to those shown in Figure 1.
Figure 1. Sample response from PING command
[C:\]ping dgntserv2.stl.ibm.com PING dgntserv2.stl.ibm.com: 56 data bytes 64 bytes from 9.112.46.127: icmp_seq=1. time=0. ms 64 bytes from 9.112.46.127: icmp_seq=2. time=0. ms 64 bytes from 9.112.46.127: icmp_seq=3. time=0. ms 64 bytes from 9.112.46.127: icmp_seq=4. time=0. ms ----dgntserv2.stl.ibm.com PING Statistics---- 5 packets transmitted, 4 packets received, 20% packet loss round-trip (ms) min/avg/max = 0/0/0
On the Solaris Operating Environment, the ping command will return the following information:
host is alive
For a workstation with OS/2 or AIX warehouse agents, make sure that you can ping the workstation using only the host name without the local domain name. For example, enter ping dgntserv2 instead of ping dgntserv2.stl.ibm.com. You might need to add an entry in the /etc/hosts file such as:
123.45.67.89 dgntserv2 dgntserv2.stl.ibm.com
Test ODBC connectivity between any non-DB2 database clients and servers. If you are using a Windows NT warehouse agent, verify that connectivity can be established as a Windows NT system process.