Dynamic caching considerations for dual cell environments
Ensure that you configure the cache invalidation correctly so that the cache in all cluster members are invalidated after indexprop is run.
If you are using local dynacache, synchronize the cache by using the DynaCacheInvalidation job
and setting up Data Replication Services in each cell. Consider the following configuration method
as an example.
Important: This configuration assumes that you enabled session affinity in
the load balancer. If session affinity is not
enabled, shoppers are more likely to be directed to a server with an invalid or stale cache.
- On each cell, create an internal replication domain and enable cache replication. For more
information, see:
- Step 5 and onwards in Clustering with vertical cluster members or
- Step 7 and onwards in Clustering with horizontal cluster members
- Create DynaCacheInvalidation jobs; one job for each cell. Ensure that you add unique strings to the Allowed host field of the DynaCacheInvalidation jobs. For more information, see Scheduling a site-level job
- Assign a WebSphere Commerce server on each cell to run the DynaCacheInvalidation job by
specifying the
com.ibm.commerce.scheduler.SchedulerHostNameJVM parameter. When you specify the value of the JVM parameter, use the appropriate Allowed host string of the DynaCacheInvalidation job. For more information, see Configuring the scheduler to run a job on an instance or cluster member.