Application Monitoring for Oracle Siebel CRM (Configure)

ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM JS

Availability2014.1 or later

Recommended implementation order

Synthetic checks come first

Add the Siebel Application Server

Configure Gateway monitoring

Track siebns.dat changes

Troubleshooting

Fix missing Siebel data

Configure GermainUX’s Application Monitoring for Oracle Siebel CRM

Configure Application Monitoring for Oracle Siebel CRM

This guide explains how to configure essential health and performance monitoring for the Siebel Enterprise, Gateway, Application Servers, Object Managers, logs, crash files, tasks, processes, HTTP, and SISNAPI services.

GermainUX includes preconfigured Siebel parsers, monitors, metrics, KPIs, and dashboards based on more than 20 years of Siebel monitoring experience. These configurations can be adjusted to match each Siebel version, architecture, component model, and operational requirement.

Recommended implementation order

Configure Siebel monitoring in this order:

	Action
1	Create a synthetic scenario for a critical workflow.
2	Import or verify the Siebel component types.
3	Add the Siebel servers.
4	Add the monitoring credentials.
5	Configure task- and process-level monitoring.
6	Configure Object Manager and Server Manager parsers.
7	Configure log, crash, and Gateway directory monitors.
8	Configure remote Siebel component monitoring.
9	Configure the Siebel Config Collator.
10	Configure HTTP and SISNAPI availability monitoring.
11	Exclude components that should not be monitored.
12	Validate the preconfigured KPIs and dashboards.
13	Configure SLAs and alerts.

Synthetic monitoring should be implemented early because it provides immediate confirmation that users can access and complete critical Siebel workflows. Server-side monitoring can then identify the component responsible when a synthetic test fails.

Prerequisites

Before configuring Siebel application monitoring, confirm that:

A GermainUX Engine is deployed and online.
The Engine can reach the Siebel servers.
The Engine can access the Siebel Gateway.
The Engine can execute the required Server Manager commands.
The Engine service account can read the configured logs and diagnostic files.
The Siebel Enterprise, Gateway, servers, and components are known.

Show all 11

Appropriate monitoring credentials are available.
Server paths are accessible from the Engine.
Required WMI or SSH connectivity is available.
Firewalls, proxies, DNS, and certificates have been configured.
The monitoring thresholds have been reviewed with the Siebel operations team.

See Engine Deployment for Oracle Siebel CRM.

Open the Siebel wizards

In GermainUX, go to: Workspace -> Left Menu → Settings > Wizards -> <search for Siebel or whichever keyword related to what you need>

The available wizards can include:

Siebel App Server
Siebel Gateway Server
Siebel OpenUI
Siebel Web Server
Parser
Directory Monitor

Use the wizard corresponding to the layer being configured.

Verify the Siebel component types

A new deployment requires the preconfigured Siebel seed data. Current GermainUX deployments normally include this configuration. For an older or manually installed deployment, import the JSON files found under:

Server Distribution/configuration/siebel

Import them through the REST client in the GermainUX Configuration Console and select Merge so existing customizations are preserved. Verify that these component types exist under:

germain.apm.monitoringConfig.components

Required component types include:

Siebel Object Manager Parser
Siebel Enterprise Manager Parser
Siebel Crash Parser
Siebel 7.x FDR Parser
Siebel 8.x FDR Parser
Siebel Crash Directory Monitor

Show all 12

Siebel Log Directory Monitor
Siebel Component Monitor (WMI)
Siebel Component Monitor (SSH)
Siebel HTTP Monitor
Siebel Enterprise Configuration Monitor
Siebel Collator

Do not reimport the seed data into an established environment without first reviewing existing customizations and taking a configuration backup.

Add the Siebel Application Server

Go to: Workspace -> Left Menu -> Settings -> Wizards -> Siebel App Server

Create an entry for each Siebel Application Server that will be monitored. Provide the requested information, including:

Server name
Hostname or address
Operating system
Siebel Enterprise
Siebel Gateway
Siebel installation path

Show all 9

Application or environment
Assigned GermainUX Engine
Monitoring credentials

Use consistent names across Siebel, GermainUX, infrastructure monitoring, and operational documentation.

Add monitoring credentials

Create a stored credential for the Siebel server and Server Manager connection. Use the GermainUX credential-management interface and provide, as applicable:

Username
Password
Domain
Secure key
Authentication type

Older deployments commonly use SADMIN, but a dedicated least-privilege monitoring account is recommended. Grant only the permissions required to retrieve Server Manager information and perform the configured availability checks. Do not place usernames or passwords directly in scripts or monitor configuration fields.

Configure task-level monitoring

