In order to respond to a request for a SOAP operation, application servers (for example, IBM® WebSphere® or BEA Systems's WebLogic®) need 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. The fulfillment of a request for a SOAP operation is therefore involve network delays and some processing time on the client side as it interprets the response it receives.This metric measures the total time needed to complete the requested SOAP operation and send the results back to the client. 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:
Percentile metrics provide a means to quantify the quality of service customers are receiving based on the response time that a fixed percentage (usually 95 percent) of users receive. These metrics are commonly referred to as 95th Percentile metrics. The exact percentage the system uses is configurable by the user.
This metric provides numeric value that represents the upper level of achieved by the desired percentage of events.
To calculate this metric, the system uses a statistical method involving standard deviation rather than by tracking each individual event in memory (that approach would be prohibitive in terms of processing requirements and memory consumption). The percentile metric is calculated using this formula:
If the faultcode element is present in a SOAP response the operation is considered to have failed and this metric is incremented. This metric is also incremented if the SOAP response has a timeout, connection reset or does not contain a response code due to missing packets.