Configure a broker for an application that uses a real-time connection to a broker

Before we can run an application that uses a real-time connection to a broker, we must configure that broker.

Before starting

Before starting this task, you perform the following steps:

• Make sure that the application has access to a broker that is running.
• Make sure that the application uses a connection factory whose properties are set appropriately for a real-time connection to a broker. For more information about the properties of a connection factory, see Properties of ConnectionFactory.

You configure a broker to run XMS applications in the same way that you configure a broker to run IBM MQ classes for JMS applications. The following steps summarize what you need to do:

Procedure

1. Create and deploy a message flow to read messages from the TCP/IP port on which a broker is listening and publish the messages. We can do this in either of the following ways:
   • Create a message flow that contains a Real-timeOptimizedFlow message processing node.
   • Create a message flow that contains a Real-timeInput message processing node and a Publication message processing node.

   We must configure the Real-timeOptimizedFlow or Real-timeInput node to listen on the port used for real-time connections. In XMS, the default port number for real-time connections is 1506.

   You do not need to perform this step if a suitable message flow is already deployed at the broker.

2. If you require messages to be delivered to the application using IBM MQ classes for JMS, configure the broker to enable multicast. Configure the topics that must be multicast enabled, specifying a reliable quality of service for those topics requiring reliable multicast.
3. If the application supplies a user ID and a password when it connects to the broker, and we want the broker to authenticate the application using this information, configure the user name server and the broker for simple telnet-like password authentication.

Results