Supported Databases

You must install TIBCO iProcess Engine with 32-bit and 64-bit Oracle 19c client before beginning the iPE installation.

Set ORACLE_HOME to 32-bit Oracle installed path in the environment variable.

Oracle Services for Microsoft Transaction Server (ORAMTS)

To see if ORAMTS is installed on your system, run the Oracle Universal Installer and click the Installed Products button. If you need to install this component, perform a Custom installation and select the appropriate product from the list.

Oracle Services for Microsoft Transaction Server (ORAMTS)

To see if ORAMTS is installed on your system, run the Oracle Universal Installer and select Installed Products. If you need to install this component, perform a Custom installation and select the product from the list.

You will need access to an Oracle Metalink account to be able to access the required patches and patch sets.

TIBCO iProcess Engine uses Oracle Call Interface (OCI) to access data in the Oracle database. For stability purposes only, TIBCO iProcess Engine is statically linked with the Oracle client libraries that provide the required OCI routines. Oracle only supports products that run against the same set of libraries that they were built with. This means you must use particular Oracle Client versions, depending on the method you use to connect to the database.

If you are using Oracle Real Application Clusters (RAC), TIBCO recommends that you install the iProcess Engine on a machine that is not part of the RAC, and use a TNS connection to connect to the remote database.

When you install iProcess Engine with SQL Server, but without the DBA role, the following error message appears:

The User does not have permissions to add the linked server.

You can ignore this message and continue to install iProcess Engine. To make sure that SSOLITE works correctly, you need to use the DBA role to run the following script after the installation:

$SWDIR/util/sql_check_linkedserver.sql

TIBCO strongly recommends that you install iProcess Engine against a SQL Server instance that uses Mixed Mode authentication (where database connections can be authenticated using either SQL Server login IDs or passwords, or Windows accounts). The installer normally creates or uses SQL Server logins to enable the iProcess Engine to connect to the SQL Server instance.

Although iProcess Engine can use Windows-authenticated accounts to access the SQL Server database, there are currently some restrictions associated with this mode of operation that require changes to the installation procedures described in this documentation.

If you want to install the iProcess Engine against a SQL Server instance that uses Windows Only authentication, see “Installing iProcess Engine Against a SQL Server Instance That Uses Windows Only Authentication” in TIBCO iProcess Engine (SQL Server) Release Notes for more information before proceeding further.

SQL Native Client

The SQL Native Client driver is not automatically provided on the Windows operating systems supported by this version of the iProcess Engine. It is installed as part of SQL Server.

If you do not have SQL Server installed on the computer where you intend to install iProcess Engine, and you intend to use a SQL Server that is installed on a remote computer, you have to download the SQL Native Client version 11 or above from the Microsoft Download Center. For example, you can download the SQL Native Client driver for SQL Server from https://www.microsoft.com/en-us/download/details.aspx?id=50402.