Use the transaction service


WebSphere applications can use transactions to coordinate multiple updates to resources as atomic units such that all or none of the updates are made permanent.

In WAS, transactions are handled by three main components...

  1. A transaction manager that supports the enlistment of recoverable XAResources and ensures that each such resource is driven to a consistent outcome either at the end of a transaction or after a failure and restart of the appserver.

  2. A container in which the J2EE application runs. The container manages the enlistment of XAResources on behalf of the application when the application performs updates to transactional resource managers (for example, databases). Optionally, the container can control the demarcation of transactions for enterprise beans configured for container-managed transactions.

  3. An application programming interface (UserTransaction) that is available to bean-managed enterprise beans and servlets. This allows such application components to control the demarcation of their own transactions.


See also

  1. Transaction support in WAS
  2. Using local transactions
  3. Developing components to use transactions
  4. Configuring transaction properties for an appserver
  5. Managing active transactions
  6. Managing transaction logging for optimum server availability
  7. Interoperating transactionally between appservers
  8. Troubleshooting transactions
  9. Transaction service exceptions
  10. UserTransaction interface - methods available