Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter Installation and User’s Documentation | About Oracle Apps Adapter | Adapter Connections | Transaction Management of Oracle Apps Adapter Connections
 
Transaction Management of Oracle Apps Adapter Connections
Oracle Apps Adapter connections support the LOCAL_TRANSACTION transaction type. With this transaction type, all of the operations on the same connection in one transaction boundary will be committed or rolled back together. A transaction boundary means the scope of the transaction, from the beginning to the end of a transaction. It can be in one adapter service, one flow service, one Java service, or several steps in a flow service. This transaction type maintains the integrity of your business documents.
Note:
The adapter also provides a NO_TRANSACTION type; however, we strongly suggest that you do not use it. Using this type of configuration the connection automatically commits (Auto Commit) all database operations.
When you configure a connection, the transaction type that you choose determines the type of transaction management that the connection's operations use implicitly. Implicit transactions are managed by the Integration Server transaction manager.
You can also explicitly manage transactions using built-in services. See Built-In Transaction Management Services for information about, and examples of, explicitly managing transactions.