These topics provide information about using transactions with WebSphere applications

Why and when to perform this task

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. The 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.

• 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:

Related tasks
Implementing WebSphere enterprise applications that use ActivitySessions