WebSphere Commerce EnterpriseWebSphere Commerce Professional

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

The instructions in this section create a new cluster that contains the original WebSphere Commerce application server. After you create this cluster, you might create more cluster members to share the workload within the cluster. You can create more cluster members either on the same node or any other node in the deployment manager cell.

Procedure

To create the new WebSphere Commerce cluster:
  1. If it is not started, start the deployment manager. URL:
  2. If they are not started, start the node agent on each node where you want to create a new cluster member.SolarisLinuxAIX Ensure that you start each node agent as the WebSphere Commerce non-root user.
  3. Open the WebSphere Application Server Deployment Manager administrative console. For instructions, refer to Launching the WebSphere Application Server Administrative Console.
  4. 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.
  5. On the Server Cluster page, click New.
  6. In the Cluster name field, enter a name for the cluster, then click Next.
  7. Select Create the member by converting an existing application server.
    From the list of existing servers, select the WebSphere Commerce application server.. The WebSphere Commerce application server name in the list displays in the following form: 
    cell_name/WC_instance_name_node(WAS_version)/server1
    where
    WAS_version
    The version number of the WebSphere Application Server.
  8. Click Next.
  9. In the Member name field, enter the name of the new cluster member to create.
  10. From the Select node field, select the name of the node on which you want to create the new cluster member. For horizontal clustering, the node name is a different name from the name of the node on which you originally installed WebSphere Commerce. For vertical clustering, the node name is the same name as the name of the node on which you originally installed WebSphere Commerce.
  11. Click Add Member. For more information about adding more cluster members, Adding additional cluster members.
  12. Click Next and review the Summary page.
  13. Click Finish.
  14. Click the Review link.
  15. 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.
  16. Click Save to save your configuration.
  17. Click OK.
  18. During horizontal clustering, the WebSphere Application Server administrative console indicates that the task is complete while the EAR file is still being copied. To verify that the EAR file is copied properly, complete the following steps:
    1. Navigate to the WC_profiledir/bin directory and run the following command:
      • SolarisLinuxAIXwsadmin.sh
      • Windowswsadmin.bat
      • For IBM i OS operating system wsadmin
    2. Enter the following command once you are connected:
      • $AdminApp isAppReady applName where applName is the name of the application. For example, WC_instance_name.
    3. If the last line of the output is true, the application is fully distributed.
    4. Exit from wsadmin. To exit wsadmin, type exit.
  19. Log out of the WebSphere Application Server Deployment Manager administrative console.