web server - Borland Technical Publications

Chapter
24
24JMS provider pluggability
Chapter
Important
For documentation updates, go to www.borland.com/techpubs/bes.
BES is designed to support any arbitrary JMS provider as long as some requirements
are met. There are three levels of JMS pluggability: runtime pluggability, configuration
of JMS admin objects (connection factories and queues/topics), and service
management. You will achieve the best results if all three are met, but just having the
runtime level pluggability, as well as vendor-specific ways to achieve the other levels,
may be sufficient in many situations.
BES 6.5 bundles three JMS providers - Tibco JMS 3.1.1 V22, Sonic 6.0, and OpenJMS
0.7.6.1. OpenJMS is bundled as a partition level service.
JMS provider clustering and security are also discussed in this section.
Runtime pluggability
Runtime pluggability is determined by compliance to the J2EE specification. A CTS
compliant JMS product that additionally implements the JMS specification optional
APIs can seamlessly plug into the BES runtime. All features like transactions and MDB
support are retained.
JMS products must possess the capability to perform transactional messaging to
support MDBs and J2EE container intercepted messaging. That is, a JMS queue or
topic must be a transactional resource. BES requires that JMS products implement the
JTA XAResource interface and support JMS XA APIs.
In addition, the JMS product should support the javax.jms.ConnectionConsumer
interface. The latter is vital since a central idea of MDBs is the concurrent consumption
of messages. The ConnectionConsumer interface achieves this. The mechanism also
works in conjunction with some optimal methods of the javax.jms.Session objects,
namely Session.run() and Session.setMessageListener().
Additionally, BES 6.5 passed CTS 1.3.1 on both JMS providers.
Chapter 24: JMS provider pluggability 221