Other options to ensure cache content consistency across cluster | Invalidate cache entry per JVM using file system
Invalidate cache entry per JVM using database
You can uniquely identify each JVM with this custom JVM property for WebSphere Commerce:
com.ibm.commerce.scheduler.SchedulerHostNameSet the value to NodeName.ServerName so that it is unique within the cell.
Next create a scheduled DynaCacheInvalidation job to run on a particular JVM. When calling the AddJob command to create the new schedule job, specify the host parameter and use the value that uniquely identifies the scheduler process. If you want to manually change an existing job, update the SCCHOST column in the SCHCONFIG table for the job that you want to run on a particular instance.
This option would eliminate the need for a replication domain. However, for each invalidation request, we need to create a SCHCONFIG record per JVM, one for each cluster member so they each run their individual DynaCacheInvalidation job. This introduces overhead on the database.
If you do not have too many cluster members (for example, 2), and the response time is acceptable when each server generates its own cache content without sharing, then you may want to explore this option.
xxxx