Explicit Transactions
You use explicit transactions when you need to explicitly control the transactional units of work. To do this, you use additional services, known as built-in services, in your flow.
A transaction context starts when the pub.art.transaction.startTransaction() service is executed. The transaction context is completed when either the pub.art.transaction.commitTransaction() or pub.art.transaction.rollbackTransaction() service is executed. As with implicit transactions, a single transaction context can contain no more than one LOCAL_TRANSACTION connection.
Note:
With explicit transactions, you must be sure to call either a commitTransaction() or rollbackTransaction() for each startTransaction(); otherwise you will have dangling transactions that will require you to reboot Integration Server.
A new explicit transaction context can be started within a transaction context, provided that you ensure that the transactions within the transaction context are completed in the reverse order they were started. That is, the last transaction to start should be the first transaction to complete, and so forth.
For example, consider the following is a valid construct:
pub.art.transaction:startTransaction
pub.art.transaction:startTransaction
pub.art.transaction:startTransaction
pub.art.transaction:commitTransaction
pub.art.transaction:commitTransaction
pub.art.transaction:commitTransaction
The following example shows an invalid construct:
pub.art.transaction:startTransaction
pub.art.transaction:startTransaction
pub.art.transaction:commitTransaction
pub.art.transaction:commitTransaction
For more information about designing and using flows, see the webMethods Service Development Help for your release.