Chat now with support
Chat with Support

Foglight for Siebel 5.2.1 - User and Reference Guide

Introducing Foglight for Siebel Systems Foglight for Siebel Systems Summary Dashboard About the Foglight SiebelServer Agent Foglight for Siebel Systems Reference

SiebelServer Agent rules

Foglight for Siebel Systems includes some built-in rules that monitor the health of your Siebel eBusiness applications environment. In this guide, the rules are organized in alphabetical order by agent.
This section contains the rules for the SiebelServer Agent:
•
Sieb_Comp_AOMErrors rule
•
Sieb_Comp_Inter_Task rule
•
Sieb_Comp_Merge_Avail rule
•
Sieb_Comp_MTServers rule
•
Sieb_Comp_Proc_Avail rule
•
Sieb_Comp_Route_Avail rule
•
Sieb_Comp_Route_Task rule
•
Sieb_Comp_State rule
•
Sieb_Crash_Log rule
•
Sieb_DB_Connect_Avail rule
•
Sieb_GW_Connect_Avail rule
•
Sieb_Log_Msg rule
•
Sieb_Srvr_Avail rule
•
Sieb_Srvr_CPU_Util rule
•
Sieb_Srvr_Memory_Util rule
•
Sieb_Srvr_NoDBConnRetry rule
•
Sieb_Srvr_NoDLRbkRetry rule
•
Sieb_Srvr_NoXhaustRetry rule
•
Sieb_Srvr_Proc_CPUTime rule
•
Sieb_Srvr_Proc_Memory rule
•
Sieb_Task_Status rule

Sieb_Comp_AOMErrors rule

Purpose
The Sieb_Comp_AOMErrors (Application Object Manager) rule determines if a Siebel Object Manager encountered errors.
Scope
SiebelServer_SiebelComponentStatistics
Rule definition
Table 19. Sieb_Comp_AOMErrors Rule definition
Condition
State
Action
#AOMErrors# != 0
Warning
Log message
Interpreting the rule
The Sieb_Comp_AOMErrors:WARNING alert is generated when the SiebelServer Agent detects that an object manager encountered an error. When the Siebel administrator receives this alert, they should check the corresponding task log to determine the cause of the error.
The SiebelServer Agent can monitor each Siebel component task for errors, thus enabling the Siebel administrator to also be alerted of the exact error that occurred. Use the Component Logs Message Trap List agent property to enable this functionality for each Siebel component.

Sieb_Comp_Inter_Task rule

Purpose
The Sieb_Comp_Inter_Task (interactive task) rule determines when the number of running tasks is nearing the maximum number of tasks allowed for interactive Siebel components.
Scope
SiebelServer_SiebelComponents
Rule definition
Table 20. Sieb_Comp_Inter_Task rule definition
Condition
State
Action
#ComponentRunMode# == "Interactive" && (#RunningTasks# >= (f4registry("InterTaskPercentWarning") * #MaxTasks#))
Warning
Log message
#ComponentRunMode# == "Interactive" && (#RunningTasks# >= (f4registry("InterTaskPercentCritical") * #MaxTasks#))
Critical
Log message, email Siebel administrator
Interpreting the rule
Each Siebel component has a maximum task parameter that represents the number of tasks/users that can run concurrently. When the component’s number of running tasks hits the maximum, no additional tasks can instantiate until at least one currently running task completes. Since interactive tasks are either object managers that service the Siebel web client or synchronization manager tasks that service remote users, the inability for new tasks to be instantiated results in a denial of service for Siebel users.
The Sieb_Comp_Inter_Task rule alerts the Siebel administrator when the number of running tasks nears the maximum tasks defined for a Siebel component. When this alert is received, the Siebel administrator can increase the maximum task parameter or assign the Siebel component to an additional Siebel server to increase the number of tasks the Siebel component can accommodate across the Siebel enterprise. See the Siebel support documentation for more information on setting the maximum task parameter.
* 
NOTE: InterTaskPercentWarning is a Foglight_Registry entry with a default value of 0.70 and InterTaskPercentCritical has a default value of 0.90. Use the Foglight Registry to change thresholds for rules by modifying registry entries.
Views that render data that this rule is based on:
•
Sieb_Comp_Tasks graph view .

Sieb_Comp_Merge_Avail rule

Purpose
The Sieb_Comp_Merge_Avail (merger availability) rule determines when the Transaction Merger, which is critical to the successful operation of Siebel Remote or Siebel Replication, is not currently running.
Scope
SiebelServer_SiebelComponents
Rule definition
Table 21. Sieb_Comp_Merge_Avail rule definition
Condition
State
Action
scope.get("ComponentAlias") == "TxnMerge" && #ComponentState# != "Running"
Critical
Log message, email Siebel administrator
Interpreting the rule
The Transaction Merger Siebel component is vital to successful Siebel Remote operation because it applies transactions to the Siebel database server that are uploaded into the appropriate Application server inbox by a Siebel Remote mobile user. The application of these transactions to the Siebel database takes place after the synchronization session finishes and the mobile client disconnects.
The Sieb_Comp_Merger_Avail:CRITICAL alert indicates that there are no Transaction Merger tasks currently running, i.e., no transactions are being applied to the Siebel database. If the Siebel administrator has not intentionally stopped the Transaction Merger, the Siebel administrator should start one or more Transaction Merger tasks with the Siebel Server Manager.
Views that render data that this rule is based on:
•
Sieb_Comp_Availability graph view .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating