Using Enterprise Application Integration Steps in Procedures

To keep control of external transactions with third party applications and to keep the transactions under the control of the transaction manager, you can use EAI steps in your procedure definition. There are different types of EAI steps used to communicate with different types of external systems. For example:

•

The EAI Database steps are used to communicate with the database-stored procedures, so that you can use the existing business logic in your procedures. See the TIBCO iProcess™ Modeler - Integration Techniques Guide for more information about installing and using EAI Database steps.

•

The COM+ EAI step is used so that iProcess can communicate with a COM+ application. See the TIBCO iProcess™ COM Plug-in: User Guide for more information about installing and using the COM EAI step.

An EAI step causes the iProcess background to call-out to an application defined sub-system to perform work. In the MSDTC version, this work may be included within the current distributed transaction. Hence, combining data updates performed by that work with the data updates performed as part of the workflow case processing.

For more information about using EAI steps, see the “Using Enterprise Application Integration Steps” topic in the TIBCO iProcess Modeler - Integration Techniques Guide.