Abstract

When an SOA business process fails to deliver the desired quality of service (QoS), it is necessary to identify the faulty services that cause the problem since the source of the problem may not be at where the problem is observed. In this paper, we propose a polynomial time diagnosis algorithm by

Highlights

  • Service oriented architecture (SOA) provides an easy-touse and flexible paradigm for integrating distributed services into business processes (BP) [3, 15]

  • In many applications implemented using SOA, it is important to have an efficient mechanism to identify and replace faulty services that cause a quality of service (QoS) problem in a BP execution

  • The PrintAndMail BP is implemented in our lab and used to test the monitoring and diagnosis performance of the LLAMA middleware

Read more

Summary

Introduction

Service oriented architecture (SOA) provides an easy-touse and flexible paradigm for integrating distributed services into business processes (BP) [3, 15]. Using SOA, enterprise systems can discover and compose services from different service providers both statically or dynamically. In many applications implemented using SOA, it is important to have an efficient mechanism to identify and replace faulty services that cause a quality of service (QoS) problem in a BP execution. To detect QoS violations and to identify the cause of failures, SOA middleware must monitor individual service behaviors at run-time. We design an SOA middleware to monitor only a subset of services in a BP at run time [22]. Whenever an end-to-end QoS problem is detected at a monitored service, the middleware triggers a diagnosis algorithm to identify possible faulty services.

Objectives
Results
Conclusion
Full Text
Published version (Free)

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