Task-level monitoring provides visibility into the individual tasks and processes running within each Siebel component. Without this information, teams may detect that a server or Enterprise is degraded but have insufficient evidence to identify the responsible component or task. This can result in unnecessary Enterprise-wide restarts. Task monitoring should provide:

Component run state
Number of running tasks
Maximum configured tasks
Task utilization percentage
Number of active multithreaded-server processes
Maximum multithreaded-server processes
Task utilization per process
Task identifiers and states

Recommended initial thresholds

The following values are starting recommendations. Adjust them for the Siebel version, architecture, component purpose, workload, and expected operating state.

Siebel component	Acceptable `CP_DISP_RUN_STATE`	`CP_NUM_RUN_TASKS` threshold	`CP_ACTV_MTS_PROCS` threshold
`WorkActn`	Running or Shutdown	Not applicable	`CP_MAX_MTS_PROCS`
`WorkMon`	Running or Shutdown	Not applicable	`CP_MAX_MTS_PROCS`
`Wf*`	Running, Shutdown, or Online	Less than 95% of `CP_MAX_TASKS`	`CP_MAX_MTS_PROCS`
`ObjMgr`	Running, Shutdown, or Online	Less than 95% of `CP_MAX_TASKS`	`CP_MAX_MTS_PROCS`
`SRBroker`	Running, Shutdown, or Online	Less than 95% of `CP_MAX_TASKS`	`CP_MAX_MTS_PROCS`
`SRProc`	Running or Shutdown	Equal to `DfltTasks`, typically 2	`CP_MAX_MTS_PROCS`
`SCBroker`	Running or Shutdown	Equal to `DfltTasks`, typically 2	Not applicable
Other Siebel components	Running, Shutdown, or Online	Less than 95% of `CP_MAX_TASKS`	`CP_MAX_MTS_PROCS`

Application Monitoring for Oracle Siebel CRM (Configure): Recommended initial thresholds

Review and approve the final SLA thresholds with the Siebel application and operations owners before enabling production alerts.

Task metrics rule

The preconfigured rule is available under: Workspace > Analytics > Rules >siebel-app-monitor-drl>Component Task Metrics It generates the following metrics:

Metric type	Description
`Siebel:Task`	Number of running tasks for the component
`Siebel:TaskPct`	Percentage of the component’s maximum tasks currently running
`Siebel:Running Tasks Process`	Average number of running tasks per active process
`Siebel:Max Tasks Process`	Maximum configured tasks per process
`Siebel:TaskPct Process`	Percentage of the per-process task capacity in use
`Siebel:MtsProcs`	Number of active multithreaded-server processes
`Siebel:MtsProcsPct`	Percentage of the maximum multithreaded-server processes currently active

The metrics retain task details such as server, component alias, component group, task ID, process ID, state, run mode, timestamps, status, parent task, label, and task type. Customize the rule only when the standard task calculations do not match the organization’s Siebel configuration.

Configure the Object Manager parser

The Object Manager parser processes Siebel component logs. Go to: Workspace > Settings > Wizards > Parser Configure:

Field	Value
Monitoring node	Select the applicable monitoring node
Engine	Select the Engine assigned to the Siebel server
Parser component type	`Siebel Object Manager Parser` for the applicable operating system
Monitored application	`Siebel`, or the configured application name
Monitored application component	Leave empty unless a specific component assignment is required
Number of instances	`1`

For English-language Siebel logs, set the parser resource file to:

/com/germainsoftware/apm/localization/parser-siebel-objmgr-enu.properties

Use the corresponding localized resource file when processing logs written in another supported language.

Configure the Server Manager parser

The Server Manager parser processes the output collected from Siebel Enterprise Manager or Server Manager. Go to: Workspace > Settings > Wizards > Parser

Configure:

Field	Value
Monitoring node	Select the applicable monitoring node
Engine	Select the Engine assigned to the Siebel environment
Parser component type	`Siebel Enterprise Manager Parser`
Monitored application	`Siebel`, or the configured application name
Monitored application component	Leave empty unless a specific assignment is required
Number of instances	`1`

For English-language output, configure:

/com/germainsoftware/apm/localization/parser-siebel-em-enu.properties

Review the configuration and submit it.

Configure Siebel log monitoring

Go to: Workspace > Settings > Wizards > Directory Monitor Configure the log directory monitor:

Field	Recommended value
Directory component type	`Siebel Log Directory Monitor`
Name	`Siebel Log Directory Monitor`, or a descriptive environment-specific name
Monitored server	The previously created Siebel server
Path to monitor	Location of the Siebel log files, accessible from the Engine
Watch subdirectories	`No`, unless the deployment requires recursive monitoring
Process existing files	`Yes` for initial ingestion; review volume before enabling in production
Process empty files	`No`
Force polling	`Yes`
Polling interval	`300000` milliseconds, equivalent to five minutes

