Administration guide > Configure the deployment environment > Configuring data grids
Configure peer-to-peer replication with JMS
The Java™ Message Service (JMS) based peer-to-peer replication mechanism is used in both the distributed and local WebSphere eXtreme Scale environment. JMS is a core-to-core replication process and allows data updates to flow among local ObjectGrids and distributed ObjectGrids. For example, with this mechanism you can move data updates from a distributed eXtreme Scale data grid to a local eXtreme Scale grid, or from a grid to another grid in a different system domain.
Before you begin
The JMS-based peer-to-peer replication mechanism is based on the built-in JMS-based ObjectGridEventListener, com.ibm.websphere.objectgrid.plugins.builtins.JMSObjectGridEventListener. For detailed information regarding enabling peer-to-peer replication mechanism, see JMS event listener.
See Enable the client invalidation mechanism for more information.
The following is an XML configuration example to enable a peer-to-peer replication mechanism on an eXtreme Scale configuration:
peer-to-peer replication configuration - XML example <bean id="ObjectGridEventListener" className="com.ibm.websphere.objectgrid.plugins.JMSObjectGridEventListener"> <property name="replicationRole" type="java.lang.String" value="DUAL_ROLES" description="" /> <property name="replicationStrategy" type="java.lang.String" value="PUSH" description="" /> <property name="jms_topicConnectionFactoryJndiName" type="java.lang.String" value="defaultTCF" description="" /> <property name="jms_topicJndiName" type="java.lang.String" value="defaultTopic" description="" /> <property name="jms_topicName" type="java.lang.String" value="defaultTopic" description="" /> <property name="jms_userid" type="java.lang.String" value="" description="" /> <property name="jms_password" type="java.lang.String" value="" description="" /> <property name="jndi_properties" type="java.lang.String" value="java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory; java.naming.provider.url=tcp://localhost:61616;connectionFactoryNames=defaultTCF; topic.defaultTopic=defaultTopic" description="jndi properties" /> </bean>
- Distribute changes between peer JVMs
The LogSequence and LogElement objects distribute changes between peer JVMs and communicate the changes that have occurred in an eXtreme Scale transaction with an ObjectGridEventListener plug-in.
- JMS event listener
The JMSObjectGridEventListener is designed to support client-side near cache invalidation and a peer-to-peer replication mechanism. It is a Java Message Service (JMS) implementation of the ObjectGridEventListener interface.
Parent topic:
Configure data grids
Related concepts
Configure write-behind loader support
JMS for distributing transaction changes
Related tasks
Related reference
ObjectGrid descriptor XML file