Weblogic Integration 9.2 Transaction Boundaries

Weblogic Integration 9.2 Transaction Boundaries

Adding any receive (blocking) nodes (Client Request or Control Receive nodes) to a business process changes the transaction boundaries:
Unless the node is in the beginning of a business process, the new receive node marks the beginning of a new transaction.
The node immediately preceding the new receive node marks the end of the preceding transaction.
Adding a Parallel group node to a business process changes the transaction boundaries:
The node immediately preceding the Parallel group node marks the end of the preceding transaction.
The beginning of each branch in a Parallel group node marks the beginning of a new transaction.
The end of each branch in a Parallel group node marks the end of the new transaction.
The node immediately following the Parallel group node marks the beginning of the next transaction.
Adding an Event Choice node to a business process changes the transaction boundaries:
The node immediately preceding the Event Choice group marks the end of the preceding transaction.
The new group node marks the beginning of a new transaction.
Unlike the case of a Parallel node, in which each branch in the Parallel node has its own transaction context, the end of the Event Choice group does not mark the end of the transaction. Execution continues in the same transaction after the Event Choice group until a node that forces an implicit transaction boundary or an explicit boundary is reached.
Existing transaction boundaries are unaffected by adding one or more nodes (within those boundaries) that do not themselves force a transaction boundary.