Creating the WebSphere Commerce cluster
After you federate your WebSphere Commerce environment, you can configure clustering. Clustering provides failover protection and provides workload balancing.
About this task
Procedure
To create the new WebSphere Commerce cluster:
- If it is not started, start the deployment manager. URL:
-
If they are not started, start the node agent on each node where you want to create a new
cluster member.
Ensure that you start each node agent as the WebSphere Commerce non-root user.
- Open the WebSphere Application Server Deployment Manager administrative console. For instructions, refer to Launching the WebSphere Application Server Administrative Console.
-
In the Navigation area, expand Servers click
Clusters, and then click WebSphere Application Server
clusters.
Note: If you want to use cluster level resources, you must manually use the createCluster and createClusterMember commands with the resourcesScope parameter to create the cluster. For more information, see the New parameter named resourcesScope was added to the createCluster and createClusterMembercommands technote.
- On the Server Cluster page, click New.
- In the Cluster name field, enter a name for the cluster, then click Next.
-
Select Create the member by converting an existing application
server.
From the list of existing servers, select the WebSphere application server. The WebSphere Commerce application server name in the list displays in the following form:
wherecell_name/WC_instance_name_node(WAS_version)/server1
- WAS_version
- The version number of the WebSphere Application Server.
- Click Next.
- In the Member name field, enter the name of the new cluster member to create.
- From the Select node field, select the name of the node on which you want to create the new cluster member.For vertical clustering, the node name is the same name as the name of the node on which you originally installed WebSphere Commerce.
- Click Add Member. For more information about adding more cluster members, Adding more cluster members.
- Click Next and review the Summary page.
- Click Finish.
- Click the Review link.
- Select Synchronize changes with Nodes to ensure that the deployment manager profile immediately synchronizes the configuration changes with the other nodes. Once complete, the modules must be mapped to the new cluster as the modules are still mapped to the single application server. For more information about mapping, see Mapping modules to servers.
- Click Save to save your configuration.
- Click OK.
- Log out of the WebSphere Application Server Deployment Manager administrative console.