Chapter 5. Runtime patterns and product mappings 105
To use the services of a WebSphere MQ transport layer, an application must
make a connection to a WebSphere MQ queue manager, the services of which
will enable it to receive (
get) messages from local queues, or send (put)
messages to any queue on any queue manager. The application’s connection
may be made directly (where the queue manager runs locally to the application)
or as a client to a queue manager that is accessible over a network.
Dynamic workload distribution is another important feature of WebSphere MQ.
This feature shares the workload among a group of queue managers that are
part of the same cluster. This allows WebSphere MQ to automatically balance
the workload across available resources, and provide hot standby capabilities if a
system component fails. This is a critical feature for companies that need to
maintain round-the-clock availability.
WebSphere MQ supports a variety of application programming interfaces
(including MQI, AMI, and JMS), which provide support for several programming
languages as well as point-to-point and publish/subscribe communication
models. In addition to support for application programming, WebSphere MQ
provides a number of connectors and gateways to a variety of other products,
such as Microsoft® Exchange, Lotus® Domino®, SAP/R3, CICS®, and IMS™,
to name just a few.
More information can be found at the IBM WebSphere MQ Web site:
http://www.ibm.com/software/ts/mqseries
5.4.3 WebSphere Business Integration Message Broker
WebSphere Business Integration Message Broker V5.0 extends the messaging
capabilities of WebSphere MQ by adding message routing, transformation, and
publish/subscribe features. Message Broker provides a runtime environment that
executes message-flows. These message-flows consist of a graph of nodes that
represent the processing needed for integrating applications. They can be
designed to perform a wide variety of functions, including these:
? Routing of messages to zero or more destinations based on the contents of
the message or message header (both one-to-many and many-to-one
messaging topologies are supported).
? Transformation of messages into different formats so that diverse applications
can exchange messages that each of them can understand.
? Enrichment of the message content en route (for example, by using a
database lookup performed by the message broker).
? Storing information extracted from messages en route to a database (using
the message broker to perform this).