Administration Guide

Configure Host Database

When registering host databases in LDAP, there are two possible configurations:

• Direct connection to the host databases; or,
• Connection to the host database though a gateway.

In the first case, the user would register the host server in LDAP, then catalog the host database in LDAP specifying the node name of the host server. In the second case, the user would register the gateway server in LDAP, then catalog the host database in LDAP specifying the node name of the gateway server.

As an example showing both cases, consider the following: Suppose there is a host database called NIAGARA_FALLS. It can accept incoming connections using APPN and TCP/IP. If the client can not connect directly to host because it does not have DB2 Connect, then it will connect using a gateway called "goto@niagara".

The following steps need to be done:

1. Register the host database server in LDAP for APPN connectivity. The REMOTE and INSTANCE clauses are arbitrary. The NODETYPE clause is set to "DCS" to indicate that this is a host database server.

      db2 register ldap as nfappn appn network CAIBMOML partnerlu NFLU 
         mode IBMRDB remote mvssys instance msvinst nodetype dcs
   

2. Register the host database server in LDAP for TCP/IP connectivity. The TCP/IP hostname of the server is "myhost" and the port number is "446". Similar to step 1, the NODETYPE clause is set to "DCS" to indicate that this is a host database server.

      db2 register ldap as nftcpip tcpip hostname myhost svcename 446 
         remote mvssys instance mvsinst nodetype dcs
   

3. Register a DB2 Connect gateway server in LDAP for TCP/IP connectivity. The TCP/IP hostname for the gateway server is "niagara" and the port number is "50000".

      db2 register ldap as whasf tcpip hostname niagara svcename 50000 
         remote niagara instance goto nodetype server
   

4. Catalog the host database in LDAP using TCP/IP connectivity. The host database name is "NIAGARA_FALLS", the database alias name is "nftcpip". The GWNODE clause is used to specify the nodename of the DB2 Connect gateway server.

      db2 catalog ldap database NIAGARA_FALLS as nftcpip at node nftcpip 
         gwnode whasf authentication dcs
   

5. Catalog the host database in LDAP using APPN connectivity.

      db2 catalog ldap database NIAGARA_FALLS as nfappn at node nfappn 
         gwnode whasf authentication dcs
   

After completing the registration and cataloging shown above, if you want to connect to the host using TCPIP, you connect to "nftcpip". If you want to connect to the host using APPN, you connect to "nfappn". If you do not have DB2 Connect on your client workstation, the connection will go through the gateway using TCPIP and from there, depending on whether you use "nftcpip" or "nfappn", it will connect to host using TCP/IP or APPN respectively.

In general then, you can manually configure host database information in LDAP so that each client does not need to manually catalog the database and node locally on each machine. The process follows:

1. Register the host database server in LDAP. You must specify the remote computer name, instance name, and the node type for the host database server in the REGISTER command using the REMOTE, INSTANCE, and NODETYPE clauses respectively. The REMOTE clause can be set to either the host name or the LU name of the host server machine. The INSTANCE clause can be set to any character string that has eight characters or less. (For example, the instance name can be set to "DB2".) The NODE TYPE clause must be set to "DCS" to indicate that this is a host database server.
2. Register the host database in LDAP using the CATALOG LDAP DATABASE command. Any additional DRDA parameters can be specified by using the PARMS clause. The database authentication type should be set to "DCS".