Page Comparison

Sending a message

Now that you have the artifacts deployed and configured for statistics monitoring, let's send 8 requests to the ESB profile as explained below.

1. Create a JSON file called request.json with the following request payload.

   Code Block
   { "name": "John Doe", "dob": "1940-03-19", "ssn": "234-23-525", "address": "California", "phone": "8770586755", "email": "johndoe@gmail.com", "doctor": "thomas collins", "hospital": "grand oak community hospital", "cardNo": "7844481124110331", "appointment_date": "2025-04-02" }

2. Open a command line terminal and execute the following command (six times) from the location where you save the request.json file:
   

   curl -v -X POST --data @request.json  http://localhost:8280/healthcare/categories/surgery/reserve  --header "Content-Type:application/json"

   If the messages are sent successfully, you will receive the following response for each request.

   Code Block
   {"appointmentNo":1, "doctorName":"thomas collins", "patient":"John Doe", "actualFee":7000.0, "discount":20, "discounted":5600.0, "paymentID":"e1a72a33-31f2-46dc-ae7d-a14a486efc00", "status":"Settled"}

3. Now, shut down the back-end service (to ensure that the back-end service is inactive) and send two more requests.

Analyze the mediation statistics

Now, let's analyze the statistics generated from the message mediation:

1. Start the Analytics dashboard:

   Panel
   borderColor #542989 bgColor #ffffff borderWidth 1
   Localtabgroup Localtab title On MacOS/Linux/CentOS Open a terminal and execute the following command: Code Block sudo wso2ei-6.6.0-analytics-dashboard Localtab title On Windows Go to Start Menu -> Programs -> WSO2 -> Enterprise Integrator 6.6.0 Analytics Dashboard. This will open a terminal and start the Analytics profile.

2. In a new browser window or tab, open the Analytics dashboard using the following URL: https://localhost:9643/portal. Use admin for both the username and password. 

3. Click the Enterprise Integrator Analytics icon shown below to open the dashboard.
   
   
   

4. View the statistics overview for all the ESB artifacts that have published statistics:
   

5. The number of transactions handled by the ESB per second is mapped on a graph as follows.

   
   

6. The success rate and the failure rate of the messages received by the ESB profile during the last hour are mapped in a graph as follows.
   

7. The HealthcareAPI REST API is displayed under TOP APIS BY REQUEST COUNT as follows.
   

8. The three endpoints used for the message mediation are displayed under Top Endpoints by Request Count as shown below. 
   
9. In the Top APIS BY Request COUNT gadget, click  HealthcareAPI to open the OVERVIEW/API/HealthcareAPI page. The following is displayed.
   • The API Request Count gadget shows the total number of requests handled by the StockQuoteAPI REST API during the last hour:
     
   • The API Message Count gadget maps the number of successful messages as well as failed messages at different times within the last hour in a graph as shown below.
     
     
   • The API Message Latency gadget shows the speed with which the messages are processed by mapping the amount of time taken per message at different times within the last hour as shown below.
     
     
   • The Messages gadget lists all the the messages handled by the StockQuoteAPI REST API during the last hour with the following property details as follows.
     
     
   • The Message Flow gadget illustrates the order in which the messages handled by the StockQuoteAPI REST API within the last hour passed through all the mediation sequences, mediators and endpoints that were included in the message flow as shown below.
     
     

10. In the Top Endpoints by Request Count gadget, click one of the endpoints to view simillar statistics per endpoint.

    • ChannelingFeeEP

    • SettlePaymentEP

    • GrandOaksEP
11. You can also navigate to any of the artifacts by using the top-left menu as shown below. For example, to view the statistics of a specific endpoint, click Endpoint and search for the required endpoint.