TIBCO Configuration Tool (TCT)

In the TIBCO Configuration Tool (TCT), the Sizing Configuration page of the Create TIBCO ActiveMatrix BPM Server wizard enables you to set values for system sizing, depending on the type of system that you are tuning.

From the Environment list, select either Development or Production. This setting determines the values that are displayed in the other fields on this page. These values are suitable for either a typical development system or a typical production system, respectively.

You can set the following options:

Database Connection Pool Size
The maximum number of database connections available in each of the BPM DataSource resource templates. If the number of engine, client, or EMS driven threads exceed this value, they may have to wait for a database connection to become available (waiting for 30 seconds by default and throwing errors in the log if one wasn’t available after waiting). For more information, see Maximum Connections.
Database Statement Cache Size
The number of prepared statements that can be cached by each connection. Caching these statements improves performance but uses more memory. It is unlikely this value needs altering. For more information, see Prepared Statement Cache Size.
Number of Process Engine Threads
The number of PE background threads to be run in the BPM node JVM. This directly affects the throughput of instance starts, continuation and completion. It is likely that these threads will use the most CPU, and there is not much benefit in having more than 27 engine threads configured. For more information, see Process Engine (PVM).
Java Heap Size (Minimum/Maximum)
The heap is the main memory area used by the JVM. The heap is divided into generations; young holds short-lived objects that are created and immediately garbage collected, and objects that persist longer are moved to the old generation. Getting the maximum heap size configured correctly is important, and is dependent on various configurations of the system (for example, database connection and thread pool sizes, PE threads, and concurrent clients). This needs to be monitored through JConsole, JVisualVM or the TIBCO JVMInfo command line utility. For more information about the minimum heap size, see Java Heap Memory. For more information about the maximum heap size, see Changing the Value of -Xmx.

For more information about the fields on this page, see the section about the TIBCO ActiveMatrix BPM Server wizard in the ActiveMatrix BPM installation documentation.