Although older interfaces may label the polling interval in seconds, the documented value 300000 is in milliseconds. If processing existing files would ingest a large historical volume, initially limit the file scope or disable historical processing.

Configure crash-file monitoring

Go to: Workspace > Settings > Wizards > Directory Monitor Configure:

Field	Recommended value
Directory component type	`Siebel Crash Directory Monitor`
Name	`Siebel Crash Directory Monitor`, or an environment-specific name
Monitored server	The previously created Siebel server
Path to monitor	Location of Siebel crash and core files
Watch subdirectories	`No`, unless required
Process existing files	`Yes`
Process empty files	`No`
Force polling	`Yes`
Polling interval	`300000` milliseconds, equivalent to five minutes

Confirm that the Engine service account can read the crash directory and that storage-retention policies prevent diagnostic files from consuming excessive disk space.

Configure Gateway monitoring

The Siebel Enterprise configuration is stored in siebns.dat. Monitor this file to detect and analyze Gateway configuration changes. Go to: Workspace > Settings > Wizards > Directory Monitor

Configure:

Field	Recommended value
Directory component type	`Siebel Enterprise Configuration Monitor`
Name	`Siebel Enterprise Configuration Monitor`
Monitored server	The Siebel Gateway server
Path to monitor	Directory containing `siebns.dat`
Watch subdirectories	`No`
Process existing files	`Yes`
Process empty files	`No`
Force polling	`Yes`
Polling interval	`300000` milliseconds, equivalent to five minutes

Verify that the configured path points to the active Gateway configuration rather than an obsolete copy or backup.

Configure remote Siebel component monitoring

Use the operating-system-appropriate component monitor:

OS	Component
Windows	`Siebel Component Monitor (WMI)` for Windows
Unix or Linux	`Siebel Component Monitor (SSH)` for Unix or Linux

Configure:

Field	Recommended value
Name	`Components Status Monitor`, or an environment-specific name
Monitored server	The previously created Siebel server
Monitored application	`Siebel`, or the configured application name
Credentials	The stored Siebel monitoring credential
Interval	`300` seconds
Local WMI connection	`No` for a remote Windows server
Component type	`Siebel Component Monitor (WMI)` or `Siebel Component Monitor (SSH)`

Add the following references to the component deployment:

Reference	Value
`SiebelCredentials`	Reference to the stored Siebel credential
`SiebelGateway`	Siebel Gateway hostname
`SiebelServer`	Reference to the configured Siebel server
`SiebelEnterprise`	Siebel Enterprise name
`SiebelPath`	Siebel installation path, such as `C:\sba811v2`
`ExcludedComponents`	Optional comma-separated list of components to exclude

For example:

SiebelGateway = gcgsiebel77
SiebelEnterprise = sba_81
SiebelPath = C:\sba811v2

Replace the example values with the values for the monitored environment.

Configure the Siebel Config Collator

The Siebel Config Collator correlates the configuration data collected from the monitored Siebel environment. In the configuration interface, locate:

MonitoringConfig > Siebel Config Collator

Configure:

Field	Value
Monitoring node	Applicable monitoring node
Engine	Engine assigned to the Siebel environment
Component type	`Siebel Config Collator`
Name	`Siebel Config Collator`, or a descriptive alternative

Review and submit the configuration.

Application Monitoring for Oracle Siebel CRM (Configure): Configure the Siebel Config Collator

Configure HTTP and SISNAPI monitoring

Configure the Siebel HTTP Monitor to validate the web tier and, where applicable, the SISNAPI path to a selected Siebel component. Locate:

MonitoringConfig > Siebel HTTP Monitor

Configure:

Field	Recommended value
HTTP component type	`Siebel HTTP Monitor`
Name	`Siebel HTTP Monitor`
Server	Previously configured Siebel server
Application	Siebel application to monitor
Scheme	`HTTPS` for production, or the scheme used by the environment
Port	Environment-specific port, such as `443` for HTTPS or `80` for HTTP
Repeat interval	`300` seconds

Add these references to the monitor:

Reference	Value
`SiebelCredentials`	Reference to the stored Siebel monitoring credential
`SiebelComponent`	Component to validate through SISNAPI

Use HTTPS wherever supported. Do not use the historical HTTP and port 80 defaults when the Siebel environment requires TLS.

Include or exclude Siebel components

Exclude components that are intentionally disabled, unused, or not operationally relevant. This prevents unnecessary collection and false availability alerts.

Open the Siebel component monitor.
Siebel Availability Monitor - GermainUX
Locate References.
Add a reference named:

ExcludedComponents

Application Monitoring for Oracle Siebel CRM (Configure): Include or exclude Siebel components

Enter the component aliases as a comma-separated list.

For example:

