The IBM WebSphere MQ product enables application programs
to communicate with each other using messages and queues.
This form of communication is referred to as asynchronous
messaging. It provides assured, once-only delivery of
messages. Using WebSphere MQ means that you can separate
application programs, so that the program sending a message
can continue processing without having to wait for a reply
from the receiver. If the receiver, or the communication
channel to it, is temporarily unavailable, the message can
be forwarded at a later time. WebSphere MQ also provides
mechanisms for generating acknowledgements of messages
received.
The Transaction Server extends the base of the WebSphere MQ product by providing direct connection between the intelligent device and the enterprise system using WebSphere MQ as the transport.
The following provides an overview of the node and
parameters that you will set in order to use WebSphere MQ
as a transport. 
Before the WebSphere MQ transport can be implemented, a queue manager, associated queues, and a message channel must be created. WebSphere MQ provides the utilities to do this and to create any other objects that are needed for transaction processing.
Assumptions
Before you begin, it is assumed that:
- The IBM WebSphere MQ, Version 5.3 (or later) was
installed and configured as appropriate for your
operating environment and local area network.
- The WebSphere MQ administrator created the queue
manager and associated queues and has given you their
names.
- The WebSphere MQ administrator created a
communication channel and has given you the name of the
channel.
- You have the IP address (or host name) of the computer where WebSphere MQ is installed.
What's Inside