Use the built-in services described in this section to manage explicit transactions for your Adapter Development Kit services.

Explicit transactions are transactions that you manually control within flow services through the use of built-in services. Implicit transactions are automatically handled by the Integration Server's transaction manager. When you define an explicit transaction, it is nested within the implicit transactions that are controlled by the transaction manager. You can have more than one explicit transaction defined within an implicit transaction. You can also nest explicit transactions within each other.

Any flow service steps found between a WmART.pub.art.transaction:startTransaction service and either a WmART.pub.art.transaction:commitTransaction service or a WmART.pub.art.transaction:rollbackTransaction service are part of an explicit transaction rather than the implicit transaction.

Within both implicit and explicit transactions, you cannot have multiple connections with a transaction type of LOCAL_TRANSACTION because you will not be able to rollback the first LOCAL_TRANSACTION adapter service after it is committed. Use the built-in services to define explicit transactions to prevent you from inadvertently committing transactions if you need to rollback the transaction.