Copyright © Cloud Software Group, Inc. All Rights Reserved

Overview of Transactions and Transaction Control Steps

A transaction is one unit of work. The iProcess Background process carries out this unit of work. It uses messages that are stored in repositories called Mboxes. Mboxes provide the communication link between iProcess Workspace (Windows) and the iProcess Engine.

A transaction is when the iProcess Background process:

•	reads the message from an Mbox

•	processes a number of steps

•	commits the resulting data back to the database.

This represents one transaction. See "Mbox Sets and Message Queues" in TIBCO iProcess Engine Architecture Guide for more information.

The iProcess Background process bundles all consecutive/concurrent EAI steps into the same transaction. If there is a failure in one step then all steps are rolled back.

TC steps can be used to break up sequences of EAI steps into multiple transactions.

Copyright © Cloud Software Group, Inc. All Rights Reserved