Use the transaction service
Overview
WebSphere applications can use transactions to coordinate multiple updates to resources as atomic units (as indivisible units of work) such that all or none of the updates are made permanent.
In WebSphere Application Server, transactions are handled by three main components:
- 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.
- 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.
- 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.
For more information about using transactions with WebSphere applications, see the following topics:
- Transaction support in WAS
- Developing components to use transactions
- Configure transaction properties for an appserver
- Using local transactions
- Setting transactional attributes in the deployment descriptor
- Using bean-managed transactions
- Managing active transactions
- Troubleshooting transactions
- Transaction service exceptions
- UserTransaction interface - methods available
See Also
- Transaction support in WAS
- Using local transactions
- Transactional interoperation with non-WebSphere appservers
- Transaction service exceptions
- UserTransaction interface - methods available
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.