2.8.1 Overview of transaction management when connecting to resources
There are two methods of managing transactions when connecting to resources; managing transactions with Application Server and directly managing transactions by a user without managing with Application Server. When connecting to a database, you can manage transactions by using transaction manager with Application Server. For details on the transaction management, see 3.4.1 How to manage transactions in resource connection in the uCosminexus Application Server Common Container Functionality Guide.
A transaction that can be managed with a batch server is a local transaction. You cannot use global transactions. Make sure to enable the light transaction functionality on a batch server. Light transaction functionality is a functionality which provides an environment, which is optimized with local transactions. For details on the local transactions and light transaction functionality, see 3.4.2 Local transactions and global transactions in the uCosminexus Application Server Common Container Functionality Guide.
When invoking EJBs, if a system exception occurs at invocation destination, transactions at invocation source and invocation destination operate as follows.
- Transactions at invocation source
-
Transactions are not marked for rollback.
- Transaction at invocation destination
-
Transactions are rolled back by container. These operations are defined in EJB specifications.