dale lane

Scenario

You have an IBM MQ queue manager. An application is putting messages to a command queue. Another application gets these messages from the queue and takes actions in response.

Objective

You want multiple separate audit applications to be able to review the commands that go through the command queue.

They should be able to replay a history of these command messages as many times as they want.

This must not impact the application that is currently getting the messages from the queue.

Solution

You can use Streaming Queues to make a duplicate of every message put to the command queue to a separate copy queue.

This copy queue can be used to feed a connector that can produce every message to a Kafka topic. This Kafka topic can be used by audit applications

Details

The final solution works like this:

1. A JMS application called Putter puts messages onto an IBM MQ queue called COMMANDS
2. For the purposes of this demo, a development-instance of LDAP is used to authenticate access to IBM MQ
3. A JMS application called Getter gets messages from the COMMANDS queue
4. Copies of every message put to the COMMANDS queue will be made to the COMMANDS.COPY queue
5. A Connector will get every message from the COMMANDS.COPY queue
6. The Connector transforms each JMS message into a string, and produces it to the MQ.COMMANDS Kafka topic
7. A Java application called Audit can replay the history of all messages on the Kafka topic

(more…)