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 WAS, transactions are handled by three main components:
Transaction manager 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 application server. J2EE application 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. UserTransaction API Allows bean-managed enterprise beans and servlets to control the demarcation of their own transactions.
See also
Transaction support in WAS
Develop a component to use transactions
Configure transaction properties for an application server
Configure transaction properties for peer recovery
Use local transactions
Manage active transactions
Manage transaction logging for optimum server availability
Interoperating transactionally between application servers
Troubleshoot transactions
Transaction service exceptions
UserTransaction interface - methods available
Coordinate access to 1-PC and 2-PC-capable resources within the same transaction
Related Tasks
Implement WebSphere enterprise applications that use ActivitySessions