![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The Process Sentinels (SWDIR\etc\procmgr) are responsible for controlling all the TIBCO iProcess Engine processes. If a node cluster architecture is used, then the Process Sentinels will exist on each server to manage the processes running on that server. This process operates in different ways depending on whether you are using a third party transaction processing monitor.The Process Sentinels can also monitor processes to check that they are running and can automatically restart them if they fail. It can also detect if SWDIR\logs\sw_error and SWDIR\logs\sw_warn files have been created and sends a work item to the administrator to inform them that these files have been created.Refer to Process Management for more information about the Process Sentinels.
Refer to Foreground Processes for more information about what these processes do.
All of the foreground processes must operate on the master server. See Determining Where Processes Run for more information.
• in the UNIX Oracle and Windows Oracle versions, Oracle AQ. This is a transactional messaging system provided by the Oracle database.
• in the UNIX DB2 and Windows SQL Server versions, the iProcess Suite’s own transactional messaging system, which uses database tables provided by the DB2 or Microsoft® SQL Server database.
DBQD1
Refer to Background Processes for more information about what these processes do.
• 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 Events COM+ application, which is installed with the TIBCO iProcess Engine. All processes that want to subscribe to events register with the iProcess Events COM+ application.
If you are using a node cluster architecture, the iProcess Events COM+ application runs by default on the machine on which you installed the master server. If performance is or becomes an issue, TIBCO recommend 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.The name of the event server is stored in the Windows registry, so you will need to change this if you move the COM+ application to a new server. (See the TIBCO iProcess Engine Administrator’s Guide for more information.)
• UNIX DB2 version. Events are handled using iProcess event/notification daemons.
− tracks which processes have subscribed to which events. (It maintains this information both in memory and in the sw_subscription_list database table.)
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |