XA support for WebLogic 10.3 is subject to the limitations of BEA's XAResource implementation as given below.

The XAResource that the adapter obtains from WebLogic and passes on to the built-in transaction manager represents an interface to the WebLogic server's transaction manager. In a distributed context, the WebLogic transaction manager would be responsible for coordinating all resources local to that server, yet still subordinate to Integration Server transaction manager. Integration Server transaction manager in effect, is the master transaction manager.

WebLogic's XAResource is designed to work in this environment provided that it is the only WebLogic XAResource involved in the entire distributed transaction. For example, you can use two or more XA-connected adapter services in a distributed transaction as long as those services are connected to the same WebLogic server. For this same distributed transaction, other, non-WebLogic resources may be included.

However, you cannot include an XAResource from two or more different WebLogic servers. For instance, two XA-connected adapter services that are connected to different WebLogic servers cannot be involved in the same distributed transaction.

For more information on WebLogic Server 10.3, see the Oracle web site.