This migration uses the MQe bridge instead of the MQe broker node and avoids the use of any deprecated MQe classes.
One key difference is that the client application will have sent all its messages to the same queue (i.e. the broker MQe input node); intelligence in the node then determined the correct destination. The application must now send any subscribe and unsubscribe messages 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).
Likewise for messages being received – an MQePubSubMsgObject class object can be converted to its equivalent MQeMbMsgObject object with the constructor MQeMbMsgObject(MQePubSubMsgObject).