> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Application Monitoring for Oracle Siebel CRM (Configure)

> This guide explains how to configure health and performance monitoring for the Siebel Enterprise, Gateway, Application Servers, and Object Managers.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/main/germain-ux-rum-js)

Availability
2014.1 or later

> [card] [Recommended implementation order](#recommended-implementation-order)
>
> Synthetic checks come first

> [card] [Add the Siebel Application Server](#add-the-siebel-application-server)
>
> Register each app server

> [card] [Configure Gateway monitoring](#configure-gateway-monitoring)
>
> Track siebns.dat changes

> [card] [Troubleshooting](#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.

> [!NOTE]
>
> 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.

> [accordion] 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](https://docs.germainux.com/main/engine-deployment-for-oracle-siebel-crm.md).

### Open the Siebel wizards

In GermainUX, go to:

**Workspace -> Left Menu → Settings > Wizards -> \<search for Siebel or whichever keyword related to what you need>**

![Application Monitoring for Oracle Siebel CRM (Configure): Open the Siebel wizards](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image-20260828-134714.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=ee7f5951c5f21abfc45c5ab912998c06)

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:

```text theme={null}
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:

```text theme={null}
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`

> [accordion] 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**

![Application Monitoring for Oracle Siebel CRM (Configure): Add the Siebel Application Server](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image-20260828-134945.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=a926ecfdb99a3d4e11d26810df0e002a)

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

> [accordion] 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   ![Application Monitoring for Oracle Siebel CRM (Configure): Add monitoring credentials](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image-20260828-141648.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=9c3f290e46f6556d739a91c8e0131b30)

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](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/38c4cba0-535e-477f-877d-8321319f876c.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=15a75e155902e9c69fc3ac0cd2702986)

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:

```text theme={null}
/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**

![Application Monitoring for Oracle Siebel CRM (Configure): Configure the Server Manager parser](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image-20260828-135156.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=e5f016ead66b85ad53e33f0c54de8699)

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:

```text theme={null}
/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**

![Application Monitoring for Oracle Siebel CRM (Configure): Configure Gateway monitoring](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image-20260828-135414.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=436c88d0813d11039e9fbd81ec156e68)

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:

```text theme={null}
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:

```text theme={null}
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](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image2019-4-8_16-24-20.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=1bdd0e9c1aa627e96f3ccd6ea49e5728)

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

```text theme={null}
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.

1. Open the Siebel component monitor.

   ![Siebel Availability Monitor](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image-20210629-155541.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=7a9afb0eb24b2a8587111cdc632475fc)

   Siebel Availability Monitor - GermainUX
2. Locate **References**.
3. Add a reference named:

```text theme={null}
ExcludedComponents
```

![Application Monitoring for Oracle Siebel CRM (Configure): Include or exclude Siebel components](https://mintcdn.com/germain-ux/uY3MrHiwPZBkcqjb/images/main/siebel-application-monitoring-configuration/image-20210629-155652.png?fit=max\&auto=format\&n=uY3MrHiwPZBkcqjb\&q=85\&s=c4a35eb15f905858f9f736c24b04300c)

1. Enter the component aliases as a comma-separated list.

For example:

```text theme={null}
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

> [accordion] 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](https://docs.germainux.com/main/oracle-siebel-crm-monitoring-kpis.md).

### 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](https://docs.germainux.com/main/oracle-siebel-crm-monitoring-configuration.md)
* [Engine Deployment for Oracle Siebel CRM](https://docs.germainux.com/main/engine-deployment-for-oracle-siebel-crm.md)
* [Crash Monitoring for Oracle Siebel CRM](https://docs.germainux.com/main/siebel-crash-monitoring-configuration.md)
* [Error Monitoring for Oracle Siebel CRM](https://docs.germainux.com/main/siebel-error-monitoring-configuration.md)
* [Business Process Monitoring for Oracle Siebel CRM](https://docs.germainux.com/main/siebel-business-process-monitoring-configuration.md)
* [RPA Bots for Proactive Issue Detection and Resolution](https://docs.germainux.com/main/rpa-bots-for-proactive-issue-detection-and-resolut.md)

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> 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.

> [card] 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.