Home

 

Add subsequent nodes to a cluster

 

+

Search Tips   |   Advanced Search


Overview

You must already have a cluster with at least one member. Perform this task on each node that you want to add to the cluster.

You do not need to create server instances on the subsequent nodes in a cluster. The dmgr (DM) will create new server instances as required.

Each subsequent node must be an unmanaged node before you start this task. Completing the task transforms the node into a managed, or federated, node.

Perform this task for each node that you want to add to the cluster.


Add a node to a cluster

  1. Add a subsequent node to the dmgr cell:

    1. Start WebSphere Application Server dmgr.

    2. Log into the subsequent node; that is, the node that you want to add to the cluster.

    3. Open a command prompt and change to the bin of the local WebSphere Application Server profile:

      app_server_root/profiles/profile_name/bin

      where profile_name is the name of the applicable WebSphere Application Server profile on this node.

    4. Run the addNode command to add this node to the dmgr cell:

        addnode [dmgr_host]
                [dmgr_port] 
                [-username uid]
                [-password pwd] 
                [-localusername localuid]
                [-localpassword localpwd]
        

    5. Confirm the node was successfully added to the dmgr cell...

  2. Copy the relevant JDBC files first node in the cluster to the subsequent node, placing them in the same location as the JDBC files on the first node. If, for example, you copied the db2jcc.jar file to the C:\IBM\SQLLIB on the first node, you need to copy the same file to the C:\IBM\SQLLIB in each of the subsequent nodes in the same cluster. The files to copy, depending on your database type, are:

      Option Description
      DB2 db2jcc.jar
      db2jcc_license_cu.jar sql
      Oracle ojdbc14.jar
      SQL Server sqljdbc.jar

  3. Copy the Stellent binary to the subsequent node:

    1. Copy...

      ..from the first node to the subsequent node. Set file paths identical between first and second node.

    2. (AIX and Linux only.) Add the following text to the end of the /etc/profile file on the subsequent node:

      export PATH=$PATH:<SearchInstallHome>/dcs/oiexport

      ..where <SearchInstallHome> is the full, absolute path to the where the Search feature is installed. For example:

    3. (AIX only.) Add the following text to the end of the /etc/profile file on the subsequent node:

      export LIBPATH =$LIBPATH:<SearchInstallHome>/dcs/oiexport

    4. (Linux only.) Add the following text to the end of the /etc/profile file on the subsequent node:

      export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<SearchInstallHome>/dcs/oiexport

  4. Ensure that the shared folders that are used for the features' content stores in the first node are accessible from the subsequent node: From the subsequent node, try to access the shared directories. For file paths to the shared directories, see the Data directories for features table in the Installing the first node of a cluster topic. Also, follow the steps in the Configuring shared message stores for buses topic to ensure the message stores are available to all nodes.

  5. Add additional members to an existing Lotus Connections cluster...

    1. Login to the dmgr Administrative Console and go to...

        Servers | Clusters | cluster_name | Cluster members | New

      Specify the following information about the new cluster member:

        Member name

        The name of the server instance that is created for the cluster. The dmgr will create a new server instance with this name

        Each member name in the same cluster must be unique. The admin console will prevent you from re-using the same member name in a cluster.

        Select node

        The node where the server instance resides.

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

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

    3. Click Save to save the configuration.

    4. Click...

        Server | Servers | Clusters | cluster_name | Cluster members

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

    5. On the detailed configuration page, click Port 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.

    6. Click...

        Environment | Virtual Hosts | default_host | Host Aliases | New

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

        Port:

        The port number for WC_defaulthost. For example, 9084.

      Click OK to complete the virtual host configuration.

    7. Click Save to save the configuration.

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

    9. Click System administration>Nodes,

    10. In the node list page, select all the nodes where the target cluster members reside, and then click Synchronize to perform a synchronization between the nodes.

    Optional: Create local directories for...

      LC_HOME/Data/profiles/statistic
      LC_HOME/Data/profiles/cache
      LC_HOME/Data/activities/statistic

  6. Configure IHS to connect to this node.

Repeat task for each subsequent node to add to a cluster.

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 features to fail. For more information, go to the NameNotFoundException from JNDI lookup operation Web page.

Each application server that is running profiles or activities, the local directories above need to exist on each node.


Configure IBM HTTP Server
Install a network deployment
Define IBM HTTP Server for a node
Convert a stand-alone deployment
Configure shared message stores for buses
Install IBM WebSphere Application Server