Setting up a publish/subscribe broker

You can use WebSphere MQ Integrator Version 2, WebSphere MQ Event Broker Version 2.1, WebSphere Business Integration Event Broker, Version 5.0, or WebSphere Business Integration Message Broker, Version 5.0 as the publish/subscribe broker for WebSphere MQ JMS. You can link to each of these brokers across a connection to base WebSphere MQ, or you can connect directly to WebSphere MQ Event Broker, WebSphere Business Integration Event Broker, or WebSphere Business Integration Message Broker over TCP/IP. Each method requires some setup activities:

Linking across WebSphere MQ
Direct connection to WebSphere MQ Event Broker, Version 2.1 over TCP/IP
For this, set up a message flow within an execution group on WebSphere MQ Event Broker. This message flow is to read messages from the TCP/IP socket on which the broker is listening.

The basic message flow consists of a JMSIPOptimised flow set to listen on the port configured for direct connections. By default, this port is 1506.

Note:
WebSphere MQ Event Broker can be configured to listen for both direct connections across TCP/IP from WebSphere MQ JMS and connections made across TCP/IP through WebSphere MQ. In this case, the two listeners must be configured on different ports. The default port for a WebSphere MQ connection is 1414.
Direct connection to WebSphere Business Integration Event Broker, Version 5.0 or WebSphere Business Integration Message Broker, Version 5.0
To configure a WebSphere Business Integration Event Broker or WebSphere Business Integration Message Broker broker for a direct connection from WebSphere MQ JMS, create a message flow to read messages from the TCP/IP port on which the broker is listening and publish the messages. You can do this in either of the following ways: You must configure the Real-timeOptimizedFlow or Real-timeInput node to listen on the port used for direct connections. By default, the port number for direct connections is 1506.