Schedule demo

Siebel Server Monitoring


Overview

Applications Manager lets you monitor the status of Siebel server components that are essential to keeping the application up and running. You can monitor as far down as the process level CPU and memory utilization of a Siebel task. Auto-discover your entire Siebel Enterprise; get out-of-the-box performance graphs showing Application Object Manager and Enterprise Application Integration Stats of processes within your enterprise.

Creating a new Siebel monitor

Using the REST API to add a new Siebel server monitor:Click here

Follow the steps given below to create a new Siebel Enterprise Server monitor in Applications Manager:

  1. Copy the APMSiebelCommands.txt file (located under <Applications Manager Home>/working/resource directory) and paste it under <Siebel Installation folder>/bin directory.
  2. Click on Add New Monitor under New Monitor in the Applications Manager web client.
  3. Click on Siebel Enterprise Server under ERP.
  4. Enter the Display Name of the monitor.
  5. Provide the Host Name or IP Address of the server where Siebel is installed.
  6. Select the Mode of Monitoring (SSH or WMI).
    • If SSH, provide the port number (default is 22), username and password information of the Siebel server. You have an option to configure Public Key Authentication (Username and Private Key). You can also give a Passphrase if the private key is protected with one. Also, you can specify the command prompt value, which is the last character in your command prompt. Default value is $ and possible values are >, #, etc.
    • If WMI, provide the username and password of the Siebel server.
  7. Enter the credential details like user name and password for authentication, or select the required credentials from the Credential Manager list by enabling the Select from Credential list option.
  8. Enter the Siebel Gateway Server and Enterprise Server names.
  9. Enter the Siebel administrator name (administrator or equivalent user) and Password.
  10. Enter the path to the Siebel Installation Directory.
  11. Specify the Timeout in minutes. Default value is 10 minutes.
  12. Specify the Discovery Interval in minutes for the automatic discovery and monitoring of child monitors.
  13. Enter the polling interval time in minutes.
  14. If you are adding a new monitor from the Central Server, select a Probe Server.
  15. Choose the Monitor Group from the combo box to which you want to associate the Monitor (optional). You can choose multiple groups to associate your monitor.
  16. Click Add Monitor(s). Upon adding the Siebel Server monitor, you can view the details of the newly added Siebel Server monitor.

Monitored Parameters

Go to the Monitors Category View by clicking the Monitors tab. Click on Siebel server under the ERP Table. Displayed is the Siebel Server bulk configuration view distributed into three tabs:

  • Availability tab, gives the Availability history for the past 24 hours or 30 days.
  • Performance tab gives the Health Status and events for the past 24 hours or 30 days.
  • List view enables you to perform bulk admin configurations.

Click on the monitor name to see all the server details listed under the following tabs:

Monitor Information

ParametersDescription
NameName of the Siebel server monitor
Last Polled at Specifies the time at which the last poll was performed.
Next Poll at Specifies the time at which the next poll will be performed.
Associated Groups Denotes the monitor groups associated with the Siebel server monitor.

Performance

