Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Additional System Requirements

Additional system requirements are described :

| • | TIBCO iProcess Objects

| • | Activity Publishing and Work Queue Delta Publication

| • | Java Runtime Environment (JRE)

| • | Korn Shell

| • | LDAP Directory Service

## 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 and/or iProcess Objects Director, see Enable iProcess Objects Server and Enable iProcess Objects Director for details.

## 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 System Administration Guide for configuring activity publishing and work queue delta publication once they are enabled.

If you plan to enable activity publishing (see Enable Activity Publishing) you must ensure that the computer hosting the iProcess Engine has access to the Java Message Service (JMS) provider that you want to use. This must be one of the JMS providers listed in JMS Providers.

JMS Providers

JMS provider | Minimum Supported Versions | Additional Requirements
TIBCO Enterprise Message Service (EMS) | 8.7.0 | If you are upgrading iProcess Engine and you are using EMS, you must ensure that your version of EMS is updated. See How Do I Upgrade TIBCO EMS for details.
IBM WebSphere | 8.5.5.11 | The IBM Client for JMS on J2SE with WebSphere Application Server must be installed on the machine hosting the iProcess Engine. See Installing the IBM Client for JMS on J2SE with IBM WebSphere Application Server for more information.
Oracle WebLogic Server | 14.1.x | 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 (`wlthint3client.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 JMS Provider.
JBOSS | 8.0 | Validated with `wildfly-client-all-26.0.0.Final.jar`. This client jar is needed in iProcess Engine to communicate with JBOSS server.
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 JMS Provider. The JMS provider must support Java 17 that is distributed with this version of iProcess Engine, and installed into the `SWDIR``\java directory`.

## Java Runtime Environment (JRE)

The following information is listed in JRE 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 allow you to configure the location of the JRE used by each component or product (if applicable).

JRE 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. Note: On some platforms, if you are installing iProcess Java Server Plug-in to use with this version of iProcess Engine, you cannot run the installer with Java 17. You must use an earlier version, such as Java 1.5. However, you can use Java 17 at runtime.
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.

TIBCO strongly recommends that you use one of the JREs listed in Distributed and Supported Java Virtual Machine (JVM) to provide the necessary Java functionality when using the components and products listed in the table above:

| 1. | The Distributed JVM version, which is distributed with this version of the iProcess Engine and installed into the `$SWDIR``/java` directory.

| 2. | The Supported JVM version, which TIBCO has validated for compatibility with this version of the iProcess Engine.

Distributed and Supported Java Virtual Machine (JVM)

Platform | Distributed JVM in $SWDIR/java | Supported JVM
Linux x86_64 | 17.0.12 | 17.0

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 the iProcess Engine.

## Korn Shell

Korn Shell (KSH) is a UNIX shell. Before installing TIBCO iProcess Engine on any supported UNIX platform, you must make sure that KSH has been installed.

Note | The public domain korn shell (pdksh) is not supported.

## LDAP Directory Service

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

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2025. Cloud Software Group, Inc. All Rights Reserved.