Web Service: Monitoring: Ports: General
Configuration Options Related Tasks Related Topics
Use this page to monitor general statistics of a Web service or Web service client endpoint on a single server. This page aggregates the statistics of all the endpoint operations.
Name Description Port
Specifies the name of this port.
This attribute corresponds to the "name" attribute of the "port" element in the WSDL that describes the Web Service. Programmers specify the name of the port using the portName attribute of the
Transport Protocol Type
Specifies the transport protocol used to invoke this Web Service, such as HTTP, HTTPS, or JMS.
This attribute determines the transport that is published in the endpoint address section of the WSDL of the Web Service. Programmers specify the transport by the type of @WLXXXTransport JWS annotation they specify, where XXX refers to the type of transport (HTTP, HTTPS, or JMS).
Programmers can also use the WLXXXTransport child element of the jwsc Ant task to specify this attribute.
Specifies the URI of this Web service.
This attribute corresponds to the final part of the endpoint address in the WSDL that describes the Web Services. It is specified at development time for JAX-RPC services using the serviceURI attribute of the @WLXXXTransport JWS annotation, where XXX refers to the transport, such as HTTP, HTTPS, or JMS. For JAX-WS services, this can be set during compilation.
Specifies the qualified name of this Web service.
This attribute is calculated and of the form
<app name>#<app version>!<service name>.
Gets the client ID for this client.
The name of the Enterprise application.
Returns the web-uri as configured in application.xml for the webapp. For a standalone war it will return the docroot (if exploded) or name of the war file (if archived).
Returns the context root (context path) for the webapp
An alphanumeric name for this server instance. (Spaces are not valid.)
The name must be unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.
The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.
After you have created a server, you cannot change its name. Instead, clone the server and provide a new name for the clone.
The WebLogic Server host computer (machine) on which this server is meant to run.
If you want to use a Node Manager to start this server, you must assign the server to a machine and you must configure the machine for the Node Manager.
You cannot change this value if a server instance is already running.
Date and time that the web service endpoint starts
Total number of errors.
Response Error Count
Total number of response errors.
Total number of security policy faults.
Total number of invocations.
Total number of responses.
Dispatch Time Average
Average dispatch time.
Execution Time Average
Average execution time.
Response Time Average
Average response time.
- Install a Web service
- Start and stop a Web service
- Attach a WS-Policy file to a Web service
- Configure Web services
- View the SOAP message handlers of a Web service
- View the WSDL of a Web service
- Test a Web service
- Monitor Web services
- Monitor Web service clients
- Introducing Web Services for Oracle WebLogic Server
- Getting Started With JAX-WS Web Services for Oracle WebLogic Server
- Getting Started With JAX-RPC Web Services for Oracle WebLogic Server
- Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server
- Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server
- Securing Web Services for Oracle WebLogic Server
- Web Services Reference for Oracle WebLogic Server