Adding vertical cluster members to a dynamic cluster
You can add vertical cluster members to your dynamic cluster. The members share the workload demands across multiple members that run on the same server.
Procedure
- Open a browser.
- Enter http://DM01:9060/ibm/console to access the deployment manager WebSphere® Integrated Solutions Console, where DM01 is the deployment manager node or host name. The port number might differ based on your installation.
- Complete the following steps to allow vertical clusters
on your dynamic cluster:
- Go to Servers > Clusters > Dynamic clusters.
- Select the 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 that are allowed on each node.
- Click Apply and then click Save to save the changes to the master configuration.
- Optional: Go to Servers > Clusters > Dynamic Clusters > clustername > Cluster Members view to view the list of new cluster members.
- Go to Servers > Clusters > Cluster Topology to view the new cluster topology.
- Complete the following steps to update the virtual host
entries:
- Identify the port values for the new dynamic members.
- Read Configuring virtual hosts for information.
- Log in to the WebSphere Integrated Solutions Console.
- Update the default_host virtual host.
- Add an alias entry for the port number. Use an "*" wildcard character for the host name.
- Complete the following steps to enable cache replication:
- From the deployment manager WebSphere Integrated Solutions Console, go to Servers > Server Types > WebSphere application servers.
- Click the new vertical cluster member.
- 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 menu.
- Click OK.
- Click Save to save your 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:
- Open a command prompt on the node where you created the vertical cluster.
- Change to the wp_profile_root\ConfigEngine directory.
- Run the following task:
- AIX® HP-UX Linux Solaris: ./ConfigEngine.sh cluster-node-config-vertical-cluster-setup -DServerName=unique vertical cluster servername -DWasPassword=password
- IBM® i: ConfigEngine.sh cluster-node-config-vertical-cluster-setup -DServerName=unique vertical cluster servername -DWasPassword=password
- Windows: ConfigEngine.bat cluster-node-config-vertical-cluster-setup -DServerName=unique vertical cluster servername -DWasPassword=password
Where unique vertical cluster servername is the name that you specified when you created the cluster member.
- Restart the vertical cluster member that is referenced in the cluster-node-config-vertical-cluster-setup task.
- The binary cache that is used by the JCR cannot share files between Portal JVMs. Therefore,
each cluster member that is on a single host system must have its own directory that is specified
for the JCR binary file cache property. Complete the following steps to configure the
directories:
- From the deployment manager WebSphere Integrated Solutions Console, go to Resources > Resource Environment > Resource Environment Providers. Each server should have a server scoped Resource Environment Provider. The provider is called JCR ConfigService PortalContent.
- Click the first JCR ConfigService PortalContent link in the list.
- Click Custom properties.
- Verify that the jcr.binaryValueFileDir value is unique within the
WebSphere Portal node where the server is located. For example, the following values are supported:
- The Node 1/Server 1 value for jcr.binaryValueFileDir is /opt/IBM/WebSphere/wp_profile/jcr/binary
- The Node 1/Server 2 value for jcr.binaryValueFileDir is /opt/IBM/WebSphere/wp_profile2/jcr/binary
- The Node 2/Server 1 value for jcr.binaryValueFileDir is /opt/IBM/WebSphere/wp_profile/jcr/binary
- The Node 2/Server 2 value for jcr.binaryValueFileDir is /opt/IBM/WebSphere/wp_profile2/jcr/binary
The following values are not supported:- The Node 1/Server 1 value for jcr.binaryValueFileDir is /opt/IBM/WebSphere/wp_profile/jcr/binary
- The Node 1/Server 2 value for jcr.binaryValueFileDir is /opt/IBM/WebSphere/wp_profile/jcr/binary
If the value is not unique, complete the following steps:- Click jcr.binaryValueFileDir.
- Change the value of the jcr.binaryValueFileDir.
- Click OK.
- Click Save.
- Repeat these steps on all JCR ConfigService PortalContent options.
- Save your changes and resynchronize the nodes.
- Log in to the deployment manager WebSphere Integrated Solutions Console.
- Select System Administration > Nodes.
- Select the node from the list and click Full Resynchronize.
- If you transferred your databases after you created the
cluster, complete the following steps on each vertical cluster member:
- Log on to the deployment manager WebSphere Integrated Solutions Console.
- Go to Environment > WebSphere Variables.
- From the Scope menu, select the Node=nodename, Server=servername option to narrow the scope of the listed variables. Node=nodename is the node that contains the WebSphere Portal application server.
- Update the WCM_DATASOURCE variable with the JCR data source name. Create the variable in the jdbc/jcr.DataSourceName format. For example, jdbc/wpdbds_jcr.
- Save all changes and synchronize the nodes.
- Stop and start the web server.