Additional System Requirements

Additional system requirements are described:

• POSIX Threads (pthreads)
• Windows Clustering
• TIBCO iProcess Objects
• Activity Publishing and Work Queue Delta Publication
• Java Runtime Environment (JRE)
• LDAP Directory Service

POSIX Threads (pthreads)

When you install or upgrade to TIBCO iProcess Suite Version 11.9.0 on a Windows system, you must have the following files:

• pthread.dll version 2.7.0 (32-bit)
• pthread.dll version 2.9.1 (64-bit)
• msvcr100.dll
Note:

TIBCO has validated Version 2.7.0 with iProcess Engine. If you want to use a later version of the library, contact TIBCO Support to confirm whether or not that version is supported by your iProcess Engine version.

When you install or upgrade TIBCO iProcess Engine to Version 11.9.0, you must use the latest versions of the pthreads library. See Installing or Upgrading TIBCO iProcess Engine to Version 11.9.0.

Downloading the pthreads Library

If you do not already have a POSIX Threads (pthreads) library, you can obtain the POSIX Threads (pthreads) for Windows distribution set from TIBCO Software Inc. by downloading it as follows:

1. Go to the TIBCO Software Product Download Site (https://edelivery.tibco.com) website.

Entry to this site requires a username and password. If you do not have a username, you can request one.

2. To navigate to the product, you can find the product in one of the following ways:
— Search the product name in the search field.
— Click All PRODUCTS A-Z.
— Click AUTOMATION

3. If you navigate to the product by clicking AUTOMATION, click Business Process Management (BPM) in the following page.

4. Click Download under TIBCO iProcess Workspace (Windows) and then click the product version that you want to download.
5. Download the zip file (iprocess_win_pthread_2.9.1_installer.zip). It contains the pthread_installer.bat script and the two pthread.dll files.
6. Extract and run the script to copy the dll files into %windir% folder. This script will copy the files as follows:
— x86\pthread.dll to "%windir%\SysWOW64"
— x64\pthread.dll to "%windir%\system32"
— x64\msvcr100.dll to "%windir%\system32".
Warning:

If a supported version of the pthread.dlllibrary is not available on the system PATH when you run the installer, the installer immediately exits with an error message. See Installation Encounters an Error Trying to Locate pthread.dll for details.

Note 

Additional pthread Requirements for the SAL SDK

If you intend to build any applications using the iProcess Engine’s SAL SDK (installed in SWDIR\sdks\swsalsdk), those applications must include the following files from the POSIX Threads (pthreads) for the following distribution set:

• include\pthread.h
• include\sched.h
• include\semaphore.h
• lib\pthreadVC2.lib

Errors occur if you build applications without including these files.

Windows Clustering

If you want to install the iProcess Engine on a Microsoft Windows cluster, make sure that the necessary cluster management software (listed in Windows Cluster Management Software) is installed on each machine in the cluster.

Windows Cluster Management Software

Operating System

Requirement

Windows Server 2016 (64-bit)

Windows Server 2016 on AWS

Windows Server 2016 (64 Bit) on Azure

Windows Server 2019 (64-bit)

Windows 10 (64-bit)

Supplied as part of the basic operating system.

TIBCO iProcess Objects

The iProcess Objects Server receives requests for services or data from TIBCO iProcess Objects (COM, JAVA, or C++) or TIBCO iProcess Server Objects (JAVA or .NET). The iProcess Objects Server processes the request, then makes the appropriate call to an iProcess Engine to initiate the desired service or obtain the desired information.

The iProcess Objects Director is a stand-alone program that maintains a list of iProcess Objects Servers that are configured in a node cluster. When a client needs access to an iProcess Objects Server, it first establishes a connection to the iProcess Objects Director. The iProcess Objects Director then decides, based on a pick method, which iProcess Objects Server the client should connect to.

If you want to enable the iProcess Objects Server or iProcess Objects Director, you need to take account of additional runtime disk space requirements listed in Additional Runtime Disk Space Requirements for TIBCO iProcess Objects. For more information about enabling iProcess Objects Server or iProcess Objects Director, see Select Components To Configure.

Additional Runtime Disk Space Requirements for TIBCO iProcess Objects

Component

Runtime Disk Space Requirement

iProcess Objects Server

5 MB + Log file

By default, the maximum size of the iProcess Objects Server log file is 15 MB. This can be configured after installation. See TIBCO iProcess Objects Server Administrator’s Guide for more information. The log file is not created during installation. It is created the first time the iProcess Objects Server is used.

iProcess Objects Director

500 KB + Log file

By default, the maximum size of the iProcess Objects Director log file is 15 MB. This can be configured after installation using the LOG_FILE_MAX_SIZE process attribute. (See TIBCO iProcess Objects Director Administrator’s Guide for more information.) The log file is not created during installation. It is created the first time the iProcess Objects Director is used.

Activity Publishing and Work Queue Delta Publication

If activity publishing is enabled, activity information about auditable objects (for example, procedures and steps) can be published to an external application. (The BG process publishes monitored activities to the IAPJMS process.) This enables real-time monitoring of auditable objects so that mission critical or important business events can be easily monitored.

Enabling activity publishing also enables Work Queue Delta publication via JMS. This allows an external application to monitor a work queue and to retrieve only those work items in a given work queue that have changed. In this case, the WIS process publishes messages about the monitored queue to the IAPJMS process, and IAPJMS in turn publishes messages to a JMS topic which can be monitored by the external application. See iProcess Engine Administrator’s Guide for configuring activity publishing and work queue delta publication once they are enabled.

Before you enable activity publishing, you must ensure that the computer hosting iProcess Engine has access to the Java Message Service (JMS) provider that you want to use. This must be one of the following JMS providers listed in JMS Providers.

JMS Providers

JMS Provider

Supported Versions

Additional Requirements

TIBCO Enterprise Message Service (EMS)

8.4.1

8.5.0

If you are upgrading iProcess Engine and you are using EMS, you must ensure that your version of EMS is updated. For more information, see How Do I Upgrade TIBCO EMS.

IBM WebSphere Application Server

8.5.5

The IBM Client for JMS on J2SE with WebSphere Application Server must be installed on the machine hosting the iProcess Engine.

For more information, see Installing the IBM Client for JMS on J2SE with IBM WebSphere Application Server.

Oracle WebLogic Server

12.1.3

12.2.1

If the WebLogic Server is hosted remotely, one of the following WebLogic client types must be installed on the machine hosting iProcess Engine:

WebLogic T3 client (weblogic.jar), or

WebLogic JMS Thin Client (wljmsclient.jar and wlclient.jar)

These JAR files are located in the WL_HOME\server\lib subdirectory of the WebLogic Server installation directory, where WL_HOME is the top-level installation directory for the entire WebLogic Platform (for example, c:\bea\weblogic90\server\lib).

For more information, see Default Java Message Service.

HornetQ

6.4.0

7.0.0

None

Other

The JMS provider can be hosted either on the local machine or on a remote machine. If the JMS provider is hosted remotely, appropriate client application JAR files must be installed on the machine hosting the iProcess Engine. See your JMS provider documentation for more information about required client JAR files. You specify the location of these JAR files when you run the installer. For more information, see Default Java Message Service.

The JMS provider must support Java Virtual Machine (JVM) 11. JVM 11.0.22 is distributed with this version of iProcess Engine, and installed into the SWDIR\java directory.

For more information about how to enable activity publishing, see Select Components To Configure.

Java Runtime Environment (JRE)

The following information is listed in IRE Information:

• the iProcess Engine components and other dependent iProcess products that use Java, and therefore need access to a Java Virtual Machine (JVM) or other JRE libraries on the computer hosting the iProcess Engine.
• the default JRE that each component or product uses to locate the libraries that it needs.
• the configuration tool provided to help you configure the location of the JRE used by each component or product (if applicable).

IRE Information

Component or Product

Default JRE Location

Configuration Tool

IAPJMS process

SWDIR\java

SWLIB_PATH process attribute value

See “Administering Process Attributes” in TIBCO iProcess Engine Administrator’s Guide for more information.

JMX engine

SWDIR\java

None

TIBCO EMS

SWDIR\java

None

TIBCO Hawk

SWDIR\java

None

TIBCO iProcess Server Plug-in for ActiveMatrix BusinessWorks

Selectable when you install the plug-in

TIBCO iProcess Technology Plug-ins installer

See TIBCO iProcess Technology Plug-ins Installation for more information.

TIBCO iProcess Java Server Plug-in

Selectable when you install the plug-in

TIBCO iProcess Technology Plug-ins installer

See TIBCO iProcess Technology Plug-ins Installation for more information.

TIBCO iProcess Engine Web Service Server Plug-in

Selectable when you install the plug-in

TIBCO iProcess Engine Web Services Plug-in installer

See TIBCO iProcess Engine Web Services Plug-in Installation for more information.
Note:

TIBCO strongly recommends that you use the following JRE to provide the necessary Java functionality when using the components and products listed in IRE Information.

JRE 11.0.22, which is distributed with this version of the iProcess Engine and installed into the SWDIR\java directory.

You can identify this JRE by running the SWDIR\java\bin\java -version command, which displays output similar to the following:

java version "11.0.22" 2024-01-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.22+9-LTS-219) 
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.22+9-LTS-219, mixed mode)
Warning: If you need to use a different version of the JRE for any reason, TIBCO strongly recommends that you contact TIBCO Support before doing so, to determine if the JRE you want to use is fully compatible with this version of iProcess Engine.

LDAP Directory Service

You can manage iProcess user, group, role, and attribute data via any LDAP compliant directory service.