WebSphere MQ objects required for bidirectional or peer-to-peer replication (two remote servers)

For example, assume that you plan to replicate transactions between Server A and Server B in both directions. You create the WebSphere MQ objects that link the Q Capture program at Server A with the Q Apply program at Server B. You also create the WebSphere MQ objects that link the Q Capture program at Server B with the Q Apply program at Server A. Server A and Server B each connect to a single queue manager on the systems where they run.

The following lists show the objects that are required for bidirectional or peer-to-peer replication between two remote servers. Because the queue manager is not part of the replication server but runs on the same system, the objects are grouped by system:

Non-channel objects at System A

• A queue manager
• A remote queue definition to serve as the send queue (this queue points to a receive queue at System B)
• A local queue to serve as the administration queue
• A local queue to serve as the restart queue
• A local queue to serve as the receive queue
• A remote queue definition to serve as the administration queue (this queue points to an administration queue at System B)
• A model queue definition for any temporary local spill queues that the Q Apply program creates and uses while it loads target tables

Non-channel objects at System B

• A queue manager
• A remote queue definition to serve as the send queue (this queue points to a receive queue at System A)
• A local queue to serve as the administration queue
• A local queue to serve as the restart queue
• A local queue to serve as the receive queue
• A remote queue definition to serve as the administration queue (this queue points to an administration queue at System A)
• A model queue definition for any temporary local spill queues that the Q Apply program creates and uses while it loads target tables

Channel objects

Channel objects from System A to System B

• A sender channel that is defined within the queue manager at System A
• An associated local transmission queue at System A
• A matching receiver channel that is defined within the queue manager at System B

Channel objects from System B to System A

• A sender channel that is defined within the queue manager at System B
• An associated local transmission queue at System B
• A matching receiver channel that is defined within the queue manager at System A

Figure 1 shows the WebSphere MQ objects that are required for bidirectional or peer-to-peer Q Replication between two remote servers.

Figure 1. WebSphere MQ objects required for bidirectional or peer-to-peer Q Replication between two remote servers.. You must create two sets of the same WebSphere MQ objects that are required to connect a Q Capture program and a Q Apply program in unidirectional Q Replication. One set of objects handles replication in one direction, and the other set of objects handles replication in the opposite direction. Only one queue manager is required at each system.