After you federate your WebSphere Commerce environment,
you can configure vertical clustering. Clustering provides failover
protection and provides workload balancing.
Before you begin
- Complete the installation of a WebSphere Commerce node using the
custom install option of the installation wizard.
- Create a WebSphere Commerce instance.
- Before clustering a WebSphere Commerce instance,
it strongly recommended that you backup the WebSphere Application
Server administrative configuration. Backing up the administrative
configuration will allow you to restore the original configuration
if clustering fails during the clustering process. For more information,
see Backing up and recovering
the application server environment.
About this task
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
- Federate the
WebSphere Commerce node into a deployment manager cell.
- Create a WebSphere
Commerce Cluster.
- Add additional cluster
members.
- Starting and stopping quick reference.
- Open the WebSphere Integrated Solutions Console.
- Create an Internal
Replication Domain for your application:
Note: It is possible
to create this as part of the initial cluster setup. If you have already
created a Replication Domain for your application, you can use the
existing one.
- Click .
- Fill in the required fields. For Number
of replicas, select Entire Domain.
Save the changes.
- Enable cache replication in each cluster member.
- Click .
- To enable replication, select Enable Cache
Replication.
- Choose a replication domain.
- Choose a replication type. For WebSphere Commerce, the
recommendation is to use Not shared. For other
options, see Dynamic cache service settings.
Note: With the Not shared replication type, invalidations are sent without
replicating content.
- Repeat steps a-d for each cluster member.
- Save your changes.
- Ensure the replication domain and
replication type of all out of box DistributedMap object caches are
specified.
- Open the WebSphere Application Server Integrated Solutions
Console.
- From the left menu, click .
-
Ensure the replication domain and replication type of 1 (notShared) is specified for all the
object caches defined in the Stores.war/classes/cacheinstances.properties file. At least the object
cache with JNDI name services/cache/WCSessionDistributedMapCache must be defined. For more
information, see Enabling WebSphere Commerce data cache
- Instead of using a default setting,
always explicitly specify the replication mode for each entry in cachespec.xml.
For example:
- Add
<sharing-policy>shared-push</sharing-policy>
to
each cache-entry in cachespec.xml.Note: You can
choose not to replicate certain cache entries. To configure a cache
entry to not replicate, set
<sharing-policy>not-shared</sharing-policy>
.
See the
cachespec.xml.
For more
information, see Cache replication.
- Regenerate the Web
server plug-in and copy the plug-in to the web server.
- Start the WebSphere Commerce cluster.