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: