Add a node to an existing cluster

Overview

Install IBM WebSphere Application Server Network Deployment (Application Server option) on the new node.

If we are adding a node to a Search cluster, do not use these instructions. Instead, use the instructions in the Add an additional Search node to a cluster topic. (Note: I could not find v5 version of this topic)

Although the IBM Cognos Business Intelligence server is managed by the same dmgr as IBM Connections, we cannot add that node to the Connections cluster.

Add a node to a cluster

1. Add a node to the dmgr cell:

   1. Log on to the new node and run...

      cd app_server_root/profiles/profile_name/bin
      ./addnode dmgr_host dmgr_port -username wasadmin -password password [-localusername localuid] [-localpassword localpwd]

      localuid and localpwd are the user name and password for the WAS administrator of the node

   2. After completion, open...

      app_server_root/profiles/profile_name/log/addNode.log

      ...confirm the node was successfully added to the dmgr cell.

   3. Copy relevant JDBC files from the dmgr node to this node, placing them in the same location as the JDBC files on the dmgr.

      If, for example, you copied db2jcc.jar from /opt/IBM/sqllib on the dmgr, copy the same file to /opt/IBM/sqllib on this node.

      Files to copy:

      Database type	JDBC files
      DB2	db2jcc.jar db2jcc_license_cu.jar sql
      Oracle	ojdbc6.jar
      SQL Server	sqljdbc4.jar

   4. Ensure the shared folders 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.

2. Add additional members to an existing Connections cluster:

   1. Log on to the dmgr Integration Solutions Console.

   2. Click...
      Servers | Clusters | cluster_name | Cluster members | New

      ...where...

      Member name

      The name of the server instance created for the cluster. The DM creates a server instance with this name. Each member name in the same cluster must be unique. The Integration Solutions Console prevents you from reusing the same member name in a cluster.

      Select node

      The node where the server instance is located.

      Click Add Member to add this member to the cluster member list.

   3. Click Next to go to the summary page where we can examine detailed information about this cluster member.

      Click Finish to complete this step or click Previous to modify the settings.

   4. Click Save to save the configuration.

   5. Click...
      Server | Servers | Clusters | cluster_name | Cluster members

      In the member list, click the new member added in the previous step.

   6. 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.

   7. Click...
      Environment | Virtual Hosts | default_host | Host Aliases | New

      ...and enter the following information for the host alias for the WC_defaulthost port...

      Host name

      The IP address or DNS host name of the node where the new member is located.

      Port:

      The port number for WC_defaulthost. For example, 9084.

      Click OK to complete the virtual host configuration.

   8. Click Save to save the configuration.

   9. Repeat the previous two sub-steps to add the host alias for the WC_defaulthost_secure port.

   10. Click...
       System administration | Nodes

   11. In the node list page, select all the nodes where the target cluster members are located and then click Synchronize.

3. Review the configuration of the application server added to the cluster.

   JVM settings need to be adapted to equal the other existing application servers in the cluster. Refer to Review the JVM heap size. Other configuration settings to consider reviewing include webcontainer threads and session timeouts settings.

What to do next

Configure IBM HTTP Server to connect to this node...

• Configure IBM HTTP Server
• Define IBM HTTP Server

Repeat this task for each new node to add to a cluster.

If we 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. See NameNotFoundException from JNDI lookup operation web page.

Refer to Configure CCM for newly added nodes to perform the required steps for making Filenet work well with Connections Content Manager. Also, perform additional configuration steps to add the Search application to a new node.

Parent topic:
Post-installation tasks

Related:
Configure IBM HTTP Server
Copy Search conversion tools to local nodes
Make search-related configuration changes to newly added nodes
Define IBM HTTP Server