Add a new node to an existing cluster.
Before you begin
You must already have a cluster with at least one member.
Ensure that you have installed IBM
® Application Server Network Deployment (Application Server option) on the new node.
If you are adding a node to a Search cluster, do not use these instructions. Instead, use the instructions in the Adding an additional Search node to a cluster
About this task
To add a node to a cluster, complete the following steps:
- Add a new node to the DM cell:
- Log into the new node.
- Open a command prompt and change to the bin directory of the local WebSphere Application Server profile:
is the name of the applicable WebSphere
Application Server profile on this node.
- Run the addNode command to add this node to the DM cell: .
addnode [dmgr_host] [dmgr_port] [-username uid] [-password pwd] [-localusername localuid] [-localpassword localpwd]
where dmgr_host is the host name of the Deployment Manager, dmgr_port is the SOAP port of the deployment manager (the default is 8879), uid and pwd are the DM administrator username and password, and localuid and localpwd are the username and password for the node's WebSphere Application Server administrator.
- Open the addNode.log file and confirm that the node was successfully added to the DM cell. The file is stored in the following location:
- Copy the relevant JDBC files from the DM node to this node, placing them in the same location as the JDBC files on the DM. If, for example, you copied the db2jcc.jar file from the C:\IBM\SQLLIB directory on the DM, you need to copy the same file to the C:\IBM\SQLLIB directory on this node. See the following table to determine which files to copy. See the following table to determine which files to copy:
Table 1. JDBC files
|Database type||JDBC files|
- Ensure that the shared folders that are used for the application content stores in the cluster are accessible from the new node: from the new node, try to access the shared directories.
- Add additional members to an existing IBM Connections cluster:
- Login to the Deployment Manager Integration Solutions Console.
- Click Servers -> Clusters -> cluster_name -> Cluster members -> New. Specify the following information about the new cluster member:
The name of the server instance that is created for the cluster. The DM will create a new server instance with this name.Select node
Note: Each member name in the same cluster must be unique. The Integration Solutions Console will prevent you from re-using the same member name in a cluster.
The node where the server instance resides.
Click Add Member
to add this member to the cluster member list.
- Click Next to go to the summary page where you can examine detailed information about this cluster member. Click Finish to complete this step or click Previous to modify the settings.
- Click Save to save the configuration.
- Click Server -> Servers -> Clusters -> cluster_name -> Cluster members. In the member list, click the new member that you added in the previous step.
- On the detailed configuration page, click Ports to expand the port information of the member. Make a note of the WC_defaulthost and WC_defaulthost_secure port numbers. For example, the WC_defaulthost port number is typically 9084, while the WC_defaulthost_secure port number is typically 9447.
- Click Environment -> Virtual Hosts -> default_host -> Host Aliases -> New. Enter the following information for the host alias for the WC_defaulthost port:
The IP address or DNS host name of the node where the new member resides.Port:
The port number for WC_defaulthost. For example, 9084.
to complete the virtual host configuration.
- Click Save to save the configuration.
- Repeat the previous two sub-steps to add the host alias for the WC_defaulthost_secure port.
- Click System administration -> Nodes.
- In the node list page, select all the nodes where the target cluster members reside and then click Synchronize. This action performs a synchronization between the nodes.
What to do next
HTTP Server to connect to this node. For more information, see the Configuring IBM HTTP Server
and Defining IBM HTTP Server for a node
Repeat this task for each new node that you want to add to a cluster.
only) If you have installed the Search application on the new node, configure the path variables to point to that application. For more information, see the Setting AIX or Linux path variables for Search
If you experience interoperability failure, you might be running two servers on the same host with the same name. This problem can cause the Search and News applications to fail. For more information, go to the NameNotFoundException from JNDI lookup operation
Parent topic: Optional post-installation tasks
Configuring IBM HTTP Server
Copying Search conversion tools to local nodes
Installing IBM WebSphere Application Server
Defining IBM HTTP Server
Adding an additional Search node to a cluster