This chapter describes an overview of WebLogic JMS Resource Adapter components, concepts, and functionality in WebLogic Server 12.1.3.
This chapter includes the following sections:
WebLogic Server provides a Java EE Connector Architecture version 1.6 compliant resource adapter called the JMS Resource Adapter (JMS RA) to provide an integration of a WebLogic JMS client with supported foreign application servers.
The JMS RA includes the following features:
Implements the JCA outbound and inbound contract for JMS.
JNDI mapping to reference JMS connection factories and destinations.
MDB integration (including dynamic adjustment to changing message load)
JMS connection pooling
Lazy resolution of JMS operations (including start order independence, tolerance of dynamic management such as starts and stops of JMS providers, and connection retries in case of provider failure). See Lazy Enlistment of Connections in a Transaction.
Cluster-capable XA support for WebLogic JMS that transparently integrates with non-WebLogic Transaction Managers and correctly recovers from all typical failure conditions. See Transaction Recovery.
Support for asynchronous message processing that ensures all active members of a distributed destination are always serviced – no trapped messages. In addition, asynchronous messaging provides advanced publish/subscribe options, such as a single logical durable subscription partitioned across a distributed topic.
Support for WebLogic JMS extensions that allow you to cast adapter wrapped objects to WebLogic JMS interfaces. See Support for the weblogic.jms.extension API.
Support for the WebLogic security model. See Securing JMS RA Connections.
Advanced poison message handling. The JMS RA can be configured to automatically redirect messages that have been redelivered multiple times to a designated error destination. See Using an Exception Queue.
Simplified configuration of multiple destination JNDI mappings through the use of a single destination context RA administrative object. This allows applications to directly reference any number of destinations and avoid the need to configure multiple administrative objects and resource-env references. See Using Automatic Destination Wrapping.
This release of the JMS RA is supported for deployment on Oracle GlassFish version 3.1 and higher.
Note:
Deploying the JMS RA is not supported on any Oracle WebLogic Server release. The JMS RA fails gracefully if deployed on WebLogic Server.This release of the JMS RA supports foreign application server interoperability with destinations in Oracle WebLogic Server releases 12.1.2 and higher.
The wljmsra.jar file is located in the WL_HOME\server\lib directory of your WebLogic Server installation.