IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Prepare connectivity for the DB2 client with a JDBC Type 2 driver

To prepare connectivity for the DB2 client if the JDBC Type 2 driver is to be used. If you are planning to use the JDBC Type 2 driver, whether the DB2 RDBMS is located on the local server or on a different (remote) server.

If you will be using the JDBC type 4 driver (which is the default setting), this procedure is not mandatory.

  1. Log in as a user with dba privileges, for example: db2inst1.

    For convenience purposes, you might want to log in as root. In the following steps, you are executing a script that prompts for the password multiple times. This can be avoided if you run it as root.

  2. Catalog the TCP/IP node pointing to the DB2 RDBMS server node:

    db2 catalog tcpip node db2node remote Remote_Server server db2_listening_port
    For example, to connects the client with na RDBMS server named ghost, which has the node name or alias ims_db2 and uses port 50000::
    db2 catalog tcpip node ims_db2 remote ghost server 50000

  3. Catalog the database on the node created:

    db2 catalog db database_name at node db2_node 
    This must be the database name to be used for the Managing Server. For example, to catalog the octigate database on the ims_db2 node, use the following command:
    db2 catalog db octigate at node ims_db2 

  4. Run the following command:
    db2 terminate


Parent topic:

Prepare an existing DB2 environment

+

Search Tips   |   Advanced Search