Use the transaction service

+

Search Tips   |   Advanced Search

 

 

 

Overview

WAS applications 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 managed by three main components:

  1. 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 appserver.

  2. J2EE application container

    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. UserTransaction API

    Available to bean-managed enterprise beans and servlets. These application components can use the UserTransaction interface to control the demarcation of their own transactions.

    For details about the methods available with the UserTransaction interface, see...

 

Procedure

  1. Develop components to use transactions
  2. Configure transaction properties for an appserver
  3. Configure transaction properties for peer recovery
  4. Manage manual peer recovery of the transaction service
  5. Manage active and prepared transactions
  6. Manage transaction logging for optimum server availability
  7. Interoperate transactionally between appservers
  8. Configure Web Services Atomic Transaction support in a secure environment
  9. Configure an intermediary node for Web services transactions
  10. Enable WAS to use an intermediary node for Web services transactions
  11. Configure a server to use business activity support
  12. Create an application that uses the business activity support
  13. Troubleshoot transactions
  14. Use one-phase and two-phase commit resources in the same transaction
  15. Use the ActivitySession service


Transaction support in WAS
Developing components to use transactions
Configure transaction properties for an appserver
Configure transaction properties for peer recovery
Manage manual peer recovery of the transaction service
Local transaction containment considerations
Manage active and prepared transactions
Manage transaction logging for optimum server availability
Interoperating transactionally between appservers
Configure Web Services Atomic Transaction support in a secure environment
Configure an intermediary node for Web services transactions
Enabling WAS to use an intermediary node for Web services transactions
Configure a server to use business activity support
Creating an application that uses the business activity support
Business activity API
Troubleshooting transactions
Transaction service exceptions
Use one-phase and two-phase commit resources in the same transaction

 

Related concepts

Extended JTA support

 

Related tasks

Use the ActivitySession service