Foglight for Siebel 5.2.1 - User and Reference Guide

The Sieb_Comp_MTServers alert is generated when the number of running MTServers does not at least equal the number of minimum MTServers that is defined for the Siebel component. The severity of the alert increases as the difference between the number of running MTServers and minimum MTServers increases. This alert does not fire for the Siebel components with a run state of Shutdown or Offline. It is normal for Siebel components that are shut down or offline to have zero minimum MTServers running. See the Siebel support documentation for more information on setting the minimum MTServer parameter.

The Transaction Merger Siebel component is vital to successful Siebel Remote operation because it scans the master transaction log on the Siebel database server and prepares transactions for visibility checking and routing by a Transaction Router. The Sieb_Comp_Proc_Avail:CRITICAL alert indicates that there are no Transaction Processor tasks currently running, that is, no transactions are being checked for visibility and prepared for routing by a Transaction Router. If the Siebel administrator has not intentionally stopped the Transaction Merger, the Siebel administrator should start a Transaction Processor task with the Siebel Server Manager.

The Transaction Router Siebel component is vital to successful Siebel Remote operation because it does visibility checking and routing of transactions from the .dx files created in the txnproc directory by the Transaction Processor.

The Sieb_Comp_Route_Avail:CRITICAL alert indicates that there are no Transaction Router tasks currently running, that is, no transactions are being routed from the .dx files to the Siebel Remote users’ outboxes. If the Siebel administrator does not intentionally stop the Transaction Router, one or more Transaction Router tasks should be started with the Siebel Server Manager.

The Transaction Router Siebel component is a vital entity to the success of Siebel Remote operation because it does visibility checking and routing of transactions from the .dx files created in the txnproc directory by the Transaction Processor. There must be at least one Transaction Router running on each Siebel server running the Siebel Remote component group. For better performance, multiple Transaction Routers can run on the same Siebel server. It is common for the Siebel administrator to set the maximum number of Transaction Routers to equal the desired number of running Transaction Routers. If the desired number of Transaction Routers is not running, a large backlog occurs increasing the latency time between the time an update is made to the Siebel database, to the time the update is successfully routed to the appropriate mobile users’ outboxes.

The Sieb_Comp_Route_Task alert is received when the number of running Transaction Routers does not equal the maximum defined. The severity of the alert increases as the difference between the number of running Transaction Routers and the maximum number of Transaction Routers increases. When this alert is received, the Siebel administrator should use the Siebel Server Manager to start additional Transaction Routers.