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

Sieb_Proc_Memory_Detail graph view

Purpose
If the Siebel administrator suspects that a Siebel server is overloaded, an analysis of each operating system process that makes up the Siebel server should be performed.
Figure 6. Siebel Server Process Memory Utilization Snapshot
The Foglight SiebelServer Agent calculates CPU and memory utilization statistics for each operating system process that makes up the Siebel server. For Siebel 7 enterprises, this agent is able to correlate the siebmtsh executables that run multithreaded processes or MTServers with the corresponding Siebel component. There is one siebmtsh executable for each MTServer that is running.
Even though the Foglight SiebelServer Agent calculates CPU and memory utilization statistics for each operating system process, the agent uses the Number of Top Siebel operating system Process to Monitor, an agent property value, to determine the number of top processes to store in the Foglight repository for each collection. Foglight sorts by memory percentage when determining the top processes to store in the Foglight repository.
If the Siebel administrator identifies a Siebel server with high memory utilization or an individual Siebel server operating system process is consuming a large percentage of memory.
If a Siebel object manager component is found to be consuming a large amount of memory resources and the number of running tasks is high, the Siebel administrator should investigate whether the object manager’s Max Tasks, Max MTServers, and RecycleFactor parameters are correctly set. Siebel Support Web provides many resources detailing how to optimally set these parameters. Other options the Siebel administrator should consider are distributing the object manager across multiple Siebel servers. This is done by assigning the Siebel component to one or more Siebel servers and using Resonate to load balance between the Siebel servers.
 
Table 11. Sieb_Proc_Memory Detail graph information
Data Displayed
Resident Set Size. ResidentSetSize for the individual Siebel operating system processes, that is, the amount of Siebel process address space (in Kilobytes) currently in the main memory. Main memory includes RAM plus ROM but does not include cache.
 
Virtual Set Size. VirtualSetSize for the individual Siebel operating system processes, that is, the amount of virtual memory the process uses, Kilobytes.
Where to go next
n/a.

Sieb_Proc_Utilization graph view

Purpose
If the Siebel administrator suspects that a Siebel server is overloaded, an analysis of each operating system process that makes up the Siebel server should be performed.
Figure 7. Siebel Server Process Utilization Snapshot
The Foglight SiebelServer Agent calculates CPU and memory utilization statistics for each operating system process that makes up the Siebel server. For Siebel 7 enterprises, this agent is able to correlate the siebmtsh executables that run multithreaded processes or MTServers with the corresponding Siebel component. There is one siebmtsh executable for each MTServer that is running.
Even though the Foglight SiebelServer Agent calculates CPU and memory utilization statistics for each operating system process, the agent uses the Number of Top Siebel operating system Process to Monitor, an agent property, value to determine the number of top processes to store in the Foglight repository for each collection. Foglight sorts by memory percentage when determining the top processes to store in the Foglight repository.
If a Siebel object manager component is found to be consuming a large amount of memory resources and the number of running tasks is high, the Siebel administrator should investigate whether the object manager’s Max Tasks, Max MTServers, and RecycleFactor parameters are correctly set. The Siebel Support Web provides many resources detailing how to optimally set these parameters. Other options the Siebel administrator should consider are distributing the object manager across multiple Siebel servers. This is done by assigning the Siebel component to one or more Siebel servers and using Resonate to load balance between the Siebel servers.
If the Siebel component that is consuming a large amount of the CPU or memory resources is a batch or background component such as the Assignment Manager, the Siebel administrator should consider reassigning this component to a Siebel server with more available resources, by reassigning it with the Siebel Server Manager.
If the Siebel component is a member of the Siebel Remote component group, the Siebel administrator should investigate whether Siebel Remote can be tuned on this Siebel server or if one or more additional Siebel servers should be dedicated to the Siebel Remote component group.
 
 
Table 12. Sieb_Proc_Utilization Detail graph information
Data Displayed
CPU Time %. CPU consumption for the top operating system processes that make up the Siebel server.
 
Memory %. Memory consumption for the top operating system processes that make up the Siebel server.
Where to go next
Drill down to:
 
•
CPU % bar to isolate the CPU analysis to an individual Siebel server operating system process.
 
•
Memory % bar. For more information, see Sieb_Proc_Memory_Detail graph view. This display is used to analyze the memory consumption for an individual Siebel server operating system process.
To continue your investigation:
•
Drill down on the CPU % bar to isolate the CPU analysis to an individual Siebel server operating system process.

Sieb_Srvr_Availability_Overview graph view

Purpose
The Sieb_Srvr_Availability_Overview graph is used to view the availability percentage of:
•
Siebel server’s status.
•
Siebel server’s ability to connect to the Siebel database.
•
Siebel server’s ability to connect to the gateway server.
The availability of the Siebel eBusiness Application depends on the availability of each Siebel server in the environment. When a Siebel server is unavailable, every enabled Siebel component assigned to that Siebel server is also unavailable. Furthermore, if a Siebel component is only assigned to one Siebel server and that one Siebel server becomes unavailable, the work being performed by those components stops. For example, if the Assignment Manager is used to assign leads from the corporate web site to the appropriate account team, and the Siebel server that runs the Assignment Manager component is unavailable, the new web leads are not assigned to an account team.
Figure 8. Siebel Server Availability
The Foglight SiebelServer Agent collects availability statistics on the Siebel server, Siebel component groups, and Siebel components assigned to the Siebel server. These availability statistics not only allow the Siebel administrator to be alerted when an availability issue is encountered, but also generate views/reports on the overall availability of the Siebel eBusiness Application environment for management.
If the Siebel server is reported as having zero percent availability, the Siebel Server Manager should be used to restart the server. Other options include restarting the Siebel Server service on Windows® Siebel servers, or use start_server on UNIX®-based Siebel servers. Contact Siebel Support if restarting the server does not restore it to 100 percent availability.
It is important for the Siebel administrator to not only monitor the availability of the Siebel database, but to monitor the ability of the Siebel server to connect to the database. If the database is available, but the Siebel server is unable to log in, all the enabled Siebel components assigned to the server are not able to service user requests. To verify the Siebel server’s ability to connect to the database as the Siebel administrator, use a database utility on the Siebel server such as SQL*Plus or ISQL to connect to the database. Contact the Siebel database administrator for help with diagnosing any connectivity issues.
It is equally important for the Siebel server to have connectivity to the gateway server. The gateway server provides persistent backing of SiebelServer configuration information, including definitions and assignments of components, operational parameters, and connectivity information. If the gateway server becomes unavailable, new Siebel components cannot be started or added, and server administration functions become limited. However, all components and object managers currently running continue to do so. If the Siebel gateway server itself becomes unavailable, the Siebel administrator receives an alert that the gateway server is unavailable, but also an alert from the Siebel servers that connection to the gateway server is lost. In this case, the Siebel administrator should restart the Siebel gateway server. However, if the Siebel administrator only receives alerts that the Siebel server lost connectivity to the Siebel gateway server, this possibly indicates that the network connectivity is lost between the two hosts. The NetMonitor Agent can be used to monitor the network connectivity between all the monitored hosts that make up the Siebel ebusiness Application environment.
 
Table 13. Sieb_Srvr_Availability Overview graph information
Data Displayed
Siebel Server %. Siebel server availability is calculated as follows:
•
100 percent if the SiebelServerStatus = Running.
•
Zero percent for all other values.
 
Database Connection %. Server database connection availability is calculated as follows:
•
100 percent if the Siebel server is able to log in to the Siebel database as the Siebel administrator.
•
Zero percent for all other values.
 
Gateway Server %. Server gateway server connection availability is calculated as follows:
•
100 percent if the Siebel server is able to connect to the Siebel gateway server.
•
Zero percent for all other values.
Where to go next
Drill down on Siebel Server % bar. For more information, see Sieb_Comp_Group_Availability graph view. This displays the availability of the Siebel component groups for the Siebel server during the same time range.

Sieb_Srvr_Detail graph view

Purpose
When a Siebel task is completed, task level statistics gathered dynamically during the operation of the task roll up to the component level. Statistics for all enabled components assigned to a Siebel server are rolled up to the server level. Siebel stores server statistics as cumulative statistics, that is, since the Siebel server started. These statistics can be used to monitor the progress and performance of a Siebel server.
Figure 9. Siebel Server Overview Since Last Collection
The Foglight SiebelServer Agent calculates Siebel server statistic deltas by determining the change in the individual cumulative statistic since the last collection and stores the delta values in the Foglight repository. This allows the Siebel administrator to analyze how the Siebel server performs over time and identify peak usage time periods.
Use the Sieb_Srvr_Detail graph to correlate the Siebel server’s response time with its utilization and throughput for each refresh interval.
At what time period does the Siebel server’s response time become unacceptable? Is this a one-time occurrence or does it occur on a regular basis? Did the number of tasks started increase as response time started to decline? If the response time declines as the Siebel server’s throughput increases on a regular basis, the Siebel administrator should investigate if this is related to increased user activity during the time period in question. For example, increased throughput may occur between 8:00 AM and 9:00 AM due to users connecting to Siebel for the morning, or between 12:00 PM and 1:00 PM due to users reconnecting after lunch. Often these types of usage patterns cannot be avoided, but the Siebel administrator should ensure that the Siebel components’ load is balanced to compensate for increased activity during those peak periods.
It is useful to identify what time of day the Siebel server has the lowest throughput, because this is the optimal time to run batch components such as the Enterprise Integration Manager (EIM) or the Assignment Manager without an impact on the majority of users.
Description of the view
 
Table 14. Sieb_Srvr_Detail graph information
Data Displayed
Average ResponseTime (months). Average object manager response time since the last collection.
 
CPU Time (months). Total CPU time (seconds) for all the Siebel server’s tasks since the last collection.
 
SQL Execute Time (months). Total time (months) the Siebel server spent performing SQL execute operations since the last collection. For SELECT statements, the amount of time spent identifying the rows if the statement requires a sort or uses FOR UPDATE. For INSERT, UPDATE, and DELETE statements, the amount of time spent modifying the data.
 
Average Request Size (bytes). Average size (bytes) of reply messages since the last connection.
 
Average Reply Size (bytes). Average size (bytes) of request messages since the last collection.
 
Tasks Started (count). Number of Siebel tasks started since the last collection.
Where to go next
Drill down to:
 
•
SQL Execute Time line. For more information, see Sieb_Srvr_SQLTime graph view. This display is used to analyze the Siebel server SQL execute, parse and fetch time during the same time range as the Sieb_Srvr_Detail graph.
 
•
CPU Time or Tasks Started line. For more information, see Sieb_Comp_Detail graph view. This display is used to analyze the utilization and throughput for each enabled Siebel component during the same time range as the Sieb_Srvr_Detail graph view .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating