Administer > Manage instances > WCS instance


Cluster with vertical cluster members

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


Before you begin

Clustering with vertical cluster members refers to the practice of defining cluster members of an application server on the same physical machine. Experience has shown that a single application server, which is implemented by a single JVM process, cannot always fully utilize the processor power and RAM of a large multiprocessor machine. Clustering with vertical cluster members provides a straightforward mechanism to create multiple JVM processes, that together can fully use all the processing power and memory available.


Procedure

  1. Federate the WebSphere Commerce node into a deployment manager cell.

  2. Create a WebSphere Commerce Cluster.

  3. Add additional cluster members.

  4. Start the WAS administration server.

  5. Launch the WebSphere administrative console.

  6. Create an Internal Replication Domain for the application:

    It is possible to create this as part of the initial cluster setup. If you have already created a Replication Domain for the application, you can use the existing one.

    1. Click Environment > Replication domains > New.

    2. Fill in the required fields. For Number of replicas, select Entire Domain. Save the changes.

  7. Enable cache replication in each clone.

    1. Click...

      Servers | Application servers | Clone Name | Container Services | Dynamic Cache Service

    2. To enable replication, select...

      Enable Cache Replication

    3. Choose a replication domain.

    4. Choose a replication type.

      For WebSphere Commerce, the recommendation is to use Not shared.

    5. Repeat steps a-d for each clone.

    6. Save the changes.

  8. Instead of using a default setting, always explicitly specify the replication mode for each entry in cachespec.xml.

    For example:

  9. Add <sharing-policy>shared-push</sharing-policy> to each cache-entry in cachespec.xml.

  10. To configure a cache entry to not replicate, set...

    <sharing-policy>not-shared</sharing-policy>.

  11. Regenerate the Web server plug-in and copy the plug-in to the Web server:

  12. Start the WebSphere Commerce cluster.


+

Search Tips   |   Advanced Search