Using AQ Destinations as Foreign Destinations Driver Support Transaction Support

7-2 Configuring and Managing JMS for Oracle WebLogic Server

7.1.1 Using AQ Destinations as Foreign Destinations

AQ foreign destinations must be local to the server running the application or MDBs sendingreceiving messages. An application that is running on one WebLogic Server instance cannot look up and use an AQ JMS foreign server and data source that is registered on another WebLogic Server instance. WebLogic AQ JMS uses a data sourceDB connection that does not support remote connectivity. An alternative is to use a messaging bridge between AQ destinations in one domain and applicationsMDBs running in another domain. See Section 7.4.2, WebLogic Messaging Bridge.

7.1.2 Driver Support

WebLogic AQ JMS requires a JDBC driver to communicate with the Oracle database. Only the Oracle JDBC 11g thin driver, included in your WebLogic Server installation, is supported for this release. Oracle OCI JDBC Driver and non-Oracle JDBC Drivers are not supported.

7.1.3 Transaction Support

Global XA JTA transactions and local JMS transacted session transactions are supported. Global transactions require use of XA based connection factories, while local transactions use non-XA based JMS connection factories. ■ If you select a non-XA JDBC driver, you can only use WebLogic AQ JMS in local transactions. ■ If you select an XA JDBC driver, you can use WebLogic AQ JMS in both local and global transactions. ■ This release does not support non-XA JDBC driver data sources with any of the global transaction options such as Logging Last Resource LLR, One-Phase Commit JTS, and Emulated Two-Phase Commit. If Supports Global Transactions is selected, WebLogic Server logs a warning message. ■ Global transactions are only supported with an XA JDBC driver One-Phase commit optimization. If you use the same XA capable data source for both AQ JMS and JDBC operations, the XA transactional behavior is equivalent to having two connections in a single data source that is treated as a single resource by the transaction manager. Therefore, if the AQ JMS and JDBC operations are invoked under the same JTA transaction, and no other resources are involved in the transaction, the transaction uses One-Phase commit optimization instead of Two-Phase commit; otherwise read-only optimization is used. See Understanding Transactions in Programming JMS for Oracle WebLogic Server

7.1.4 Oracle RAC