WebSphere MQ Enterprise Transport

The WebSphere MQ Enterprise Transport is the transport used by WebSphere MQ. The WebSphere MQ Enterprise Transport supports WebSphere MQ applications that connect to IBM® Integration Bus to benefit from message routing and transformation options.

The WebSphere MQ Enterprise Transport provides all the reliable messaging features available in WebSphere MQ. This transport provides persistent and non-persistent messaging and supports transactions. To use the WebSphere MQ Enterprise Transport, you must deploy a message flow that contains an MQInput node to your broker. If this message flow sends output messages to other WebSphere MQ applications, it must also include an MQOutput, MQReply, or Publication node.

The WebSphere MQ Enterprise Transport is a queued transport; applications communicate with the broker by writing data to and reading data from message queues. Use the WebSphere MQ Enterprise Transport when you require assured delivery of messages or need to use transactional support.

WebSphere MQ Enterprise Transport is used by WebSphere MQ clients or application programs that are written to the Application Messaging Interface (AMI) or Message Queue Interface (MQI). The client uses the services provided by the message flows deployed within one or more brokers in the broker network by interacting with the queues serviced by those message flows.

The queue specified in the MQInput node determines the queue on which the broker receives publications from publishing applications. Subscribers connect to the broker by sending a registration request to the broker's SYSTEM.BROKER.CONTROL.QUEUE. The subscriber specifies a queue on which they want to receive any publications on the registered topic in the registration request.

All IBM Integration Bus applications, like WebSphere MQ applications, can use all the supported WebSphere MQ interfaces to put messages to the message flow queues. In fact, every WebSphere MQ application is a potential IBM Integration Bus application.

These applications use one of two techniques to gain access to broker services:

• An application can use a WebSphere MQ client connection. You can use all the WebSphere MQ clients supported by Version 6.0 or later. You can therefore connect applications running in a wide variety of environments into your broker network. An application running on the same system as the queue manager to which it connects can also use a client connection.
• An application running on the same system as a broker can use a local connection to the queue manager that hosts that broker. If it uses this method, the client must execute on the same system. It can connect to a queue manager supporting a broker, or to any other queue manager in the WebSphere MQ network that has a defined path to the broker's queue manager. (This option is not possible on z/OS®, where clients are not supported.)

Multiple applications can communicate using separate local queue managers by using WebSphere MQ intercommunication (remote queue definitions, or clustering). For more details, see "Concepts of intercommunication" in the Intercommunication section of the WebSphere MQ information center.

IBM Integration Bus does not impose any particular conditions or restrictions on applications.

Receiving applications can get the messages put to the output queue or queues of a message flow when they have been processed by that message flow. The applications must be connected, either by a client/server connection, or across a local connection, to the queue manager that owns the queue or queues defined as the target for their messages. If the message flow provides a publish/subscribe service, the Publication node puts the messages to the queue specified by the subscriber as its local receiver queue.

Applications that connect using WebSphere MQ Enterprise Transport use a mixture of point-to point and publish/subscribe models.

The following built-in nodes are provided to support this protocol:

• MQInput
• MQOutput
• MQReply
• MQGet
• Publication
• SCA nodes, when communicating with WebSphere Process Server applications.