user manual

Chapter 24: JMS provider pluggability 253

Chapterb

Chapter 24JMS provider pluggability

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.

JMS provider clustering and security are also discussed in this section.

Note Tibco JMS is bundled with BES 6. Sonic 5 is certified, but not bundled with

BES. Sonic must be acquired and installed separately, and the sonic.config

file must be updated to let BES know where Sonic is installed. The location of

this file is <install_dir>\bin\sonic.config. The JMS home is the Sonic home

directory, the root directory of the Sonic install, for example, jms.home = <sonic

home>.

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