Starting the TIBCO iProcess Engine Processes

The Process Sentinels are responsible for starting all the TIBCO iProcess Engine processes. This can either be starting the complete system or starting individual processes as requested. The Process Sentinels make sure that the processes are started in the correct sequence.

Many processes require that dependent processes are already running, for example, the WQS must start before starting the WIS processes. The Process Sentinels make sure that all process dependencies are satisfied before starting a process.

All Process Sentinels (master and slaves) maintain a complete list of all processes running in the TIBCO iProcess Engine node cluster. Each server hosts its own Process Sentinels, which are only responsible for processes running on its computer. When the Process Sentinels attempt to start processes, they know if all the process dependencies are satisfied across all the TIBCO iProcess Engines in the node cluster. The Process Sentinels only attempt to start processes, if all the process dependencies are satisfied across all the TIBCO iProcess Engines in the node cluster.

For example, if a system is configured to have 1 WQS, 5 WIS, 5 WISMBD, the processes would be started in the following order:

•

Start the WQS processes

•

Start all the WIS processes

•

Start all the WISMBD processes.

The following diagram illustrates the order in which the Process Sentinels start the TIBCO iProcess Engine processes. All processes are started by the Process Sentinels apart from the RPC pool servers, which are started by the RPC TCP Listener process.