Use the transaction service

 

+

Search Tips   |   Advanced Search

 

In WAS, transactions are managed by...

• A transaction manager

  Supports the enlistment of recoverable XAResources and ensures that each resource of this type 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 enterprise 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.

• The UserTransaction API

  Used by Bean-managed EJBs and servlets to set transaction demarcations.

  See...

JTA support includes additional APIs so that application frameworks can manipulate the unit of work (UOW) context of a thread, and components can register with a JTA transaction. For example, a persistence manager can be notified of transaction completion.

See...

1. Additional APIs
2. Develop components to use transactions
3. Set transaction properties for an appserver
4. Set transaction properties for peer recovery
5. Manage manual peer recovery of the transaction service
6. Manage active and prepared transactions
7. Manage active and prepared transactions using scripting
8. Manage transaction logging for optimum server availability
9. Interoperating transactionally between appservers
10. Use WS-Transaction policy to coordinate transactions or business activities for Web services
11. Troubleshooting transactions
12. Use one-phase and two-phase commit resources in the same transaction
13. Transaction support in WAS
14. Local transaction containment considerations
15. Transaction service exceptions
16. JTA support
17. Use the ActivitySession service