Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Introduction to Transactional Business Process Automation : Transaction Scope

Transaction Scope
The following sections describe the scope of transactions on the different versions of the TIBCO iProcess Engine.
Oracle Server Transaction Scope
The Oracle version of the TIBCO iProcess Engine enables you to use one local resource manager (provided by the Oracle resource manager).
Because the TIBCO iProcess Engine uses Oracle Advanced Queues to store its internal instruction messages and Oracle tables to store case data, transaction management can be controlled by the internal Oracle database transaction manager.
This means that if updates to the Oracle database fail, the resource manager can roll back the updates and restore the database and case data to its original state.
DB2 Transaction Scope
The DB2 version of the TIBCO iProcess Engine enables you to use the local DB2 resource manager.
This means that if updates to the DB2 database fail, the resource manager can roll back the updates and restore the database and case data to its original state.
SQL Server Transaction Scope
When using the iProcess Suite with the Microsoft SQL Server, all transactions are managed by the SQL Server resource manager. SQL Server provides the following transaction functionality:
When all the processes use the local resource manager on the SQL Server, this is called a local transaction. If some processes use an external resource manager such as the EAI COM step, then this is known as a distributed transaction because more than one resource manager is used. A slightly different architecture is used for distributed transactions because a transaction manager program is used to control the resource managers. Refer to Using Distributed Transactions with MSDTC for more information.
Using Distributed Transactions with MSDTC
Windows has a built in transaction manager component called Microsoft Distributed Transaction Coordinator (MSDTC). The MSDTC controls resource managers from distributed sources such as SQL Server and COM.
The transaction scope provided with this architecture allows distributed transactions involving many resource managers to be controlled by the MSDTC. Some server EAI plug-ins such as EAI COM+ may require a distributed transaction and therefore need to use MSDTC. You can set the TIBCO iProcess Engine to use MSDTC by setting the EAI_NEEDS_MSDTC process attribute - refer to “Administering Process Attributes” in the TIBCO iProcess Engine: Administrator's Guide for more information about setting process attributes.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved