Administer > Manage instances > WCS instance > Cluster with horizontal cluster members

Create the WebSphere Commerce cluster

Overview

After federating the 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 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.

Create new WebSphere Commerce cluster

1. Start the deployment manager

2. Start the node agent on each node where we will create a new cluster member.

   For *nix, start each node agent as the non-root user.

3. Open the WAS ND Administrative Console.

4. In the Navigation area, expand...

   Servers | Clusters | WebSphere Application Server clusters | New

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

6. In the Existing server section, select...

   Select an existing server to add to this cluster

   ...and from the list of existing servers, select the commerce application server from the pull-down list.

   cellWC_instance_node(WAS_version)/server1

7. 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 commerce application server.

   cellWC_instance_node(WAS_version)/server1

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 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 the configuration.

15. Review to save the configuration.

16. To ensure that the deployment manager profile immediately synchronizes the configuration changes with the other nodes...

    Synchronize changes with Nodes

17. During horizontal clustering the 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, run...

    cd WC_PROFILE/bin
    ./wsadmin.sh
    $AdminApp isAppReady applName

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

18. Click Save.

19. Click Ok.

20. Log out from the WAS ND Administrative Console.

+

Search Tips   |   Advanced Search