file. It then retrieved the appropriate SLA files, in this case 100 1.xml was the only one that 

had to be retrieved. This file then configured to proxy to log requests to Yahoo Mail.  

6.3.6 Service Monitoring 

For the purpose of the test a series of requests were made to the Yahoo Mail service over the 

period of one hour. The intention was to use the service as one would normally do but to try 

to access all the service mappings specified in the SLA so as to generate data on usage. 

6.3.7 Results of Case Study 

For this case study, a specific class named 

SLAReporter 

was designed to demonstrate the 

capabilities of the framework. It analysed the data logged by the proxy and the contents of 

the SLA for the service to determine if overall availability and performance are met. It then 

generated a HTML report containing the results of the analysis of the case study. The 

contents of the report for the case study are contained in Appendix E.  

6.3.8 Report Analysis 

SLAReporter

 was configured to run after an hour of service usage to Yahoo Mail. Based on 

the SLA and the data logged for the period of service usage, a report was generated. The 

report contained in Appendix E provided a breakdown of a number of different aspects of 

the service which include: 

Service Usage 

Service Performance 

Service Availability 

The report provides overall performance and availability of the service compared with what 

was specified in the SLA. The service usage is also broken down by each mapping to 

indicating which are most frequently accessed service functions. Detailed performance 

information for each parameter is given including the minimum, average and maximum 

values observed. Then the overall availability of the service is reported and where failures 

a

a

e