The figure below shows the general architecture involved in the relationship between WebSphere MQ Everyplace and a broker.
For a discussion of security considerations for WebSphere MQ Everyplace applications, see Securing WebSphere MQ Everyplace resources.
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.
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.
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.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac10100_ |