This subsection describes how to use the performance analysis trace file for analyzing the response time of all the Web Services including the JAX-WS engine and the response time of a Web Service (UP). Note that this subsection describes an example of Web Services developed using Web Service Implementation Classes and stub-based Web Service clients. The event IDs might differ for other Web Services and Web Service clients, so substitute and read as and when required.

Using the event IDs '0xA408', '0xA40C', '0xA410', and '0xA414' as the keys, the Trace based performance analysis file will be filtered. The following table lists and describes the trace collection points for each event ID.

Table 39-28 Trace collection points corresponding to the event IDs to be filtered

No.	Event ID	Trace collection points
1	0xA408	When the servlet of the JAX-WS engine starts
2	0xA40C	Before the Web Service is invoked
3	0xA410	After the Web Service is invoked
4	0xA414	Before a SOAP Message of the JAX-WS engine is sent

The following figure shows an example of filtering the trace based performance analysis files by setting the event IDs '0xA408', '0xA40C', '0xA410', and '0xA414' as keys, when a request is sent twice.

Figure 39-16 Example of filtering the Trace based performance analysis

You can check the request processing status from the client application information. If the same request is being processed, the same client application information is output.

You can analyze the response time of all the Web Services including the JAX-WS engine from the trace collection time of the event IDs '0xA408' and '0xA414' in the identical client application information. You can also analyze the response time of a Web Service (UP) from the trace collection point of '0xA40C' and '0xA410'.

This subsection describes how to analyze the response time of Web resources including the JAX-RS engine and the response time of a Web resource (UP) by using the performance analysis trace file.

You filter the performance analysis trace file by setting the event IDs [0xA4A0], [0xA4A2], [0xA4A3], and [0xA4A1] as keys. The following table lists the event IDs and their trace collection points.

Table 39-29 Trace collection points for the event IDs to be filtered

No.	Event ID	Trace collection point
1	0xA4A0	When starting a servlet of a JAX-RS engine
2	0xA4A2	Before calling a Web resource
3	0xA4A3	After calling a Web resource
4	0xA4A1	Before sending an HTTP message of a JAX-RS engine

The following figure shows an example of filtering the performance analysis trace files by setting the event IDs [0xA4A0], [0xA4A2], [0xA4A3], and [0xA4A1] as keys, when a request is sent twice.

Figure 39-17 Example of filtering performance analysis traces

You can check the request processing status from the client application information. When processing the same request, the same client application information is output.

You can analyze the response time of all the Web resources including the JAX-RS engine, starting from the time of the trace collection for the event IDs [0xA4A0] and [0xA4A1] of the same client application information. Also, you can analyze the response time of the Web resource (UP) starting from the time of the trace collection for [0xA4A2] and [0xA4A3].