Add vertical cluster members to a static cluster

 

+

Search Tips   |   Advanced Search

 

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

To add a vertical cluster member to the clustered environment:

1. Access the administrative console on the deployment manager...
   http://DmgrHost:9049/ibm/console

2. For WAS v6.1, click...
   Servers | Clusters | cluster_name | Cluster members

   For WAS v7.0, click...

   Servers | Clusters | WebSphere appserver clusters | cluster_name | Cluster members

3. Click New to create the cluster member.

   1. Define the name of cluster member.

      Do not use spaces in the cluster member name.

   2. Select an existing node where WebSphere Portal is installed.

   3. Check the box Generate Unique HTTP Ports.

   4. Click Add Member and then click Next to view the summary.

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

4. Click Finish, and save the changes.

   • The new cluster topology can be viewed from...
     Servers | Cluster Topology

     If using WAS v7.0, the new cluster topology can be viewed from...

     Servers | Clusters | Cluster Topology

   • The Servers > Application Servers view will list the new server cluster members.

     If using WAS v7.0, the Servers > Server Types > WebSphere appservers view will list the new server cluster members.

5. To enable cache replication:

   1. From the deployment manager Administrative Console, navigate to...
      Servers | Application servers

      ...and then click the new vertical cluster member(s). If using WAS v7.0, navigate 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 Push only from the Replication type drop-down menu.

   6. Click OK.

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

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

   1. Run...
      cd profile_root/ConfigEngine
      ConfigEngine.bat cluster-node-config-vertical-cluster-setup -DServerName=unique vertical cluster servername -DWasPassword=password

      ...where unique vertical cluster servername is generated by the Deployment Manager when the vertical cluster member is created.

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

7. Access the Web Content Management content through an external Web server:

   1. Log on to the deployment manager administrative console.

   2. Select Environment > WebSphere Variables.

   3. From the Scope drop-down menu, select the Node=nodename, Server=servername option to narrow the scope of the listed variables, where Node=nodename is the node that contains the appserver.

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

   5. Update the WCM_PORT variable with the port number used to access the WebSphere Portal server through the Web server or On Demand Router.

   6. To synchronize the node with the deployment manager:

      1. Select System Administration > Nodes.

      2. Select the node that you want to synchronize from the list.

      3. Click Full Resynchronize.

   7. Log off of the deployment manager administrative console.

8. Save changes and resynchronize the nodes.

   1. In the administrative console for the deployment manager, click Save on the task bar, and save your administrative configuration.

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

9. Regenerate the Web server plug-in.

   1. Regenerate the Web server plug-in using the deployment manager administrative console.

   2. For a remote Web server, copy the updated plug-in configuration file (plugin-cfg.xml) to the Web server's plug-in configuration directory.

10. Stop and start the Web server.

Parent topic:

Choose the type of vertical cluster to create on Windows

---