32 Testing and Monitoring Web Services
- Testing Web Services
- Monitoring Web Services and Clients
- Using Work Managers to Prioritize Web Services Work and Reduce Stuck Execute Threads
Parent topic: Developing Advanced Features of JAX-WS Web Services
Testing Web Services
You can test basic and advanced features of your web service, such as security, quality of service (QoS), HTTP headers, and so on. You can also perform stress testing of the security features. For information about testing web services using the Web Services Test Client or Fusion Middleware Control Test Web Service page, see Testing Web Services in Administering Web Services.
Parent topic: Testing and Monitoring Web Services
Monitoring Web Services and Clients
You can monitor runtime information for web services and clients, such as number of invocations, errors, faults, and so on, using the WebLogic Remote Console or WLST.
The following naming convention is used to identify the web service or client in the monitoring pages:
<application_name>#<application_version>!<service_name><contextpath><url_pattern>
Where:
-
application_name—Name of the application that contains the web service or client. -
application_version—Version of the application that contains the web service or client. -
service_name—Name of the web service or client. -
context_path—Context path defined for the web service. For more information, see Defining the Context Path of a WebLogic Web Service. -
url_pattern—System default or user-defined web service URL pattern. For more information, see Specifying the Transport Used to Invoke the Web Service.
Parent topic: Testing and Monitoring Web Services
Monitoring Web Services
The following table lists the tabs that you can select to monitor web service information. The pages aggregate the statistics of all the servers on which the web service is running.
Note:
For JAX-WS web services, the built-in Ws-Protocol operation displays statistics that are relevant to the underlying WS-* protocols. This information is helpful in evaluating the application performance.
Table 32-1 Monitoring Web Services
| Click this tab . . . | To view . . . |
|---|---|
|
Monitoring> General |
General statistics about the web services, including total error and invocations counts. |
|
Monitoring> Invocations |
Invocation statistics, such as dispatch and execution times and averages. |
|
Monitoring> WS-Policy |
Policies that are attached to the web service, organized into the following categories: authentication, authorization, confidentiality, and integrity. |
|
Monitoring> Ports |
Table listing the web service endpoints (ports). The table provides a summary of information for each port. Click a port name to view more details. |
|
Monitoring> Ports > General |
General statistics about the web service endpoint. The page displays information such as the web service endpoint name, its URI, and its associated web service, Enterprise application, and application module. Error and invocations counts are aggregated for all web service endpoint operations. |
|
Monitoring> Ports > Invocations |
Invocation statistics for the web service endpoint, such as success, fault, and violation counts. |
|
Monitoring> Ports > Cluster Routing |
Cluster routing statistics for the web service endpoint, such as request and response, and routing failures. |
|
Monitoring> Ports > Make Connection |
MakeConnection anonymous endpoints for a web service. For each anonymous endpoint, runtime monitoring information is displayed, such as the number of messages received, the number of messages pending, and so on. You can customize the information that is shown in the table by clicking Customize this table. Click the name of an anonymous endpoint to view more details. |
|
Monitoring> Ports > Reliable Message |
Reliable messaging sequences for a web service. For each reliable messaging sequence, runtime monitoring information is displayed, such as the sequence state, the source and destination servers, and so on. You can customize the information that is shown in the table by clicking Customize this table. Click the sequence ID to view more details. |
|
Monitoring> Ports > Reliable Message > Requests |
Reliable messaging requests for a web service. For each reliable messaging request, runtime monitoring information is displayed. You can customize the information that is shown in the table by clicking Customize this table. Click the reliable message ID to view more details. |
|
Monitoring> Ports > WS-Policy |
Statistics related to the policies that are attached to the web service endpoint, organized into the following categories: authentication, authorization, confidentiality, and integrity. |
|
Monitoring> Ports > Operations |
List of operations for the web service endpoint. For each operation, runtime monitoring information is displayed, such as the number of times the operation has been invoked since the WebLogic Server instance started, the average time it took to invoke the web service, the average time it took to respond, and so on. You can customize the information that is shown in the table by clicking Customize this table. Note: For JAX-WS web services, the built-in Ws-Protocol operation displays statistics that are relevant to the underlying WS-* protocols. For example, for web services reliable messaging, this operation captures message statistics for Click the name of an operation to view more information. Click the General or Invocations tab to display general statistics or invocation statistics, respectively, for the selected operation. |
Parent topic: Monitoring Web Services and Clients
Monitoring Web Service Clients
The table provides a summary of runtime information for each web service client. Click the client name in the table to view more information.
Note:
For JAX-WS web services, the web services runtime creates system-defined client instances within a web service endpoint that are used to send protocol-specific messages as required by that endpoint. These client instances are named after the web service endpoint that they serve with the following suffix: -SystemClient. Monitoring information relevant to the system-defined client instances is provided to assist in evaluating the application.
Table 32-2 Monitoring Web Service Clients
| Click this tab . . . | To view . . . |
|---|---|
|
Monitoring> General |
General statistics about the web service clients, including total error and invocations counts. The page displays the web service client name, its associated Enterprise application and application module, and context root. Error and invocations statistics are aggregated for all servers on which the web service is running. |
|
Monitoring> Invocations |
Invocation statistics, such as dispatch and execution times and averages. |
|
Monitoring> WS-Policy |
Policies that are attached to the web service client, organized into the following categories: authentication, authorization, confidentiality, and integrity. |
|
Monitoring> Servers |
Table listing the server on which the client is currently running. Click the client name and then use the tabs in the following steps to view more information about the web service client on that server. |
|
Monitoring> Servers > General |
General statistics about the web service client. The page displays information such as the web service client port, its associated Enterprise application, and application module, context root, and so on. Error and invocations counts are aggregated for all web service client operations. |
|
Monitoring> Servers > Invocations |
Invocation statistics for the web service client, such as success, fault, and violation counts. |
|
Monitoring> Servers > Cluster Routing |
Cluster routing statistics for the web service client, such as request and response, and routing failures. For more information, see Monitoring Cluster Routing Performance. |
|
Monitoring> Servers > Make Connection |
MakeConnection anonymous endpoints for a web service client. For each anonymous endpoint, runtime monitoring information is displayed, such as the number of messages received, the number of messages pending, and so on. You can customize the information that is shown in the table by clicking Customize this table. Click the name of an anonymous endpoint to view more details. |
|
Monitoring> Servers > Reliable Message |
Reliable messaging sequences for a web service client. For each reliable messaging sequence, runtime monitoring information is displayed, such as the sequence state, the source and destination servers, and so on. You can customize the information that is shown in the table by clicking Customize this table. Click the name of an anonymous endpoint to view more details. |
|
Monitoring> Servers > WS-Policy |
Statistics related to the policies that are attached to the web service client, organized into the following categories: authentication, authorization, confidentiality, and integrity. |
|
Monitoring> Servers > Operations |
List of operations for the web service client. For each operation, runtime monitoring information is displayed, such as average response, execution, and dispatch times, response, invocation and error counts, and so on. You can customize the information that is shown in the table by clicking Customize this table. Click the name of an operation to view more information. Click the General or Invocations tab to display general statistics or invocation statistics, respectively, for the selected operation. |
Parent topic: Monitoring Web Services and Clients
Using Work Managers to Prioritize Web Services Work and Reduce Stuck Execute Threads
After a connection has been established between a client application and a web service, the interactions between the two are ideally smooth and quick, whereby the client makes requests and the service responds in a prompt and timely manner. Sometimes, however, a client application might take a long time to make a new request, during which the web service waits to respond, possibly for the life of the WebLogic Server instance; this is often referred to as a stuck execute thread. If, at any given moment, WebLogic Server has a lot of stuck execute threads, the overall performance of the server might degrade.
If a particular web service gets into this state fairly often, you can specify how the service prioritizes the execution of its work by configuring a Work Manager and applying it to the service. For example, you can configure a response time request class (a specific type of Work Manager component) that specifies a response time goal for the web service.
The following shows an example of how to define a response time request class in a deployment descriptor:
<work-manager>
<name>responsetime_workmanager</name>
<response-time-request-class>
<name>my_response_time</name>
<goal-ms>2000</goal-ms>
</response-time-request-class>
</work-manager>
You can configure the response time request class using the WebLogic Remote Console.
For more information about Work Managers in general and how to configure them for your web service, see Using Work Managers to Optimize Scheduled Work in Administering Server Environments for Oracle WebLogic Server.
Parent topic: Testing and Monitoring Web Services