Add vertical cluster members to a dynamic cluster on Windows
You can add vertical cluster members to share the workload demands of cluster across multiple members running on the same physical machine.
Add a vertical cluster member to clustered environment:
- Open a browser and enter http://DM01:9060/ibm/console in the address bar to access the administrative console on the dmgr, where DM01 is the dmgr node or host name. The port number might differ based on installation.
- Allow vertical clusters on dynamic cluster:
- Navigate to Servers -> Clusters -> Dynamic clusters and select the appropriate dynamic cluster.
- Select the Allow more than one instance to start on the same node check box under Vertical stacking of instances on node.
- Enter a new value in the Number of instances text box to determine the number of vertical cluster members allowed on each node.
- Click Apply and then click Save to save the changes to the master configuration.
- 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 application servers view will list the new server cluster members.
You must 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 for information.
- Complete the following steps to enable cache replication:
- From the dmgr console, navigate to Servers -> Server Types -> WebSphere application servers and then click the new vertical cluster member(s).
- Click Dynamic cache service under Container services.
- Change Cache size to 3000 entries.
- Check the Enable cache replication check box.
- Select NOT_SHARED from the Replication type drop-down menu.
- Click OK.
- Click Save to save changes to the master configuration.
- Complete the following steps on each vertical cluster member to clean up the server-scoped resources, caches, and resource providers:
- Run the ConfigEngine.bat cluster-node-config-vertical-cluster-setup -DServerName=unique vertical cluster servername -DWasPassword=foo from the WP_PROFILE/ConfigEngine, where unique vertical cluster servername is the name you specified when you created the cluster member.
- Restart the vertical cluster member referenced in the cluster-node-config-vertical-cluster-setup task.
- Access the Web Content Manager content through an external Web server:
- Log on to the dmgr console.
- Select Environment -> WebSphere Variables.
- 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 application server.
- 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.
- Update the WCM_PORT variable with the port number used to access the WebSphere Portal server through the Web server or On Demand Router.
- To synchronize the node with the dmgr:
- Select System Administration -> Nodes.
- Select the node that you want to synchronize from the list.
- Click Full Resynchronize.
- Log off of the dmgr console.
- Save changes and resynchronize the nodes.
- In the administrative console for the dmgr, click Save on the task bar, and save administrative configuration.
- Select System Administration -> Nodes, select the node from the list, and click Full Resynchronize.
- Stop and start the web server.
Parent
Choose the type of vertical cluster to create on Windows