EAIObjMgr_enu,CommInboundRcvr,WorkMon

Use exact component aliases. Do not insert spaces unless they are part of the actual alias. Follow the same configuration pattern when the selected monitor supports an inclusion reference. Review exclusions regularly. A component that becomes operationally important should not remain excluded.

Configure KPIs and SLAs

After collection begins:

Verify that each expected Siebel KPI receives data

Establish a baseline during representative business activity

Configure warning and critical thresholds

Create alerts for availability, state, error, task, process, and capacity conditions

Configure maintenance periods for planned Siebel outages

Route alerts to the team responsible for the affected component

Add diagnostic or corrective actions where appropriate

Particular attention should be given to:

Component availability
Object Manager response time
Running tasks
Task utilization percentage
Tasks per process
Active MTS processes

Show all 12

MTS process utilization
Server Manager errors
Crash and core files
Log errors
HTTP availability
SISNAPI availability

See KPIs for Oracle Siebel CRM.

Dashboards

GermainUX includes preconfigured dashboards for Siebel CRM. Search the dashboard catalog for names beginning with Siebel, including:

Siebel Performance
Siebel Availability

Use dashboard filters to select the intended:

Application
Environment
Enterprise
Server
Component
Time range

Validate the configuration

Server Manager and task data

Confirm that:

Siebel servers and components appear.
Component states are current.
Running and maximum task values are populated.
Task percentages are calculated correctly.
MTS process metrics appear.
Excluded components are omitted.
Collection repeats at the configured interval.

Log and parser data

Confirm that:

The Engine can read the log paths.
New files and entries are detected.
Object Manager logs use the correct parser.
Server Manager output uses the Enterprise Manager parser.
Localized log content is parsed correctly.
Errors and exceptions populate the expected KPIs.

Crash and Gateway data

Confirm that:

Crash or core files are detected.
The correct crash parser is selected.
siebns.dat is monitored from the active Gateway.
Configuration changes produce the expected events.

HTTP and SISNAPI

Confirm that:

The web endpoint is reachable.
TLS validation succeeds.
Authentication succeeds when required.
The configured Siebel component responds.
Response times and availability populate the expected KPIs.

Troubleshooting

If no Siebel application data appears:

Confirm that the Engine is online

Verify that the monitors are assigned to the correct Engine

Test WMI, SSH, HTTP, and file access from the Engine host

Confirm that the stored credential is valid

Verify the Siebel Enterprise, Gateway, server, and installation path

Confirm that all required component references are present

Verify that the parser and directory-monitor component types were imported

Check the Engine logs for authentication, permission, path, or parsing errors

Confirm that the intended components are not listed under ExcludedComponents

Verify that the monitoring intervals have elapsed

Confirm that the relevant KPIs are enabled

Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.

Recommended implementation order

Add the Siebel Application Server

Configure Gateway monitoring

Troubleshooting

​Configure GermainUX’s Application Monitoring for Oracle Siebel CRM

​Configure Application Monitoring for Oracle Siebel CRM

​Recommended implementation order

​Prerequisites

​Open the Siebel wizards

​Verify the Siebel component types

​Add the Siebel Application Server

​Add monitoring credentials

​Configure task-level monitoring

​Recommended initial thresholds

​Task metrics rule

​Configure the Object Manager parser

​Configure the Server Manager parser

​Configure Siebel log monitoring

​Configure crash-file monitoring

​Configure Gateway monitoring

​Configure remote Siebel component monitoring

​Configure the Siebel Config Collator

​Configure HTTP and SISNAPI monitoring

​Include or exclude Siebel components

​Configure KPIs and SLAs

​Dashboards

​Validate the configuration

​Server Manager and task data

​Log and parser data

​Crash and Gateway data

​HTTP and SISNAPI

​Troubleshooting

​Related documentation

​Get Help

Contact GermainUX Support

Can't find what you need?

Configure GermainUX’s Application Monitoring for Oracle Siebel CRM

Configure Application Monitoring for Oracle Siebel CRM

Recommended implementation order

Prerequisites

Open the Siebel wizards

Verify the Siebel component types

Add the Siebel Application Server

Add monitoring credentials

Configure task-level monitoring

Recommended initial thresholds

Task metrics rule

Configure the Object Manager parser

Configure the Server Manager parser

Configure Siebel log monitoring

Configure crash-file monitoring

Configure Gateway monitoring

Configure remote Siebel component monitoring

Configure the Siebel Config Collator

Configure HTTP and SISNAPI monitoring

Include or exclude Siebel components

Configure KPIs and SLAs

Dashboards

Validate the configuration

Server Manager and task data

Log and parser data

Crash and Gateway data

HTTP and SISNAPI

Troubleshooting

Related documentation

Get Help