WebSphere® MQ
Multicast Transport is
a service that connects dedicated JMS application clients and is optimized
for high volume, one-to-many publish/subscribe topologies.
WebSphere Event
Broker provides
support to allow these clients to communicate with other applications through
message flows in a broker.
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.
The ability
to communicate with a broker means that JMS application multicast clients
can communicate with applications that use other supported protocols and transports.
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: