Add vertical cluster members to a dynamic cluster on Linux

We can add vertical cluster members to share the workload demands of the cluster across multiple members running on the same physical machine.

Add a vertical cluster member to the clustered environment

1. Open a browser and enter http://DM01:9060/ibm/console in the address bar to access the dmgr console, where DM01 is the dmgr node or host name. The port number might differ based on the installation.

2. To allow vertical clusters on the dynamic cluster:

   1. Navigate to Servers > Clusters > Dynamic clusters and select the appropriate dynamic cluster.

   2. Select the Allow more than one instance to start on the same node check box under Vertical stacking of instances on node.

   3. Enter a new value in the Number of instances text box to determine the number of vertical cluster members allowed on each node.

   4. Click Apply and then click Save to save the changes to the master configuration.

   5. Optional: Navigate to Servers > Clusters > Dynamic Clusters > clustername > Cluster Members view to view the list of new cluster members.

   • The new cluster topology can be viewed from the Servers > Clusters > Cluster Topology view.

   • The Servers > Server Types > WebSphere appservers view lists the new server cluster members.

   Update the virtual host entries for the new port created when adding a cluster member. We can do this by updating the default_host virtual host in the WAS admin console and adding a new alias entry for the port number (use an "*" wildcard character for the host name). See Configure virtual hosts for information.

3. To enable cache replication:

   1. From the dmgr console, go to Servers > Server Types > WebSphere appservers and then click the new vertical cluster member(s).

   2. Click Dynamic cache service under Container services.

   3. Change Cache size to 3000 entries.

   4. Check the Enable cache replication check box.

   5. Select NOT_SHARED from the Replication type drop-down menu.

   6. Click OK.

   7. Click Save to save the changes to the master configuration.

4. Complete the following steps on each vertical cluster member to clean up the server-scoped resources, caches, and resource providers:

   1. On the node where you created the vertical cluster...
      ./ConfigEngine.sh cluster-node-config-vertical-cluster-setup -DServerName=unique vertical cluster servername -DWasPassword=foo

      unique vertical cluster servername is the name you specified when you created the cluster member.

   2. Restart the vertical cluster member referenced in the cluster-node-config-vertical-cluster-setup task.
      

5. To access the WCM content through an external web server:

   1. Log on to the dmgr console.
      

   2. Select Environment > WebSphere Variables.
      

   3. From the Scope drop-down menu, select the option...
      Node=nodename, Server=servername

      ...where Node=nodename is the node containing the portal application server.
      

   4. Update the WCM_HOST variable with the fully qualified host name used to access the portal server through the web server or On Demand Router.
      

   5. Update the WCM_PORT variable with the port number used to access the portal server through the web server or On Demand Router.
      

   6. Update the WCM_HOST and WCM_PORT variable for each additional portal server that already exists in the cluster.

   7. Synchronize the node with the dmgr:

      1. Select System Administration > Nodes.

      2. Select the node to synchronize from the list.

      3. Click Full Resynchronize.

   8. Log off of the dmgr console.

6. Save the changes and resynchronize the nodes.

   1. In the dmgr console, click Save on the task bar, and save the administrative configuration.

   2. Select System Administration > Nodes, select the node from the list, and click Full Resynchronize.

7. Stop and start the web server.

Parent: Choose the type of vertical cluster to create on Linux