2009 International Symposium on Information Engineering and Electronic Commerce 2009
DOI: 10.1109/ieec.2009.139
|View full text |Cite
|
Sign up to set email alerts
|

A Novel SOA-Oriented Federate SLA Management Architecture

Abstract: The theory of Service Oriented Architecture (SOA) provides an idea to achieve application integration and on-demand services provision. But at the same time, its loose coupling structure brings great challenges to achieve effective service management. This paper analyzes the characteristics of SOA service deployment structure, and then proposes a novel SOA-oriented federate SLA management architecture. In this architecture, Service Level Agreement (SLA) can be flexibly defined and reused, and its corresponding… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2012
2012
2013
2013

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 10 publications
0
3
0
Order By: Relevance
“…Metrics to measure granularity, complexity and reuse [15,35,36], performance [5,13] and QoS [28,31] of SOAbased services also rely on design-time data. Most work on operation and optimization has been done on how to handle service level agreements primarily based on design-time data: how to formally describe them [19,34,39,40], technically implement, test and enforce them [4,10,15,17,18,23,25,26,32,33,42,44,45] or how to monitor them [2,20,21]. Contributions available on SLA design deal with isolated approaches: Sauvé et al [38] and Marques et al [27] are in favor of deriving the service level targets directly from the business impact of the given service (i.e.…”
Section: Related Workmentioning
confidence: 99%
“…Metrics to measure granularity, complexity and reuse [15,35,36], performance [5,13] and QoS [28,31] of SOAbased services also rely on design-time data. Most work on operation and optimization has been done on how to handle service level agreements primarily based on design-time data: how to formally describe them [19,34,39,40], technically implement, test and enforce them [4,10,15,17,18,23,25,26,32,33,42,44,45] or how to monitor them [2,20,21]. Contributions available on SLA design deal with isolated approaches: Sauvé et al [38] and Marques et al [27] are in favor of deriving the service level targets directly from the business impact of the given service (i.e.…”
Section: Related Workmentioning
confidence: 99%
“…All the values of these inputs will be represented either 1 (exist) or 0 (not exist).One or two hidden layers to test the effect of increasing the hidden layers upon the performance of the architecture. The output layer consist either one neuron if we want to calculate trace of immeasurable matrix or one neuron represents the activated output for immeasurable part in ANNSLA model [12].…”
Section: Annsla Matlab Architecturementioning
confidence: 99%
“…SLA is a negotiated basic agreement between two parties (Service Provide and Consumer) which is designed to create a common understanding about the services, the priorities, responsibilities, etc Service Provider uses SLA to provide Service with a certain level of Quality and to charge customer - [4]. requester of discovering and binding services to act more fast and thoroughly, and help service provider to compose and offer services more effectively in service providing a chain [5].…”
Section: Extended Service Oriented Architecturementioning
confidence: 99%