Configuration

Licensee

Specify a name to identify the installing iProcess Engine.

Note: The length of the name must be between 4 and 32 characters.

JMX Port Number

TIBCO iProcess Engine includes a Java Management Extensions (JMX) engine that enables TIBCO Business Studio to deploy procedures to the iProcess Engine.

Specify the port number on which the JMX engine should run.

The port number must be:

—an integer value between 0 and 65535.

—unique across all iProcess Engine installations on this computer.

If you do not specify a number, the default port 10025 will be used.

In Business Studio, a Deployment Server can use this port number to deploy processes to this iProcess Engine using the JMX Remote Method Invocation (RMI) interface. See TIBCO Business Studio Process Developer’s Guide for more information.

The port number will be written to the SWJMXConfig.port entry in the SWDIR\etc\swjmx.properties file, and can be changed after installation if needed. See TIBCO iProcess Engine Administrator’s Guide for more information.

Client-Server RPC Port Number

Specify the RPC service number that the TIBCO iProcess Workspace (Windows) clients use to communicate with this iProcess Engine:

- Select a new value from the drop-down list.

- Click the button to open the RPC Port Numbers dialog box. Enter the RPC port numbers in the Client-Server RPC Port Number field.

Note: You cannot change this value when upgrading an existing iProcess Engine.

391875 to 391879 are reserved for iProcess Engine client-server RPC program numbers. Using a number in this range should prevent any clash with other applications using the same number, provided that other applications also use legitimate RPC numbers.

The RPC service number must be unique across all iProcess Engine installations on this computer.

Process Sentinels Service Startup

Select the startup mode you want to use for the iProcess Process Sentinels service from the drop-down list:

Automatic - The iProcess Process Sentinels service starts automatically when the computer starts up.

Manual - You must manually start the Process Process Sentinels service either locating the service from Control Panel > Services or using the SWDIR\bin\swstart command.

Disabled - You cannot start the iProcess Process Sentinels service.

After the installation, you can change this setting by using the Services Console on Windows.

Auto-start Processes On Service Startup

Check this check box to automatically start the iProcess Engine processes after the iProcess Process Sentinels service has started and set the value of the iProcess Engine PM_AUTO_BOOT process attribute to 1 (enabled).

Uncheck this check box to disable automatic process startup and set the value of the iProcess Engine PM_AUTO_BOOT process attribute to 0 (disabled). You will need to manually start the iProcess Engine processes after the iProcess Process Sentinels service has started.

For an existing iProcess Engine, if the automatic process startup is currently enabled (PM_AUTO_BOOT=1), you cannot disable it during the upgrade. The check box is disabled.

See TIBCO iProcess Engine Administrator’s Guide for more information about the PM_AUTO_BOOT process attribute.

Note: You must check this check box if you are installing the iProcess Engine to a Microsoft Windows Cluster.

Enable Case Prediction

Check this check box to enable the case prediction server process (BGPREDICT) and set the value of the iProcess Engine ENABLE_CASE_PREDICTION process attribute to 1 (enabled).

Uncheck this check box to disable the case prediction server process (BGPREDICT) and set the value of the iProcess Engine ENABLE_CASE_PREDICTION process attribute to 0 (disabled).

For an existing iProcess Engine, if the case prediction server process is currently enabled (ENABLE_CASE_PREDICTION=1), you cannot disable it during the upgrade. The check box is disabled.

See TIBCO iProcess Engine Administrator’s Guide for more information about the iProcess Engine ENABLE_CASE_PREDICTION process attribute.

Note: The case prediction server process only affects background case prediction. It has no effect on live case prediction or case simulation.

For more information about the usage of case prediction, see the Using Case Prediction to Forecast Outstanding Work Items section in TIBCO iProcess Modeler Advanced Design.

Enable Case Data Normalization

Case data normalization is a feature used to make case data searching more efficient and therefore faster. It uses the field_value_N column in the case_data table in the iProcess Engine database. This column provides a normalized value of the value in the field_value column, allowing the database to do simple string comparisons, instead of having to do type conversions.

Check this check box to enable case data normalization and set the value of the iProcess Engine NORMALISE_CASE_DATA process attribute to 1 (enabled).

Uncheck this check box to disable case data normalization and set the value of the iProcess Engine NORMALISE_CASE_DATA process attribute to 0 (disabled).

For an existing iProcess Engine, if case data normalization is currently enabled (NORMALISE_CASE_DATA=1), you cannot disable it during the upgrade. The check box is disabled.

See TIBCO iProcess Engine Administrator’s Guide for more information about the NORMALISE_CASE_DATA process attribute.

Note: If you intend to use iProcess Objects to perform case data searches, TIBCO strongly recommends that you enable case data normalization. If you do not do this, you will be able to view and start procedures, but you will not be able to view the cases until you normalize the data.

You can enable or disable case data normalization after installation by using the Case Data Normalization Utility. See the Administering Case Data Normalization section in the TIBCO iProcess Engine Administrator's Guide for more information about this utility.

When upgrading an existing iProcess Engine, you should also note the following before choosing to enable case data normalization:

The installer populates the field_value_N column for every row in the case_data table by using the values from the field_value column. This can significantly impact the duration of the upgrade process if there are large numbers of cases on the system. See How Long Will an Upgrade Take for more information.