Before you can run an application that uses a real-time connection
to a broker, you must configure the broker.
Before you begin
Before starting this task, you must do the following:
- Make sure that your application has access to a broker that is running.
- Make sure that your application uses a connection factory whose properties
are set appropriately for a real-time connection to the broker. For more information
about the properties of a connection factory, see Properties of ConnectionFactory.
Why and when to perform this task
You configure the broker to run
XMS applications
in the same way that you configure the broker to run
WebSphere MQ JMS applications.
The following steps summarize what you need to do but, for more details, see
the
WebSphere
Business Integration Event Broker or
WebSphere Business
Integration Message Broker Information Center:
Steps for this task
- Create and deploy 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:
- 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.
You 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.
- If you require messages to be delivered to your application using WebSphere MQ Multicast Transport, configure the
broker to enable multicast. Configure the topics that need to be multicast
enabled, specifying a reliable quality of service for those topics that need
to be configured for reliable multicast.
- If your application supplies a user ID and a password when it connects
to the broker, and you want the broker to authenticate your application using
this information, configure the user name server and the broker for simple
telnet-like password authentication.
Result
You can now start your application.