Siebel Application Response Management (SARM) is a framework for identifying performance problems in the Siebel enterprise application. SARM allows administrators to collect critical performance and timing data,

The Siebel Server runs each component in its own separate process (or shell). These shells provide interface for a component to communicate with shared memory, and use infrastructure facilities for logging, events, networking, and so on. A shell performs the following actions when it is forked off:

We faced a strange situation as components were not taking any request and component were going to “UNAVAILABLE” state. This should not happen especially for the *Application Object Manager Components.

Siebel Error Codes are most challenging barriers for a developer. It’s very difficult to understand the exact problem in configuration by seeing the error codes. Consultant spent their important time in searching at number of blogs and oracle metalink support to find the correct explanation of the Siebel Error Codes. We are providing you a library of all siebel error codes to make your search efficient.

In last article "How to capture the eCommunications logs for specific users in Siebel" we have learned How to set user list and log levels.  This article will help us in finding logs for any specific user.