Recording by using mirror queues mode

In Mirror Queues mode, IBM® Rational® Integration Tester uses an WebSphere® MQ API exit, which is installed on the queue manager, to take a copy of each message and put it into another queue. Therefore, if you record multiple queues, multiple mirror queues are set up.

About this task

Note: This recording mode is available only if IBM® WebSphere® MQ 7.1 or later is installed and configured in Library Manager.
For general information about WebSphere® MQ API exits, see the WebSphere® MQ documentation. For information about deploying the API exit, see Installing and configuring Rational Integration Tester API exits.
Note: When you use mirror queues to record an operation, you might encounter a race condition where the first few replies are sent before the reply queue monitor is set up. To avoid this problem, record the transport rather than the operation.

An example of the process is described in the following steps:

Procedure

  1. Start recording on Q1.
  2. Rational® Integration Tester (Recording Studio) configures the API exit to mirror all messages that are put onto Q1 to Q1_RIT.
  3. The client puts message onto Q1 with the reply queue specified as Q1R.
  4. The queue manager triggers the API exit, which puts a copy of the message onto Q1_RIT.
  5. Rational® Integration Tester (Recording Studio) subscribes to this queue and gets the message. Rational® Integration Tester detects that message specified a reply of Q1R. Rational® Integration Tester configures the API exit to mirror all messages from Q1R to Q1R_RIT.
  6. The server picks up the message from Q1 and replies to Q1R.
  7. The queue manager triggers the API exit, which puts a copy of the message onto Q1R_RIT.
  8. Rational® Integration Tester (Recording Studio) subscribes to this queue and gets the message.
  9. The client receives the reply from Q1R. client receiving reply from Q1R

    When you stop recording, Rational® Integration Tester will, by default, delete the mirrored queue (Q1_RIT and Q1R_RIT in the example) and tell the API exit to stop mirroring. Thus, mirrored queues do not fill up with messages when you are not recording.