ParametersDescription
Availability history for last 6 hoursName of the Siebel server monitor
Performance history for last 6 hoursSpecifies the time at which the last poll was performed.
CPU UtilizationDisplays the current CPU utilization of the server.
Memory UtilizationDisplays the current memory utilization of the server.
Statistic NameSiebel application statistic name.
Statistic ValueSiebel application statistic value.
DescriptionDescription of the statistic.
Transactions from PIM in ProgressNumber of inprocess transactions from PIM
Global Data Cursor Cache MissesNumber of global data cursor cache misses
Tests SuccessfulNumber of tests that were successful
Global Data Cursor Cache ObjectsNumber of objects currently in the global data cursor cache
Transactions form Siebel in ProgressNumber of inprocess transactions from Siebel
Maximum OOB Component TimeMaximum OOB Component Time
Global Data Cursor Cache CPUTotal CPU time spent on creating global data cursor objects in cache (in seconds)
Failed Transactions from SiebelNumber of failed transactions from Siebel
Global Data Cursor Cache MemoryTotal memory spent on creating global data cursor objects in cache (in bytes)
Global Data Cursor Cache HitsNumber of global data cursor cache hits
Events ProcessedTotal number of events processed
Data Cursor Cache ObjectsNumber of objects currently in the data cursor cache
Failed Transactions from PIMNumber of failed transactions from the PIM
Events Processed RateRate of Processing the events
Data Cursor Cache MemoryTotal memory spent on creating data cursor objects in cache (in bytes)
Number of Component CrashesThe number of times a process of the component has crashed.
Data Cursor Cache MissesNumber of SQL data cursor cache misses
Number of Component RestartsThe number of times a process of the component has restarted.
Number of ErrorsTotal number of level 0 and 1 errors.
Number of object rows assignedThis statistics represents the cumulative number of records assigned by this component since the server was started
PSP Cache Hit TotalTotal PSP Cache Hit Number
PSP Cache Miss TotalTotal PSP Cache Miss Number
SQL Object Cache MemoryTotal memory spent on creating SQL object objects in cache (in bytes)
Data Cursor Cache CPUTotal CPU time spent on creating data cursor objects in cache (in seconds)
Completed Transactions from SiebelNumber of completed transactions from Siebel
Completed Transactions from PIMNumber of completed transactions from the PIM Server
Average OOB Queue SizeAverage OOB Queue Size
SearchEvents Processed RateRate of Processing the records during indexing
Average OOB Component TimeAverage OOB Component Time
SearchEvents ProcessedTotal number of records processed during indexing
Tests FailedNumber of tests that failed
Tests AttemptedNumber of tests that were started
Data Cursor Cache HitsNumber of SQL data cursor cache hits

Components

ParametersDescription
ComponentSpecifies the name of the Siebel component.
Component GroupSpecifies the name assigned to the Siebel component group.
RunStateSpecifies the value returned for the state of the component. An example value of RunState is offline
ActiveMTSProcessThe number of running multi-threaded shell (MTS) processes.
RunningTasksThe current number of running tasks for the component.

AOM Statistics

Application Object Manager Statistics

ParametersDescription
Average Connect TimeThe time required to perform all the activities required to establish an interactive session (such as authentication, initialization, and allocating the necessary resources) with Object Manager.
Average Response TimeThe average (mean) time required to respond to an end-user action. If application performance is deteriorating, the metric value increases.
Statistic NameSiebel application statistic name.
Statistic ValueSiebel application statistic value.
DescriptionDescription of the statistic.
Average Request SizeThe average size of request messages (in bytes)
Average Reply SizeThe average size of reply messages (in bytes)
Average Requests Per SessionThe average number of requests per Object Manager session
Total Think TimeThe total end-user think time (in seconds)
Average Think TimeThe average end-user think time between requests (in seconds)
Object Manager ErrorsThe number of errors encountered during Object Manager session
Reply MessagesThe number of reply messages sent by the server
Request MessagesThe number of request message received by the server
Total Database Response TimeThe total Database Response/Processing Time (milliseconds)
Total Reply SizeThe total size (in bytes) of reply messages
Total Request SizeThe total size (in bytes) of request messages
Total Response TimeThe total Object Manager response time (msec)

Database Statistics

ParametersDescription
Average Execution TimeThe average (mean) amount of time the database requires to process the SQL statement after the statement is parsed.
Average Fetch TimeThe average (mean) amount of time the database requires to fetch records by an SQL statement after the statement is parsed.
Statistic NameSiebel application statistic name.
Statistic ValueSiebel application statistic value.
DescriptionDescription of the statistic.
SQL Cursor Cache MissesThe number of SQL cursor cache misses
SQL Cursor Total CpuThe total CPU time spent on creating SQL cursor objects in cache (in seconds)
SQL Parse TimeThe total elapsed time for SQL parse operations (in seconds)
Number of SQL FetchesThe total number of SQL fetch operations
SQL Object Cache ObjectsThe number of objects currently in the SQL object cache
Number of SQL ExecutesThe total number of SQL execute operations
SQL Object Cache MissesThe number of SQL object cache misses
SQL Cursor Cache HitsThe number of SQL cursor cache hits
Number of SQL ParsesThe total number of SQL parse operations
SQL Object Cache HitsThe number of SQL object cache hits
SQL Object Cache CPUThe total CPU time spent on creating SQL object objects in cache (in seconds)
SQL Fetch TimeThe total elapsed time for SQL fetch operations (in seconds)
Avg SQL Parse TimeThe average time for SQL parse operations (in seconds)
SQL Execute TimeThe total elapsed time for SQL execute operations (in seconds)

