Event Handling

The TIBCO 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.

The event handling mechanism used depends on the TIBCO iProcess Engine variant used:

•

UNIX Oracle version. Events are handled using Oracle AQ’s publish/subscribe interface.

•

Windows Oracle and Windows SQL Server versions. Events are handled using the iProcess Events64 COM+ application, which is installed with the TIBCO iProcess Engine. All processes that want to subscribe to events register with the iProcess Events64 COM+ application.

Note:

If you are using a node cluster architecture, the iProcess Events64 COM+ application runs by default on the machine on which you installed the master server. In case of issues related to performance, TIBCO recommends that you dedicate a separate server, which is not running any TIBCO iProcess Engine processes, as the event server. This will reduce the load on the master server.

Since the name of the event server is stored in the Windows registry, you must change this before moving the COM+ application to a new server. For more information, see the TIBCO iProcess Engine Administrator’s Guide.

•

UNIX DB2 version. Events are handled using iProcess event/notification daemons.

process that carries out the following functions:

—

tracks which processes have subscribed to which events. (It maintains this information both in memory and in the sw_subscription_list database table.)

—

receives events when they are published.

—

forwards notification of an event to the notification daemon in each subscribed process.

A notification daemon is a thread created by any TIBCO iProcess Engine process that wishes to receive event notifications.

Did you find this helpful?

Yes No