Create the WebSphere Commerce cluster

After federating your WebSphere Commerce environment, you can configure clustering. Clustering provides failover protection and provides workload balancing.

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

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. Ensure that you start each node agent as the WebSphere Commerce non-root user.

  3. Open the WAS Deployment Manager Administrative Console. For instructions, refer to Launching the WAS Administrative Console.

  4. In the Navigation area, expand Servers and click Clusters.

  5. On the Server Cluster page, click New.

  6. In the Cluster name field, enter a name for the cluster.

  7. Complete one of the following steps:

    • Existing server section, select Select an existing server to add to this cluster and from the list of existing servers, select the WebSphere Commerce application server from the pull-down list. The WebSphere Commerce application server name in the list will appear in the following form
      cell/WC_instance_node(WAS_version)/server1
      
      
      
      where

      cell

      is the name of the deployment manger cell to which the WebSphere Commerce application server belongs.

      instance

      is the name of the WebSphere Commerce instance.

      WAS_version

      is the version number of the WAS.

    • Select basis for first cluster member section, 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 will appear in the following form
      cell/WC_instance_node(WAS_version)/server1
      
      
      
      where

      cell

      is the name of the deployment manger cell to which the WebSphere Commerce application server belongs.

      instance

      is the name of the WebSphere Commerce instance.

      WAS_version

      is the version number of the WAS.

  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 Apply. For adding additional cluster members refer to Add additional cluster members.

  12. Click Next and review the Summary page.

  13. Click Finish.

  14. Click Save to save your configuration.

  15. Review to save your configuration.

  16. Select Synchronize changes with Nodes to ensure that the deployment manager profile immediately synchronizes the configuration changes with the other nodes.

  17. During horizontal clustering the WAS Administrative Console will indicate that the task is complete while the EAR file is still being copied. To verify that the EAR file has been copied properly, complete the following steps:

    1. Navigate to the WC_profiledir/bin directory and run the following command:

      • AIX|Linux|Solaris: wsadmin.sh

      • I5/OS:

        wsadmin

      • Windows: wsadmin.bat

    2. Enter the following command once you have connected:

      • $AdminApp isAppReady applName where applName is the name of the application. For example, WC_instance.

    3. If the last line of the output is true, the application is fully distributed.

    4. Exit from wsadmin. To exit wsadmin, type exit.

  18. Click Save.

  19. Click Ok.

  20. Log out from the WAS Deployment Manager Administrative Console.

 

Related Concepts


WAS ND clustering mechanism

 

Related tasks


Cluster with vertical cluster members
Cluster with horizontal cluster members
Prepare additional nodes
Define the JDBC driver path
Add additional cluster members
Start or stopping a WebSphere Commerce cluster
Remove a cluster member