DB2 clients

Because Trade 6.1 uses the DB2 universal JDBC Type 4 driver, you do not need to configure the DB2 clients on the application server systems any more (as was needed for previous versions of Trade). If we encounter issues when accessing the database, follow these steps to resolve the connection problems.

1. Log on to the application server machine (pt) as the DB2 instance owner and start a db2 shell.

2. Using this shell, catalog the remote database server db (thus creating a local node representing it) by using the following command:

   db2 catalog tcpip node <my_local_node> remote <db2_server_hostname> server <port_from_the_services_file_on_my_OS_(50000)>

   In our case, the correct command was:

   db2 catalog tcpip node pt remote brazos server 50000

3. Catalog the remote database ptradedb:

   db2 catalog database ptradedb as ptradedb at node <my_local_node>

   In our case, the correct command was:

   db2 catalog database ptradedb as ptradedb at node pt

4. Verify the database connectivity from the DB2 client machine (pt):

   db2 connect to tradedb user <db_user> using <password>

   In our case, the following command displayed the information shown in Example 10-7:

   db2 connect to ptradedb user db2rcli using <password>

   Example 10-7 Database connectivity from DB2 clients to DB2 server

   Database Connection Information 
   Database server        = DB2/AIX64 9.1.0 
   SQL authorization ID   = DB2RCL1 
   Local database alias   = PTRADEDB
   

Next