An application client can run on a system anywhere in the WebSphere MQ network. Because WebSphere Event Broker clients must use WebSphere MQ facilities to connect to the broker, and to interact with it (using the MQI and AMI), the setup of clients for WebSphere Event Broker is identical to that for clients for an WebSphere MQ server.
To support client connections to a broker:
An application can only get messages from queues owned by the queue manager to which it is connected (this is true for all WebSphere MQ applications). Therefore, if an application expects to receive messages from a queue populated by a service within a particular broker and owned by that broker's queue manager, it must connect to that broker's queue manager (using a local or WebSphere MQ client connection).
An application that puts messages, however, can be connected to any queue manager in the network, as long as the queue manager can resolve the target destination in some way. In all cases, the queue manager to which the client application is connected must know the location of the queue or queues to which the application puts messages (for example using remote queue definitions).
When you define a WebSphere MQ queue as a node for a message flow, you must not give it a name that starts with SYSTEM_BROKER. This is reserved for queues defined for internal use by WebSphere Event Broker.
If your application is a subscriber, receiving messages published by other applications, it can specify a temporary dynamic queue as its subscriber queue. If it does so, the broker automatically deregisters the subscription when the queue is deleted.
For more details about applications, putting and getting messages, and the use of WebSphere MQ clients, see WebSphere MQ Clients and the WebSphere MQ Application Programming Guide.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac10126_ |