Configuring iProcess Engine Events Server

Note: This section is only relevant if you are running iProcess Engine on a Windows platform.

The iProcess Engine uses a publish/subscribe event mechanism to handle the following inter-process tasks:

• Notifying processes to update caches.
• Synchronization of process startup and shutdown.

Events are handled by the iProcess Events COM+ application. All processes that want to subscribe to events register with the COM+ application.

The iProcess Events COM+ application is installed on the same machine as iProcess Engine. If you are using a node cluster architecture, the event server is set to be the machine on which you installed the master server. The event server name is stored in the following registry key:

RegistryLocation\Staffware plc\Staffware Server\Nodes\nodename\
IEL_EVENT_SERVER

where:

• RegistryLocation is \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.
• nodename is the name of iProcess Engine installation.

If performance becomes an issue, TIBCO recommends that you dedicate one machine in the cluster, which is not running any iProcess Engine processes, to host the iProcess events. This reduces the load on the machine. To do this, you will need to edit the registry entry and change the nodename to the name of the new iProcess events server. You will need to restart the machine after doing this.

Warning: Incorrectly editing the registry can severely damage your system. Ensure that you edit ONLY the indicated registry entry.

Ensure that the iProcess Events application starts successfully on the new iProcess events server before starting iProcess Engine, otherwise the system might not function correctly.