Adapter for Enterprise JavaBeans 6.5 SP3 | webMethods Adapter for Enterprise JavaBeans Documentation | webMethods Adapter for Enterprise JavaBeans Installation and User’s Documentation | Built-In Transaction Management Services | Transaction Management Overview | Transaction Types
 
Transaction Types
Adapter for Enterprise Javabeans supports local transactions with all supported application servers, without other resource participants. Adapter for Enterprise Javabeans also supports XA transactions only on WebLogic Server 10.3. For a description of the transaction types supported by the Adapter for Enterprise Javabeans, see Transaction Management of Adapter for Enterprise Javabeans Connections.
In general, the Adapter for Enterprise Javabeans can communicate with multiple application servers (resources) at a time provided that those application servers are the same vendor and version. There are limitations when the adapter tries to access multiple resources using locally transacted connections within a single flow service.
Note:
If a transaction accesses multiple resources, and more than one of the resources only supports local transactions, the integrity of the transaction cannot be guaranteed. For example, if the first resource successfully commits, and the second resource fails to commit, the first resource interaction cannot be rolled back; it has already been committed. To help prevent this problem, Integration Server detects this case when connecting to more than one resource that does not support two-phase commits. It throws a run-time exception and the service execution fails.
Also remember that the application server, the EJB container, and the EJB itself may impose their own set of restrictions on how an EJB may be used in a transaction.