Transaction Management of Messages For a queuing technology to be transactional it must be under the control of a Resource Manager. The resource manager ensures that its resources, the queues, are always in a consistent state. Any updates, i.e. the sending or receiving of messages, made during a transaction will either all succeed or all fail. UNIX Oracle Transaction Implementation When using the UNIX Oracle version of an iProcess Engine, all resources are updated in an iProcess transaction as one unit of work. This is because the message queues are maintained in the database and can therefore be controlled by the Oracle Resource Manager. Transactions are limited to the scope of this database as the resource manager only controls this database. Refer to the Oracle Database documentation for more information about how Oracle handles resource management. Windows SQL Server Transaction Implementation The TIBCO iProcess Engine uses the Microsoft SQL Server database to store iProcess messages. The SQL Server makes sure the queues are in a consistent state and will make sure that all resources updated during a transaction are committed as one unit of work. UNIX DB2 Transaction Implementation When using the UNIX DB2 version of an iProcess Engine, all resources are updated in an iProcess transaction as one unit of work. This is because the message queues are maintained in the database and can therefore be controlled by the DB2 Resource Manager. Transactions are limited to the scope of this database as the resource manager only controls this database.