Is It Necessary to Use TIBCO iProcess COM Server Plug-in
The iProcess COM Server Plug-in is a component of the iProcess Engine that you can choose to register when you run the installer, see Select Components To Configure for details. You need to register this plug-in if the iProcess Engine will handle procedures that use EAI COM steps to call external COM applications.
|
Note
|
The iProcess COM Server Plug-in can have a significant impact on iProcess Engine performance. TIBCO recommends that you register it only if you need to use EAI COM steps.
|
The iProcess COM Server Plug-in uses the transaction infrastructure provided by the Microsoft Distributed Transaction Coordinator service (MSDTC). This infrastructure imposes security and authentication requirements which can cause permissions problems if the iProcess environment is not set up correctly to support distributed transactions. If such problems occur, the iProcess COM Server Plug-in will not work, see Distributed Transaction Errors Occur When You Start iProcess Engine for details.
Consequently, TIBCO recommends that if you intend to use the iProcess COM Server Plug-in, you make sure that you adhere to the following requirements when installing the iProcess Engine:
|
•
|
The following entities must all be located either on the same machine or in the same domain: |
|
—
|
the Windows iProcess Engine administrator account (IPEADMIN), which runs the iProcess nodeName Process Sentinels service |
|
—
|
the Oracle or SQL Server database |
|
—
|
the Windows account that is running the Oracle or SQL Server database |
|
—
|
the Windows account that is running the Distributed Transaction Coordinator service. |
|
•
|
In a domain, the Distributed Transaction Coordinator service must be running on every machine that is running an iProcess Engine master or slave server, or the Oracle or SQL Server database. |
See TIBCO iProcess COM Plug-in User’s Guide for more information.