This metric reflects the time required to process the request for a SOAP operation, build a response and begin the initial transmission of the response. This metric does not include any network delays or client-side processing delays.
See the “Calculation” section of for a low-level description of how this metric is calculated.
This metric provides an estimate of the peak number of SOAP operations per second that are processed by the web service. This gives you the ability to evaluate the peak load that a SOAP Web Service experiences when evaluating SLAs. Some SLAs provide exemptions if concurrent activity exceeds a predetermined level. This metric provides a benchmark by which you can evaluate the peak levels of activity that a web service experiences.
The algorithm for this metric records the termination time of each SOAP operation as it completes. The termination time is used because that is the event that indicates the operation was successfully completed. These times are then evaluated to determine the maximum number of operations that complete in any given second.
In order to respond to a request for a SOAP operation, application servers (for example, IBM® WebSphere® or BEA Systems's WebLogic®) needs to utilize a variety of resources such as databases, network bandwidth, system memory and CPU. The application server must hold many of these resources until the required response is prepared and then transmitted back to the client.
This metric measures the total time needed to process the requested SOAP operation and formulate a response. During that time, many of the resources required to formulate the response may be partially or fully dedicated. The following delays are included in this metric:
See the “Calculation” section of for a low-level description of how this metric is calculated. At a high-level, the metric can be described by this equation: