Web Service Level Agreements

The main point is to create a new level for the grid, cloud or SOA middleware, capable of creating a trading mechanism between service providers and consumers. For example, the EU-funded Framework SLA@SOI 7 research project[12]explores aspects of multi-level, multi-supplier slas within service-based infrastructure and cloud computing, while another EU-funded project, VISION Cloud[13], has delivered results in terms of content-based ALS. Most service providers provide statistics, often through an online portal. There, customers can check whether ALS is being met and whether they are entitled to service credits or other penalties under ALS. If the service provider is taken over by another entity or merges with another entity, the client can expect his ALS to remain in effect, but that may not be the case. The agreement may need to be renegotiated. Don`t make assumptions; Note, however, that the new owner does not want to alienate existing customers, so they can choose to honor existing SLAs. The ALS should contain not only a description of the services to be provided and their expected levels of service, but also metrics to measure the services, obligations and responsibilities of each party, corrective measures or penalties in the event of a breach, and a protocol for adding and removing measures. We describe a new framework for defining and tracking service level agreements (ALS) for web services.

Monitoring and implementation of ALS is increasingly important in a web environment where applications and business services depend on services that are dynamically and responsively subscribed. For economic and practical reasons, we want an automated deployment process for both the service itself and the SLA management system, which measures and controls QoS parameters, verifies agreed service levels and reports violations to authorized parties involved in the ALS management process. Our approach to these issues is presented in this paper. The WSLA (Web Service Level Agreement) framework aims to define and monitor ALS for web services. Although WSLA was designed for a web service environment, it also applies to all multi-domain management scenarios. B to managing business processes and services or managing networks, systems and applications in general. The WSLA framework consists of a flexible and expandable language, based on an XML scheme, and an execution architecture consisting of several SLA monitoring services that can be outsourced to third parties to ensure maximum objectivity. WSLA allows service customers and providers to clearly define a large number of ALSs, identify ALS parameters and their measurement, and link them to managed resource tools. After receiving an SLA specification, WSLA monitoring services are automatically configured to force ALS. The implementation of the WSLA framework, called the SLA Compliance Monitor, is available to the public as part of IBM Web Services` toolkit.

The service received by the customer as a result of the service provided is at the heart of the service level agreement. Measures should be designed so that bad conduct is not rewarded by both parties. If z.B. a service level is violated because the customer does not provide information on time, the provider should not be penalized. G. Dreo Rodosek and L. Lewis, Dynamic Service Provisioning: a user-oriented approach. A O. Festor and A. Pras, eds.

Review of the 12th annual IFIP/IEEE International Workshop on Distributed Systems: Operations and Management (DSOM 2001), IFIP/IEEE, INRIA Press, Nancy, France, p. 37-48, October 2001. Availability of service: the time available for use.