Dynacache multi-cell replication support

WebSphere Application Server has released support for replication of Dynacache invalidations across cells. This allows Dynacache cache instance data to be consistent across cells. This feature released in the WAS60239, WAS61029 and WAS7007 service streams allows for dual data center topologies with Dynacache.  The replication of cache invalidations across cells is done using JMS.  ONLY cache invalidations are propagated, not cache entries.

High Level Usage Scenario:

• A solution architect is designing a topology that requires multiple active/active WAS ND cells and needs cached content in Dynacache object caches to stay in sync between the cells.
• A solution architect is designing a topology with a single WAS cell that requires multiple core groups due to the number of JVMs (>50).
  
  
  
  
  • Each core group contains servers hosting the same applications and needs object cache content to stay in sync between the cells. 
   Usage Scnenario: An administrator needs to configure dynacache to propagate Dynacache object cache invalidations between cells and/or core groups. 
  
  The configuration of this feature can be done using a script dynacacheJMSSIB.py shipped in the WAS Install. Enabling dynamic cache service multi-cell and multi-core group invalidation with scripting
  
  
  
  
  
  

Broadly speaking to configure this feature you will need to

1.  Define external cache group for remote cell invalidations.

2.  Define external cache group member for each remote cell to indicate where to send invalidations in remote cell.
      - Address – The name of the JMS queue to send invalidations to. A unique queue should exist for each cache instance.
      - Adapter bean name – Name of the class implementing the ECA interface that sends remote cell invalidations.

3. Define external cache group member for each remote cell to indicate where to send invalidations in remote cell.

4.   Create SIB hosted on cluster members
4a.Install RemoteCellInvalidatorApp on cluster members so the local cell can receive JMS invalidations from remote cells.
4b.Define connection factory with end points for connecting to the remote cell and define a bus containing the cluster members.

5. Repeat steps 1, 2, and 4 in the remote cell.