Let's look at the Remote Queue defnition for CAPA.TO.APPB.SENDQ.REMOTE, shown next. On the left-hand side are the defnitions on QMA, which comprise the Remote Queue, the Transmission Queue, and the Channel defnition. The defnitions on QMB are on the right-hand side and comprise the Local Queue and the Receiver Channel.
Let's break down these definitions to the core values to
show the relationship between the different parameters, as shown next:
We defne a Remote Queue by matching up the superscript
numbers in the definitions in the two Queue Managers:
For defnitions on QMA, QMA is the local system
and QMB is the remote system.
For defnitions on QMB, QMB is the local system
and QMA is the remote system.
- Remote Queue Manager name
- Name of the queue on the remote system
- Transmission Queue name
- Port number that the remote system is listening on
- The IP address of the Remote Queue Manager
- Local Queue Manager name
- Channel name
Queue names:
- QMB: Decide on the Local Queue name on QMB—CAPA.TO.APPB.RECVQ.
- QMA: Decide on the Remote Queue name on QMB—CAPA.TO.APPB.SENDQ.REMOTE.
Channels:
- QMB: Defne a Receiver Channel on QMB, QMA.TO.QMB—make sure the channel type (CHLTYPE) is RCVR.
- The Channel names on QMA and QMB have to match: QMA.TO.QMB.
- QMA: Defne a Sender Channel, which takes the messages from the Transmission Queue QMB.XMITQ and which points to the IP address and Listening port number of QMB. The Sender Channel name must be QMA.TO.QMB.
Let's move on from unidirectional replication to
bidirectional replication. The bidirectional queue diagram is shown next, which
is a cut-down version of the full diagram of the The WebSphere MQ layer
and just shows the queue names and types without the details.
The principles in bidirectional replication are the same as
for unidirectional replication. There are two Replication Queue Maps—one going
from QMA to QMB (as unidirectional replication) and one going
from QMB to QMA.
till then.....
njoy the simplicity.......
