user manual

255 BES Developer’s Guide
Configuring admin objects
ConnectionConsumer interface since a central idea of MDBs is the concurrent
consumption of messages. The ConnectionConsumer achieves this, and
works in conjunction with some optimal methods of the javax.jms.Session
objects.
Tibco and Sonic
Tibco and Sonic have already achieved the runtime level of pluggability.
Additionally, BES 6.0 passed CTS 1.3.1 on both JMS providers.
Other JMS providers
For other JMS providers to achieve a runtime level of pluggability, compliance
with the J2EE specifications is necessary. BES requires that the JMS XA APIs
support JTA integration. In addition, the JMS product should support the
ConnectionConsumer interface. Refer to Sun's chapter on the JMS API for
specific information on complying with the specification.
Configuring admin objects
The next level of pluggability, involves configuring admin ojects, like queues,
topics and connection factories. The BES DDEditor tool can define, edit and
deploy these objects into the BES JNDI tree without needing a JMS product-
specific mechanism.
Tibco and Sonic
Both Tibco and Sonic achieve this level of pluggability. Their admin object
properties are defined in BES and can be configured graphically, using the
DDEditor.
To set the following admin object properties using the DDEditor:
1 Launch the DDEditor from within the Management Console or standalone
from the Start menu.
2 Select New and JNDI Definitions Archive to create a new JMS object.
3 Right-click and select New JMS Object.
4 Give the JMS object a name in the New JMS Object window and click OK.
Your JMS object will appear under your archive.
5 Click on your JMS object, and select the Main tab.
6 Configure your object by selecting various fields from the drop-down menus
and entering information in the properties' fields.