WebSphere Message Brokers
File: ac10126_
Writer: Kate Hostler

Task topic

This build: July 31, 2007 21:17:58

Defining WebSphere MQ resources

An application client can run on a system anywhere in the WebSphere MQ network. Because WebSphere Message 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 Message Broker is identical to that for clients for an WebSphere MQ server.

To support client connections to a broker:

  1. If the application runs on the same system as the broker, it can establish a local connection with the broker's queue manager using MQCONN, and you do not have to define any WebSphere MQ resources to support it.
  2. If the application runs on the same system as another queue manager in the broker network, it can establish a local connection to that queue manager. In this scenario, you must define the appropriate resource to support communications between the queue manager to which the client has connected and the queue manager that hosts the broker that provides the required service.
  3. If the application runs on a system that does not support a queue manager, it must make a client connection to a queue manager on another system. The queue manager to which it connects can be one of the following:
    • The broker's queue manager

      You must set up the appropriate client connection and server connection definitions to support this option.

    • Another queue manager in the network

      You must set up the appropriate client connection and server connection definitions to support this option, and ensure that definitions are in place to support communications between the queue manager to which the client has connected and the queue manager that hosts the broker that provides the required service.

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 Message 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.

Related concepts
WebSphere MQ Enterprise Transport
Message flows overview
Related tasks
Developing message flows
Deploying
Related reference
WebSphere MQ Enterprise Transport
Built-in nodes
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:17:58

ac10126_ This topic's URL is: