Abstract

Runtime monitoring is necessary for continuous quality assurance of Web Services. Sensors are critical in runtime monitoring to capture the data and detect anomalies. However, sensors in current monitoring systems are usually manually instrumented or hard-coded in the program. It is expensive to implement, and inflexible to change at runtime. The paper extends our previous research on collaborative monitoring and proposes a model-based approach for automatic generating sensors and enforcing policies. Web Services standards WSDL and OWL-S are taken as the models of service interface, workflow, and semantic. Sensors are generated based on the models from two perspectives: (1) dependency analysis of the data, operations, and services with respect to the ontology model of domain concepts and usage context; (2) coverage strategies to decide the specific logic and paths to cover and the data to capture by the monitoring sensors. Policies are defined as a 3-tuple of type, subject and assertion sets and are specified using WS-Policy standards. They are associated to the sensors and enforced at runtime by the policy engine that interoperates with service execution engine to communicate runtime behavior information and verification results. Prototype system is implemented based on the Eclipse platform where sensors are implemented as the listeners to the process execution and instrumented into the middleware including the OWL-S execution engine and SOAP engine. Experiments show that the monitoring results in low overhead of the system performance, reduced effort and enhanced flexibility of sensor instrumentation.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.