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 it. When registering an instance of the database server, you need to 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.
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 Universal Database EEE that includes multiple physical machines, the REGISTER command must be invoked once for each machine. The rah command is used to issue the REGISTER command on all machines.
| Note: | The same ldap_node_name cannot be used for each machine
since the name must be unique in LDAP. You will want to substitute the
hostname of each machine 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 machine where the rah command is run. In the rare occurrence where there are multiple DB2 Universal Database EEE instances, the combination of the instance and host index may 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:
When running in a high availability or fail-over 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 machines without having to catalog a separate TCP/IP node for each machine. The cluster IP address is specified using the hostname parameter, 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.
Refer to the Command Reference for additional information on the REGISTER command.