B2B Integration : A Practical Guide to Collaborative E-commerce

230 B2B Integration — A Practical Guide to Collaborative E-commerce
V.
Message
Prod ucer Creates
I Sends to
f Connection "\
\ Factory )
• Creates
Connection I
1 Creates
Session
• Creates
Message
^^^^< Message
Qeates Consumer
Figure 8.6. — JMS building blocks
I Receives From
Destination }
• Administered objects are pre-configured JMS administered objects used
by clients. There are two kinds of administered objects, destinations
and connection factories.
• JMS domains allow classification of the messaging environment as
either point-to-point or request/reply. The domains are implemented
using the JMS API. One or both domains can be supported in a
single application.
Non-JMS clients are programs that use a messaging product's native
client API instead of the JMS API. If the application predated the
availability of the JMS API, it is likely to include both JMS and non-
JMS clients.
JMS promises to work in concert with other MOM products to
provide reliable, asynchronous communication among components in
a distributed computing environment. Using the JMS interface, an
application can invoke the messaging services of IBM's MQSeries,
Progress Software's SonicMQ and other popular messaging product
vendors. Similar to MSMQ, JMS supports messages that contain
serialized Java objects, as well as messages that contain extensible
markup language (XML) pages.