Journal of Lightwave Technology
DOI: 10.1109/icre.2003.1232738
|View full text |Cite
|
Sign up to set email alerts
|

Monitoring Web service requirements

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
60
0

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 95 publications
(60 citation statements)
references
References 31 publications
0
60
0
Order By: Relevance
“…SLA negotiation approaches for service composition have also been proposed [19], [63]. However, services need to be monitored at runtime to substantially guarantee that their qualities conform to the SLAs [50] because SLAs only provide traditional recourse, rather than timely alerts of impending SLA violations [52]. At runtime, anomalies, e.g.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…SLA negotiation approaches for service composition have also been proposed [19], [63]. However, services need to be monitored at runtime to substantially guarantee that their qualities conform to the SLAs [50] because SLAs only provide traditional recourse, rather than timely alerts of impending SLA violations [52]. At runtime, anomalies, e.g.…”
Section: Related Workmentioning
confidence: 99%
“…In this SLA compliance monitor, three web service monitoring services, namely Measurement Service, Condition Evaluation Service and Deployment Service, are implemented for the purposes of metric definitions, metric update receipts and WSLA document decomposition respectively. The authors of [52] propose a two-level monitoring system named ReqMon. In ReqMon, each web service site contains at least one monitor server and there is a global integrative monitor that controls individual monitors.…”
Section: Related Workmentioning
confidence: 99%
“…There has been a lot of work done both in web service monitoring (Robinson, 2003;Birman et al, 2004;G. Canfora et al, 2005) and in adding fault tolerant to existing systems (L. Moser et al, 1999;Natarajan et al, 2000), but they are not specifically addressing fault tolerance in BPEL processes.…”
Section: Related Workmentioning
confidence: 99%
“…In order to create coarse grained business processes that constitute a number of related business functions, a high-level work flow language such as BPEL (Weerawarana and Curbera, 2002) is often used. However, due to the autonomous nature of the Web services, it is difficult for a third party user to ensure and check that a Web service will fulfill its requirements (functional or non-functional) (Robinson, 2003;Menasc, 2002). Consequently, the inherent openness of the interactions among Web services leaves BPEL processes susceptible to the failures of their constituent services.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation