Installing the iProcess Engine on a Node Cluster
Installing the TIBCO iProcess Engine on multiple servers that all use the same database instance is known as a node cluster architecture. You can convert from a single-server to a node cluster at any time simply by adding another server to the installation. In the node cluster architecture, you can have a number of TIBCO iProcess Engine processes running on different servers, but they work as a single iProcess Engine. Node clusters improve load balancing and performance. However, all the TIBCO iProcess Engine case data such as fields and their values in forms will be stored in one TIBCO iProcess Engine database instance.
The following diagram illustrates a TIBCO iProcess Engine (node cluster) that uses two servers to run TIBCO iProcess Engine processes. They can all access iProcess case data from the same TIBCO iProcess Engine database instance.
Note that:
|
•
|
A complete installation of the iProcess Engine needs to be performed on each machine in the node cluster. |
|
•
|
All the iProcess Engines point to a single database instance. Within the database there is a single engine configuration that specifies which executables are configured to run on each server. |
|
•
|
The iProcess sentinels are configured to run on each machine. One server in the cluster is designated as the master server and the iProcess Sentinels on this server co-ordinate the startup, shutdown and management of the processes on all machines in the cluster. |
|
•
|
The iProcess Sentinels on the slave servers manage the executables designated to run on that machine. |