WebSphere MQ Real-time Transport

Start of changeWebSphere® MQ Real-time Transport is a lightweight protocol optimized for use with nonpersistent messaging. It is used exclusively by Java™ Message Service (JMS) clients, and provides high levels of scalability and message throughput.End of change

Start of changeThese clients participate in publish/subscribe scenarios, sending messages over IP connections to other internet and intranet applications. WebSphere Event Broker provides support to allow these clients to communicate with other applications through message flows in a broker.End of change

WebSphere MQ Real-time Transport is suited for applications and environments where you need to send large numbers of messages, or where messages are to be sent to large numbers of client applications. Use this protocol for applications that must rely on the quality of service provided by TCP/IP but do not need persistent delivery. For example, you can use this protocol in situations where a piece of data is updated very frequently, such as updating a scoreboard for a sporting event or updating a share price on a stock ticker. Because this is a lightweight protocol, it offers higher levels of performance for nonpersistent messaging than WebSphere MQ Enterprise Transport. The WebSphere MQ Real-time Transport does not provide any facilities for persistent messaging or durable subscriptions.

To use the WebSphere MQ Real-time Transport, you deploy a message flow that contains a Real-timeOptimizedFlow node or a Real-timeInput node to your broker. (The Real-timeInput node is an input node and the Real-timeOptimizedFlow node is a complete message flow that provides a high performance publish/subscribe message flow.) The message flow can send output messages to other real-time applications, using either the Real-timeOptimizedFlow or the Publication node.

This protocol is a non-queued transport: applications communicate with the broker by writing data directly to TCP/IP ports, and the input nodes are configured with a TCP/IP port number on which the broker listens for incoming connections. Client applications that use the WebSphere MQ Real-time Transport connect to this port.

Applications that connect using WebSphere MQ Real-time Transport and the JMS API use predominantly the publish/subscribe model.

The following built-in nodes support this protocol:

Related concepts
End-user application support
Related tasks
Supporting end-user applications
Related reference
Built-in nodes
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:39:51

ac12580_