After a Web service client is installed and started, you can get information about the client, such as its associated application and module, context root, invocation and error counts, and so on.
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 wth the following suffix: -SystemClient.
Monitoring information relevant to the system-defined client instances
is provided to assist in evaluating the application.
To monitor a Web service client:
The table provides a summary of information for each Web service client.
For each client, runtime monitoring information is displayed, such as the invocation, response, and error counts; execution, response, and dispatch time averages; and so on. You can customize the information that is shown in the table by clicking Customize this table.
Click the client name in the table to view more information.
This 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.
Error, invocations, and response statistics are aggregated for all servers on which the Web service is running.
Fault, violations, and success counts are aggregated for all servers on which the Web service client is 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.
This 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.
Invocation, response, and error statistics are aggregated for all Web service client operations
Request, response, and routing counts and failures are aggregated for all Web service client operations.
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.
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 a sequence to view the requests in the sequence.
Success, fault, and violation counts are aggregated for all Web service client operations.
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.