Note:
The WebLogic JMS resource adapter is deprecated as of Oracle WebLogic Server 12.2.1.3.0, and will be removed in a future release. Oracle recommends that you use either the thin T3 client or a message bridge to integrate applications running on non-WebLogic application servers through JMS. See the following topics:
Developing a WebLogic Thin T3 Client in Developing Standalone Clients for Oracle WebLogic Server
Understanding the Messaging Bridge in Administering the WebLogic Messaging Bridge for Oracle WebLogic Server.
WebLogic JMS Resource Adapter in What’s New in Oracle WebLogic Server 12.2.1.3.0
WebLogic Server provides a Java EE Connector Architecture version 1.7 compliant resource adapter called the JMS resource adapter to provide an integration of a WebLogic JMS client with supported foreign application servers.
The JMS resource adapter includes the following features:
Implementation of the Java EE Connector Architecture outbound and inbound contract for JMS.
JNDI mapping to reference JMS connection factories and destinations.
Message-drive bean (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.
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 messaging system 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.
Support for the WebLogic security model.
Advanced poison message handling. The JMS resource adapter can be configured to automatically redirect messages that have been redelivered multiple times to a designated error destination.
Simplified configuration of multiple destination JNDI mappings through the use of a single destination context resource adapter 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.
This release of the JMS resource adapter is supported for deployment on Oracle GlassFish version 3.1 and higher.
Note:
Deploying the JMS resource adapter on Oracle WebLogic Server is not supported.
This release of the JMS resource adapter supports foreign application server interoperability with destinations in Oracle WebLogic Server releases 12.1.2 and higher.