DB2 Version 9.7 for Linux, UNIX, and Windows

Registration of DB2 servers after installation

Each DB2® server instance must be registered in LDAP to publish the protocol configuration information that is used by the client applications to connect to the DB2 server instance.

About this task

When registering an instance of the database server, you must specify a node name. The node name is used by client applications when they connect or attach to the server. You can catalog another alias name for the LDAP node by using the CATALOG LDAP NODE command.

Note: If you are working in a Windows domain environment, then during installation the DB2 server instance is automatically registered in the Active Directory with the following information:

   nodename: TCP/IP hostname
   protocol type: TCP/IP

If the TCP/IP hostname is longer than 8 characters, it will be truncated to 8 characters.

The REGISTER command appears as follows:

   db2 register db2 server in ldap
      as <ldap_node_name>
      protocol tcpip

The protocol clause specifies the communication protocol to use when connecting to this database server.

When creating an instance for DB2 Enterprise Server Edition that includes multiple physical machines, the REGISTER command must be invoked once for each computer. Use the rah command to issue the REGISTER command on all computers.

Note: The same ldap_node_name cannot be used for each computer since the name must be unique in LDAP. You will want to substitute the hostname of each computer for the ldap_node_name in the REGISTER command. For example:

   rah ">DB2 REGISTER DB2 SERVER IN LDAP AS <> PROTOCOL TCPIP"

The "<>" is substituted by the hostname on each computer where the rah command is run. In the rare occurrence where there are multiple DB2 Enterprise Server Edition instances, the combination of the instance and host index can be used as the node name in the rah command.

The REGISTER command can be issued for a remote DB2 server. To do so, you must specify the remote computer name, instance name, and the protocol configuration parameters when registering a remote server. The command can be used as follows:

   db2 register db2 server in ldap
      as <ldap_node_name>
      protocol tcpip
      hostname <host_name>
      svcename <tcpip_service_name>
      remote <remote_computer_name>
      instance <instance_name>

The following convention is used for the computer name:

If TCP/IP is configured, the computer name must be the same as the TCP/IP hostname.

When running in a high availability or failover environment, and using TCP/IP as the communication protocol, the cluster IP address must be used. Using the cluster IP address allows the client to connect to the server on either computer without having to catalog a separate TCP/IP node for each computer. The cluster IP address is specified using the hostname clause, shown as follows:

   db2 register db2 server in ldap
      as <ldap_node_name>
      protocol tcpip
      hostname n.nn.nn.nn

where n.nn.nn.nn is the cluster IP address.

To register the DB2 server in LDAP from a client application, call the db2LdapRegister API.