Sharding with JTA/XA Transaction in WebLogic Server

13.7 Sharding with JTA/XA Transaction in WebLogic Server

Starting from Oracle Database 23ai Release, you can use sharding with JTA/XA transactions, when you configure UCP as a native data source in WebLogic Server. This feature broadens UCP middle-tier coverage to include more applications, like the ones that require container-managed JTA/XA transactions or sharding.

Java Transaction API (JTA) specifies standard Java interfaces between a transaction manager and the parties involved in a distributed transaction system: the resource manager, the application server, and the transactional applications. Now, Java Enterprise applications that use UCP native data source sharding APIs, to obtain connections to Oracle sharded databases, can participate in JTA/XA transactions managed by WebLogic Transaction Manager (TM).

For any XA transaction with all supplied sharding keys parameter in the connection requests, which lead to the same Oracle sharded database instance, the XA transaction goes through successfully and commits the changes. For an XA transaction, leading to different Oracle sharded database instances, UCP native data source raises an exception to the WebLogic Transaction Manager and the transaction is rolled back.