InfraStructure

ParametersDescription
Statistic NameSiebel application statistic name.
Statistic ValueSiebel application statistic value.
DescriptionDescription of the statistic.
Tasks Exceeding Configured CapacityThe number of tasks stated that exceeded configured capacity
CPU TimeThe total CPU time for component tasks (in seconds)
Num of DLRbk RetriesThe number of Retries due to Deadlock Rollbacks
Num of Exhausted RetriesThe number of Times All Retries are Exhausted
Elapsed TimeThe total running time elapsed for component tasks (in seconds)
Number of SleepsThe total number of sleeps for component tasks
FDR Avg time between agingAvg Seconds per buffer wrap
Sleep TimeThe total amount of sleep time for component tasks (in seconds)
FDR Buffer Life in secondsSeconds since buffer was created
Num of DBConn RetriesThe number of retries due to DB Connection Loss
Minimum Peak Memory UsagePeak Mem used by task. Rolls up differently than MaxPeakMemory
Maximum Peak Memory UsageThe Peak Memory used by task. Rolls up differently from MinPeakMemory
Total TasksThe total number of tasks completed for server components
FDR Buffer WrapsThe number of buffer wraps

EAI Statistics

ParametersDescription
Statistic NameSiebel application statistic name.
Statistic ValueSiebel application statistic value.
DescriptionDescription of the statistic.
EAI Receiver Total Messages ProcessedThe total number of messages processed by the Enterprise Application Integration receiver.
Siebel Adapter Total Query CallsThe total cumulative size of output property sets (in KB) for all queries
Siebel Adapter Total Sync/Upsert CallsThe total number of non-query (synchronize, upsert, update or insert) calls made to Siebel Adapter
Total XML Converter Size of Input BufferThe total cumulative size of input buffer (in KB)
Siebel Adapter Total Query SizeThe total cumulative size of output property sets (in KB) for all queries
Siebel Adapter Total Sync SizeThe total cumulative size of input property sets (in KB) for all non-query calls (synchronize, upsert, update or insert)
Total XML Parser CallsThe total number of XML parser calls
Total XML Converter Size of Output BufferThe total cumulative size of output buffer (in KB)
Total XML Generator CallsThe total number of XML generator calls

Tasks

ParametersDescription
Tasks RunningThe current number of concurrent task instances running in the Siebel component.
Tasks PausedThe tasks that have been temporarily placed in a suspended state.
Tasks CompletedThe tasks that have run to completion.
Tasks Exited with ErrorsThe tasks that encountered an error during its processing and exited.
Tasks KilledThe tasks that were not able to shut down cleanly, and were forced to shut down.
Error Tasks
ComponentName of the Siebel component.
TaskIDThe operating system identification number assigned to the task.
Run StateCurrent run state for the Siebel task (Running, Paused, Stopping,
Task StatusA task may be in one of four states
  • Running
  • Paused
  • Stopping
  • Completed
Task LabelThe task label.
Start TimeThe time when this task started.
End TimeThe time when this task ended.

Active Sessions

ParametersDescription
ComponentSpecifies the name of the Siebel component.
TaskIDSiebel task ID for the application OM that handles the user session.
Run StateThe running state of the users' sessions for the selected Siebel Server.
Hung StateThe state of the users' sessions for the selected Siebel Server not responding.
DB Session IDA unique session number created for the user
OM LoginObject Manager login ID of the user.
Task StatusCurrent status of the task i.e running or paused.

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by over 6000+ businesses globally