iProcess Engine Installation Software Release 11.0.

1 AIX(IBM RS/6000) Platform

Pre-Requisites On

System Requirements:
To be able to install and run this version (Software Release 11.0.1) of the iProcess Engine, the system must meet the following requirements: Basic System Requirements Additional System Requirements Oracle Database Requirements Basic System Requirements The Disk space columntables indicates the amount of disk space neededfor the iProcess Engine distribution set when it is extracted to the temporary installationdirectory. IBM RS/6000 Operating System One of the following: AIX 5L Version 5.2 AIX 5L Version 5.3, Technology Level5300-04 or later Note: Both 32-bit and 64-bit versions of AIX5L are supported For: Oracle10g - 635 MB Disk space

Note: If we are using AIX 5L Version 5.3,we must apply the fix for APAR IY84470. Note:If we are running Oracle 10g against AIX 5L Version 5.2, then AIX 5L Version 5.2 mustbe Maintenance Level 1 or higher. Additional System Requirements TIBCOiProcess Objects Server If we intend to enable the iProcess Objects Server, we will need to takeaccount of the following additional runtime disk space requirements. Hardware Platform Runtime Disk Space

IBM RS/6000 20 MB + Log The iProcess Objects Server log file defaults to a maximum size of 15 MB. This can be configured after installation.

iProcess Engine Installation Software Release 11.0.1 AIX(IBM RS/6000) Platform TIBCOiProcess Objects Director

Pre-Requisites On

If we intend to enable the iProcess Objects Director, we will need totake account of the following additional disk space and memory requirements. Platform Disk Space Memory

IBM RS/6000 500 KB + Log 20 MB The iProcess Objects Director log file defaults to a maximum size of 15 MB. This can be configured after installation using the LOG_FILE_MAX_SIZE process attribute. (See the TIBCO iProcess Objects Director Administrator s Guide for more information.) iProcessServer Manager The iProcess Server Manager is a JSP web client application that you can use to start, stop,restart and pause iProcess Engine server processes. It utilizes TIBCO Hawk to provide agraphical view of the iProcess Engine server processes on a machine or a node cluster. If we are planning to use the iProcess Server Manager we must have: y TIBCO Hawk Version 4.8.1 installed on the machine where we intend to install theiProcess Engine. y TIBCO Rendezvous Version 8.1.1 installed on the machine where we intend to install the iProcess Engine. (This is the minimum version required to run TIBCOHawk Version 4.8.1.) y TIBCO Hawk Version 4.8.1 installed on the machines on which you want toadminister iProcess Engine processes.

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 processpublishes monitored activities to the IAPJMS process.) This enables real-time monitoringof auditable objects so that mission critical or important business events can be easilymonitored. Enabling activity publishing also enables Work Queue Delta Publication. This allows anexternal application to monitor a work queue and to retrieve only those work items in agiven work queue that have changed. See theiProcess Engine System Administration guide for configuring activity publishing andwork queue delta publication once they are enabled. If we plan to enable activity publishing, we must ensure that the computer hosting theiProcess Engine has access to the Java Message Service (JMS) provider that we want touse.

iProcess Engine Installation Software Release 11.0.1 AIX(IBM RS/6000) Platform

Pre-Requisites On

The below table shows the JMS Provider which is to be used: JMS Provider Minimum Supported Versions 4.4.3
4.0.0

Additional Requirements

TIBCO Enterprise Message Service (EMS) JBoss JBoss Messaging Other

None None SP2

1.0.1

Note that: y 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. y The JMS provider must support one of the following Java Virtual Machines (JVM): Platform Operating System Distributed JVM (in $SWDIR/java) 5.0.0.76 Supported JVM 5.0.0.76

IBM RS/6000

AIX 5L Version 5.2 or5.3

Java Runtime Environment (JRE) Component/Product IAPJMS process Default JRE Location $SWDIR/java Configuration Tool SWLIB_PATH process attribute value See "Administering Process Attributes" in the TIBCO iProcess Engine Administrator s Guidefor more information. none none none none TIBCO iProcess Technology Plug-ins installer See TIBCO iProcess Technology Plug-ins Installation for more information. TIBCO iProcess Technology

iProcess Server Manager JMX engine TIBCO EMS TIBCO Hawk TIBCO iProcessBusinessWorks Connector Server Plug-in

$SWDIR/java $SWDIR/java $SWDIR/java $SWDIR/java Selectable when we install the plug-in

TIBCO iProcess Java

Selectable when we install the

iProcess Engine Installation Software Release 11.0.1 AIX(IBM RS/6000) Platform Server Plug-in plug-in

Pre-Requisites On Plug-ins installer See TIBCO iProcess Technology Plug-ins Installation for more information. Note:On some platforms, if we are installingiProcess Java Server Plug-in to use with thisversion of iProcess Engine, we cannot run theinstaller with Java 1.6; you must use an earlierversion such as Java 1.5. However, we canuse Java 1.6 at run-time. TIBCO iProcess Engine Web Services Plug-in installer See TIBCO iProcess Engine Web Services Plug-in Installation for more information.

TIBCO iProcess Engine Web Services Server Plug-in

Selectable when you install the plug-in

TIBCO strongly recommend that we use one of the JREs listed in the following table to provide the necessary Java functionality when using thecomponents and products. Platform Operating System Distributed JVM (in $SWDIR/java) 5.0.0.76 Supported JVM 5.0.0.76

IBM RS/6000

AIX 5L Version 5.2 or5.3

Oracle Database Requirements This version (11.0.1) of the iProcess Engine requires either Oracle9i Release 2 or Oracle Database10g Release 2. Notes: y We will need access to an Oracle Metalink account to be able to access the required patches and patch sets. y The iProcess Engine uses Oracle Call Interface (OCI) to access data in the Oracle database. For reasons of stability, the iProcess Engine is statically linked with the Oracle client libraries that provide the required OCI routines. Oracle state that they only support products that run against the same set of libraries they were built with. This means we must use particular Oracle Client versions, depending on the method you use to connect to the database.

iProcess Engine Installation Software Release 11.0.1 AIX(IBM RS/6000) Platform y

Pre-Requisites On

If we are using Oracle Real Application Clusters (RAC), TIBCO recommend that we install the iProcess Engine on a machine that is not part of the RAC, and use aTNS connection to connect to the remote database. If we are using Oracle 10.2.0.2, note that by default Oracle files and directories are created with more restricted permissions compared to previous versions. If these default permissions are used, the iProcess Engine does not have the necessary permissions to access the libraries that it needs in the $ORACLE_HOMEdirectory, and so will fail to start. To ensure that this problem does not occur, modify the defaultpermissions on the 10.2.0.2 Oracle database server (for a direct connection) or client(for a TNS connection) home, by running a changePerm.sh script. If you run swinstall as the root user, swinstall may be able to run this script. For more information about this issue, and how to use the changePerm.sh script,please see the following Oracle references: Oracle Database Patch Set Notes, 10g Release 2 (10.2.0.2) for your hardwareplatform. OracleMetalink document 356850.1. The exact Oracle version requirements depend on the type of database connection youintend to use: 1. Adirect connection to the default database hosted on the computer where you willinstall or upgrade the iProcess Engine. 2. A Transparent Network Substrate (TNS) connection, either to: The default database hosted on the computer where you will install or upgrade the iProcess Engine, or A remote database - meaning a database that is either hosted on a remote computer,or a non-default database on the computer where you will install or upgrade the iProcess Engine.

Direct Connection Requirements for Oracle When using a direct connection, you must set the ORACLE_HOME environment variableto the pathname of the Oracle Database. The following table shows the required Oracle database versions when you use a directconnection to the default database. Platform Solaris, HP-UX on HP-9000, AIX, Linux Required Release Level 9.2.0.8 or 10.2.0.2 Required Patch(es) None

TNS Connection Requirements for Oracle When using a TNS connection, we must: y Set the ORACLE_HOME environment variable to the pathname of the Oracle Client. y Use Oracle s Transparent Network Substrate (TNS) to connect the iProcess Engine to the Oracle Database.

iProcess Engine Installation Software Release 11.0.1 AIX(IBM RS/6000) Platform y y

Pre-Requisites On

Ensure that the correct Oracle Client release is installed on the computer where we will install or upgrade the iProcess Engine, as described in the following table. Ensure that the remote Oracle database uses one of the Oracle Database releasesspecified in the following table.

The following table shows the required Oracle database and client versions: Oracle Platform Certified Database Release Level... 9.2.0.x where x is 8 or higher 10.2.0.x where x is 2 or higher 10.2.0.x where x is 2 or higher ...with Required Client Release Level 9.2.0.8 9.2.0.8 or 10.2.0.2 9.2.0.8 or 10.2.0.2

Solaris, HP-UX on HP-9000, AIX, Windows, Linux

If we are using an Oracle Database version that is: y Earlier than the releases explicitly mentioned in the table above, we must upgrade toone of the specified releases. y Later than the releases explicitly mentioned in the table above, please contact TIBCO Support to confirm whether or not that release is supported by our iProcess Engineversion.