In some cases Siebel servers not started after bounce and our investigation lead us to conclusion that clean bounce of Siebel Severs is must whenever below scenario is being faced:

Siebel Server is not starting up after bounce
Getting SISNAPI error for MQ components

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:

Scripting has never been recommended by experts in Siebel application. Customization is required to configure customer requirement which is difficult to achieve with tools. Here are some eScripting Do’s & Don’t which will help you to avoid future problems.

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.

Hi everybody. As you know, when using a VBC, the returned records can not be sorted (because its a VBC restriction). In this post i will give you a scripting solution to do this. The explanation is a little long, please be patient.