web server - Borland Technical Publications

Other JMS providers
Using Message Driven Beans (MDB) with OpenJMS
Important
For a BES partition to support MDBs, the MDB must be able to access a JMS server.
To make the MDB access the OpenJMS server, make sure that:
1 OpenJMS is installed and enabled as an in-process service in your partition or
available in the domain. Right-click on the OpenJMS service and select Start from
the menu to enable the service.
2 The resource references are properly configured in the ejb-jar.xml file to point to
the right type of connection factory.
If your MDB needs transactional access, you must use Embedded or RMI
connection factories with your MDB so as to support transaction propagation.
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.
Note
Required client libraries for other JMS providers
When trying to connect to another JMS provider the required libraries must first be
deployed to the target Partition. The steps are:
1 Start your BES server and Management Console.
2 From the Console, open the Wizards menu and select the Deployment Wizard. The
wizard allows you to deploy modules to a Partition.
3 “Add” the library file and check the option to restart the Partition on deploy.
4 Proceed to deploy to the chosen Partition(s). Close the wizard.
You should see your libraries listed under the “Deployed Modules” folder of the
Partition(s). The Borland Deployment Descriptor Editor panels do not provide as much
custom help for other JMS vendor products as it does for JMS vendors certified to work
with BES. Refer to the other JMS vendor's documentation to ascertain the correct
name of the ConnectionFactory, Topic or Queue implementation class in order to
create JNDI objects.
All required libraries are already configured so nothing extra is needed if you are going
to use JMS services bundled with BES.
Configuring admin objects for other JMS providers
BES provides configurations in the Borland Deployment Descriptor Editor for Tibco,
Sonic and other JMS providers. However, there are required properties and classes for
using other JMS providers with BES. These must be configured in the jms.properties
file located in C:\Documents and Settings\username\.bmc60.
Chapter 24: JMS provider pluggability 237