Using the transaction service

Using the transaction service

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:

For more information about using transactions with WebSphere applications, see the following topics:


Sub-topics
Transaction support in WebSphere Application Server
Developing a component to use transactions
Configuring transaction properties for an application serverConfiguring transaction properties for peer recovery
Managing manual peer recovery of the transaction service
Using local transactions
Managing active transactions
Managing transaction logging for optimum server availability
Interoperating transactionally between application servers
Troubleshooting transactions
Transaction service exceptions
UserTransaction interface - methods available
Coordinating access to 1-PC and 2-PC-capable resources within the same transaction

Related tasks
Implementing WebSphere enterprise applications that use ActivitySessions