Interaction between WebSphere MQ Everyplace and a broker

The figure below shows the general architecture involved in the relationship between WebSphere MQ Everyplace and a broker.


The relationship between
WebSphere MQ Everyplace and a broker. The path of messages flowing between
them. The topic text describes the relationships and the flow of messages.

For a discussion of security considerations for WebSphere MQ Everyplace applications, see Securing WebSphere MQ Everyplace resources.

Input from WebSphere MQ Everyplace applications

In the example shown in the figure, the WebSphere MQ Everyplace client attached to WebSphere Business Integration Message Broker is a WebSphere MQ Everyplace device with a WebSphere MQ Everyplace queue manager called ClientQM1. The broker, hosted by WebSphere MQ queue manager WBRK_QM, has a message flow deployed with an MQeInput node. This has an embedded WebSphere Business Integration Message Broker gateway (with its own WebSphere MQ Everyplace queue manager, ServerQM1 listening on an appropriate port) which treats WBRK_QM as a remote WebSphere MQ Everyplace queue manager.

WebSphere Business Integration Message Broker supports MQeInput or MQeOutput nodes only in a single execution group.

You should therefore ensure that all flows that communicate with WebSphere MQ Everyplace are within the same execution group. If you have more than one MQeInput node in that execution group, each one must use the same WebSphere MQ Everyplace queue manager.

Also, there must always be an MQeInput node in the same execution group as an MQeOutput node.

  • A message from the WebSphere MQ Everyplace 'client' destined for WebSphere Business Integration Message Broker must be directed to the queue belonging to the WebSphere MQ queue manager (WBRK_QM) hosting the broker (not the WebSphere MQ Everyplace queue manager, ServerQM1, running within WebSphere Business Integration Message Broker).
  • When the gateway receives a message destined for WBRK_QM rather than itself, the message is put on the WebSphere MQ bridge queue.
  • At this point, the message is a WebSphere MQ Everyplace object: it is passed to a transformer that creates a WebSphere MQ form of the message and passes it back to the WebSphere MQ bridge queue.
  • The message, now a WebSphere MQ message, is passed over a JNI (Java Native Interface) connection and held on a synchronized WebSphere MQ queue belonging to WBRK_QM.
  • From this queue, it is taken into the message flow by the input node.
  • Within a broker, the message can be dealt with in different ways depending on the message class used for the message, as explained in WebSphere MQ Everyplace messages.

Output to WebSphere MQ Everyplace

WebSphere MQ Everyplace output can be sent using either an MQeOutput node or a Publication node. The Publication node incorporates the function associated with an MQeOutput node, enabling messages to be retrieved by subscribers.

Further information about WebSphere MQ Everyplace

The information given in this and related topics, mostly concerns the interaction between WebSphere MQ Everyplace and WebSphere Business Integration Message Broker.

Refer to the WebSphere MQ Everyplace product library for further information about WebSphere MQ Everyplace itself. The MQSeries Everyplace for Multiplatforms Whitepaper also provides a useful overview of WebSphere MQ Everyplace.