Application Monitoring for Oracle Siebel CRM (Configure)

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.

▶️ Recommended implementation order

Configure Siebel monitoring in this order:

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:

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:

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:

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:

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:

Field
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:

📈 Recommended initial thresholds

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

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:

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:

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:

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:

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:

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:

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:

Configure:

Add the following references to the component deployment:

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:

Review and submit the configuration.

🌐 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:

Add these references to the monitor:

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.

1. Open the Siebel component monitor.
   

   

2. Locate References.

3. Add a reference named:

ExcludedComponents

4. 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:

1. Verify that each expected Siebel KPI receives data.

2. Establish a baseline during representative business activity.

3. Configure warning and critical thresholds.

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

5. Configure maintenance periods for planned Siebel outages.

6. Route alerts to the team responsible for the affected component.

7. 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

• 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:

1. Confirm that the Engine is online.

2. Verify that the monitors are assigned to the correct Engine.

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

4. Confirm that the stored credential is valid.

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

6. Confirm that all required component references are present.

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

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

9. Confirm that the intended components are not listed under ExcludedComponents.

10. Verify that the monitoring intervals have elapsed.

11. Confirm that the relevant KPIs are enabled.

📚 Related documentation

• Oracle Siebel CRM Monitoring Configuration

• Engine Deployment for Oracle Siebel CRM

• Crash Monitoring for Oracle Siebel CRM

• Error Monitoring for Oracle Siebel CRM

• Business Process Monitoring for Oracle Siebel CRM

• RPA Bots for Proactive Issue Detection and Resolution

ℹ️ Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Oracle Siebel CRM environment.

Contact GermainUX Support.