Service Dashboard

Every service and service group deployed in a Carbon server has its own Dashboard for management and monitoring. Follow the instructions below to access the dashboard of a service.

1. Log on to the product's management console and select "Services -> List" under the "Main" menu.

2. The "Deployed Services" page appears which lists out all the currently active services. Select a service and click on it to view its dashboard. For example,

A service dashboard provides the following information.

• Service Details
• Client Operations
• Statistics
• Quality of Service Configuration 
  

Service Details

The "Service Details" panel provides the following details of a service:

• Service Name - Defines the unique name of a service.
• Service Description - Briefly describes a service.
• Service Group Name - Defines the name of the group service belongs to. Refer to more information about service groups in section Managing Service Groups.
• Deployment Scope
• Service Type - Specifies service type (for example, Axis2, Proxy, STS).

Client Operations

WSO2 Carbon provides the following client operations:

• Try this service
• Generate Client
• WSDL 1.1/2.0

WSO2 Carbon also provides information about the endpoints of a service. The service is set to two endpoints by default. For example:

1. https://10.100.1.147:9443/services/HelloService/
2. http://10.100.1.147:9763/services/HelloService/

Typically, the endpoint URI is of the format http://{host ip of the server}:{server port}/services/{service name}.

Try This Service   

The "Try this service" link directs you to a new window where the operations available the your service is displayed. Using this window, you can check whether your service provides the desired output. The URL for invoking the TryIt tool can also be appended by concatenating the endpoint URL of your service with the following string:

•  ?tryit : Ajax client for simple, generic interactions with the service.

The TryIt link will be enabled in your service dashboard only if "org.wso2.carbon.tryit" feature of the WSO2 feature repository is installed in your Carbon instance.

For more information on the TryIt functionality, refer to section Tools -> Testing WSDLs.

Generate Client  

You can easily generate a client for your service using the "Generate Client" option. This functionality is provided by the "wsdl.tools" feature of the WSO2 feature repository. For more information, refer to section Tools -> Generate Java Code for WSDL .

WSDL 1.1 and WSDL 2.0  

Click on the links to the WSDL 1.1 and the WSDL 2.0 to open the page with XML configuration. The URLs for the WSDL files of the service can also be appended by concatenating the endpoint URL of the service with the following strings:

• ?wsdl2 : WSDL 2.0 description of the service
• ?wsdl : WSDL 1.1 description of the service

The WSDLs describe the operations the service exposes, the structure of the XML that is sent and received by each operation, and how to communicate with the service to retrieve the XML content. By default, six different types of endpoints are deployed. Each of these endpoint types are represented by the WSDL 2.0 <endpoint> elements of the service, and by the <binding> elements which these endpoints refer to. The default six types of endpoints are as follows:

• SOAP 1.2 over HTTP
• SOAP 1.1 over HTTP
• Plain old XML/REST over HTTP
• SOAP 1.2 over HTTPS
• SOAP 1.1 over HTTPS
• Plain old XML/REST over HTTPS

Statistics

The "Statistics" panel provides statistical information about a service as follows:

• Request Count
• Response Count
• Fault Count
• Maximum Response Time
• Minimum Response Time
• Average Response Time

It also provides a graphical view of the system response time.

This functionality is provided by the "system.statistics" feature of the WSO2 feature repository. For more information, refer to section "System Monitoring and Statistics -> Access and Performance Statistics."

Quality of Service Configuration

WSO2 Carbon provides a number of tools to manage the service quality. You can activate the tools individually as required. For more information, refer to section Quality of Service Configuration.