Adding vertical cluster members to a static cluster
You can add vertical cluster members to share the workload demands of your cluster across multiple members on the same physical server.
Procedure
- Log on to the deployment manager WebSphere® Integrated Solutions Console.
- Go to Servers > Clusters > WebSphere application server clusters > cluster_name > Cluster members.
- Click New to create the cluster
member.
- Define the name of cluster member. Note: Do not use spaces in the cluster member name.
- Select an existing node where IBM® WebSphere Portal is installed.
- Check the box Generate Unique HTTP Ports.
- Click Add Member or Apply and then click Next to view the summary.
Important: Update the virtual host entries for the new port that is created when you added a cluster member. Update the default_host virtual host in the WebSphere Integrated Solutions Console. Then, add an alias entry for the port number. Use an "*" wildcard character for the host name. Read Configuring virtual hosts for information. - Define the name of cluster member.
- Click Finish and save the changes.
- View the new cluster topology from Servers > Clusters > Cluster Topology.
- The Servers > Server Types > WebSphere application servers view lists the new server cluster members.
- 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.
- Open a command prompt.
- Change to the wp_profile_root/ConfigEngine directory.
- Run the following command on each vertical cluster member to clean up the server-scoped
resources, caches, and resource providers:
- 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
- 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.
- Restart the vertical cluster member that is referenced in the cluster-node-config-vertical-cluster-setup task.
- Save your changes and resynchronize the nodes.
- In the deployment manager WebSphere Integrated Solutions Console, click Save on the taskbar.
- Save your administrative configuration.
- Go to System Administration > Nodes.
- Select the node from the list.
- 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.
- Regenerate the web server plug-in.
- Log in to the deployment manager WebSphere Integrated Solutions Console.
- Copy the updated plug-in configuration file (plugin-cfg.xml) to the web server's plug-in configuration directory.
- Stop and start the web server.