This migration makes minimal changes to the application, yet still uses
the MQe bridge instead of the MQe broker node. The downside is that it requires
the use of deprecated MQe classes.
The following work is required:
- Modify the message flow on the broker such that MQ input nodes are used
instead of MQe input nodes.
- Modify the client application such that messages are sent via the MQe
bridge. Any subscribe and un-subscription messages are sent to the broker’s
control queue SYSTEM.BROKER.CONTROL.QUEUE, whilst publication messages must
now be sent to the input queue of the appropriate message flow (this flow
will contain a Publication node). In all cases the com.ibm.broker.mqimqe.wrapper.MQeMbMsgObject
continues to be used.
- Configure an MQe bridge to transfer and transform MQe messages from the
MQe network to the MQ network underlying the broker topology. The bridge transformer
class must be configured to be com.ibm.mqe.mqbridge.MQeMbTransformer.
Note that two bridge queues must also be configured: one to direct messages
to the broker’s control queue SYSTEM.BROKER.CONTROL.QUEUE; the other to direct
messages to the input queue of the appropriate message flow.