Enable dynamic cache service multi-cell and multi-core group invalidation with scripting

Enable dynamic cache service multi-cell and multi-core group invalidation with scripting

Use the dynacacheJMSSIB.py script to enable dynamic cache service multi-cell and multi-core group invalidation. Configure the external cache adapter and service integration bus infrastructure in multiple cells. To work correctly, the script must be executed from...
PROFILE_HOME/bin

We must also ensure that :

Each cell or core group contains a cluster hosting a production application. The same production application has to be used in both cells or core groups to ensure invalidation IDs are processed correctly.
A separate cluster of two servers is created in each cell or core group to host the service integration bus. The members of this cluster cannot have a RemoteJMSInvalidator external cache group defined. If a RemoteJMSInvalidator external cache group is defined for these cluster members, an infinite loopback condition occurs where invalidations are repeatedly send back and forth between cells.
A datasource is defined and is accessible from both service integration bus cluster members. If the database is shared by both cells, ensure a unique database name is used when defining each the datasource for each cell.
Each cell or core group contains a replication domain containing both the service integration bus cluster and all of the clusters hosting the production applications.

The dynacacheJMSSIB.py script configures each cell or core group in three steps:

Inbound JMS/service integration bus configuration.
Inbound JMS/service integration bus configuration includes:

Create a service integration bus and configuring the service integration bus destination.
Create a Java Message Service (JMS).
Configure the JMS activation specification
Install the WAS_INSTALL_ROOT/installables/DynacacheMessageHandler.ear message driven bean on the service integration bus cluster.

Outbound JMS/service integration bus configuration.
Outbound JMS/service integration bus configuration includes configuring the JMS queue connection factory to communicate with a remote cell.

External cache group configuration.
External cache group configuration includes configuring an external cache group and external cache adapter on each cluster member hosting the production applications.

Display the available parameters for each command...
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheInSIB --help
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheOutSIB --help
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=ddynacacheECA --help

To delete an inbound, outbound, or ECA configuration, add --delete to the command used to create the respective configuration artifacts.

Example 1: Multiple cells

This example shows how the script is used to configure two cells, Cell1 and Cell2, where both cells host the same application,ApplicationA.
Cell1
ProductionCluster1 (hosts ApplicationA)
	SIBCluster1
		node1/sib1 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=7777
			hostname=host1.com
		node1b/sib2 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=7776
			hostname=host11.com			
		ReplicationDomain (contains ProductionCluster1 members and SIBCluster1 
		members)
	Service Integration Bus Data Source1
		JNDI name = jdbc/SIBCluster1DataSource
Cell2
ProductionCluster2 (hosts ApplicationA)
	SIBCluster2
		node2/sib1 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=8888
			hostname=host2.com
		nodesb/sib2 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=8889
			hostname=host22.com			
		ReplicationDomain (contains ProductionCluster2 members and SIBCluster2 
		members)
	Service Integration Bus Data Source2
		JNDI name = jdbc/SIBCluster2DataSource	
Enable dynamic cache service cell invalidation support for Cell1 and Cell2.

Configure inbound JMS/service integration bus for Cell1:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheInSIB --cluster=SIBCluster1 --datasourceJNDI=jdbc/SIBCluster1DataSource

Configure inbound JMS/service integration bus for Cell2:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheInSIB --cluster=SIBCluster2 --datasourceJNDI=jdbc/SIBCluster2DataSource

Configure outbound JMS/service integration bus for Cell1:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheOutSIB --remoteCellSIBServers=host2.com:8888,host22.com:8889 --remoteCellID=Cell2

Configure outbound JMS/service integration bus for Cell2:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheOutSIB --remoteCellSIBServers=host1.com:7777,host11.com:7776 --remoteCellID=Cell1

Configure external cache group/adapters for Cell1:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheECA --cluster=ProductionCluster1 --remoteCellID=Cell2

Configure external cache group/adapters for Cell2:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheECA --cluster=ProductionCluster2 --remoteCellID=Cell1

This example shows how the script is used to configure a single cell containing multiple core groups. The core groups host the same application (ApplicationA).
CoreGroup1
	ProductionCluster1 (hosts ApplicationA)
	SIBCluster1
		node1/sib1 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=7777
			hostname=host1.com
		node1b/sib2 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=7776
			hostname=host11.com			
		ReplicationDomain (contains ProductionCluster1 members and SIBCluster1 
		members)
	Service Integration Bus Data Source1
		JNDI name = jdbc/SIBCluster1DataSource
CoreGroup2 in Cell2 is also hosting ApplicationA and has the following topology:
CoreGroup2
	ProductionCluster2 (hosts ApplicationA)
	SIBCluster2
		node2/sib1 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=8888
			hostname=host2.com
		nodesb/sib2 (service integration bus member)
			SIB_ENDPOINT_ADDRESS=8889
			hostname=host22.com			
		ReplicationDomain (contains ProductionCluster2 members and SIBCluster2 
		members)
	Service Integration Bus Data Source2
		JNDI name = jdbc/SIBCluster2DataSource	
Enable dynamic cache service core group invalidation support for CoreGroup1 and CoreGroup2.

Configure inbound JMS/service integration bus for CoreGroup1:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheInSIB --localCellID=Cell1/CoreGroup1 --cluster=SIBCluster1 --datasourceJNDI=jdbc/SIBCluster1DataSource

Configure inbound JMS/service integration bus for CoreGroup2:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheInSIB --localCellID=Cell1/CoreGroup2 --cluster=SIBCluster2 --datasourceJNDI=jdbc/SIBCluster2DataSource

Configure outbound JMS/service integration bus for CoreGroup1:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheOutSIB --localCellID=Cell1/CoreGroup1 --remoteCellSIBServers=host2.com:8888,host22.com:8889 --remoteCellID=Cell1/CoreGroup2

Configure outbound JMS/service integration bus for Coregroup2:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheOutSIB --localCellID=Cell1/CoreGroup2 --remoteCellSIBServers=host1.com:7777,host11.com:7776 --remoteCellID=Cell1/CoreGroup1

Configure external cache group/adapters for CoreGroup1:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheECA --cluster=ProductionCluster1 --localCellID=Cell1/CoreGroup1 --remoteCellID=Cell1/CoreGroup2

Configure external cache group/adapters for CoreGroup2:
./wsadmin.sh -lang jython -f ../../../util/dynacacheJMSSIB.py --setup=dynacacheECA --cluster=ProductionCluster2 --localCellID=Cell1/CoreGroup2 --remoteCellID=Cell1/CoreGroup1

Related:

Dynamic cache service multi-cell and multi-core group invalidation
Start the wsadmin scripting client
Java virtual machine custom properties