WebSphere Message Brokers
File: ac12590_
Writer: Kate Hostler

Reference topic

This build: July 31, 2007 21:18:30

WebSphere MQ Multicast Transport

Applications that connect using WebSphere MQ Multicast Transport and the JMS API use predominantly the publish/subscribe model. The applications must be multicast-enabled to use this protocol.

To use the WebSphere MQ Multicast Transport, you must deploy a message flow that contains a Real-timeOptimizedFlow node or a Real-timeInput node to your broker. 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 Multicast Transport connect to this port.

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

Related concepts
End-user application support
Message modeling
Related tasks
Supporting end-user applications
Related reference
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:18:30

ac12590_ This topic's URL is: