For a summary of key deployment elements for MDBs, see Deployment Elements and Annotations for MDBs. For an introduction to key deployment elements for topic MDBs, see Configuring and Deploying MDBs Using JMS Topics.
This chapter includes the following sections:
The steps in the following section assume that you have access to the appropriate JMS components:
A JMS connection factory.
A connection factory must be XA transaction (global JTA transaction) capable in order to support transactional MDBs.
The default WebLogic JMS MDB connection factory is XA-capable, is automatically generated on WebLogic clusters, and is sufficient for the majority of MDBs that consume from WebLogic JMS destinations. For information about WebLogic JMS default connection factories, see Using a Default Connection Factories Defined by WebLogic Server in Administering JMS Resources for Oracle WebLogic Server.
For instructions about how to create a custom WebLogic JMS connection factory, see Create connection factories in a system module in Oracle WebLogic Server Administration Console Online Help.
The default behavior and configuration methods for other JMS provider connection factories vary. If you use a non-Oracle JMS provider, see the vendor documentation for details.
A JMS destination
For instructions on configuring WebLogic JMS destinations, see Configure Messaging in Oracle WebLogic Server Administration Console Online Help.
Note:
If your JMS provider is a remote Oracle WebLogic Server JMS provider or a foreign JMS provider, and you use the wrapper approach recommended in Whether to Use Foreign JMS Server Mappings, in addition to configuring the non-local JMS components, you must also configure a Foreign Connection Factory and Foreign JMS Destination in your local JNDI tree.