When an end user clicks a view tab to navigate to a new view, a chain of processes is invoked on different machines in order to handle the request. For example, the Siebel Web Server Extension must connect to the application object manager (AOM) on the Siebel server. The AOM will issue an SQL statement to the Siebel database and the Siebel Web Engine (SWE) will put the view layout and data together and render the view.
In order to be able to make exact measurements to determine performance bottlenecks quickly, Siebel engineers have included instrumentation points in the core program code of all Siebel software components.
This feature is commonly known as Siebel Application Response Measurement (SARM). The following diagram explains how SARM works:
From the above diagram, we can learn the following about Siebel Application Response Measurement:
Requests from the web client are processed on the Siebel Web Server Extension (SWSE) on the web server...