Service-Oriented Computing (Information Systems)
Format: PDF / Kindle (mobi) / ePub
Service-Oriented Computing (SOC) promises a world of cooperating services loosely connected, creating dynamic business processes and agile applications that span organizations and platforms. As a computing paradigm, it utilizes services as fundamental elements to support rapid, low-cost development of distributed applications in heterogeneous environments. Realizing the SOC promise requires the design of Service-Oriented Architectures (SOAs) that enable the development of simpler and cheaper distributed applications. In this collection, researchers from academia and industry report on recent advances in the field, exploring approaches, technology, and research issues related to developing SOAs. SOA enables service discovery, integration, and use, allowing application developers to overcome many distributed enterprise computing challenges. The contributors to this volume treat topics related to SOA and such proposed enhancements to it as Event Drive Architecture (EDA) and extended SOA (xSOA) as well as engineering aspects of SOA-based applications. In particular, the chapters discuss modeling of SOA-based applications, SOA architecture design, business process management, transactional integrity, quality of service (QoS) and service agreements, service requirements engineering, reuse, and adaptation. Contributors L. Bahler, Boualem Benatallah, Christoph Bussler, F. Caruso, Fabio Casati, C. Chung, Emilia Cimpian, B. Falchuk, Dimitrios Georgakopoulos, Jaap Gordijn, Paul Grefen, Jonas Grundler, Woralak Kongdenfha, Yutu Liu, Mark Little, Heiko Ludwig, J. Micallef, Thomas Mikalsen, Adrian Mocan, Anne HH Ngu, Bart Orriens, Savas Parastatidis, Michael Papazoglou, Barbara Pernici, Pierluigi Plebani, Isabelle Rouvellou, Quan Z. Sheng, Halvard Skogsrud, Stefan Tai, Farouk Toumani, Pascal van Eck, Jim Webber, Roel Wieringa, Jian Yang, Liangzhao Zeng, Olaf Zimmermann
(WS-Security). http://www.oasis-open.org/committees/wss.  R. Bilorusets et al. Web Services Reliable Messaging (WS-ReliableMessaging). 2004. http://msdn.microsoft.com/ webservices/understanding/specs/default.aspx?pull=/library/en-us/dnglobspec/html/ws-reliablemessaging.asp.  OASIS. Web Services Reliable Messaging (WS-Reliability). http://www.oasis-open.org/committees/wsrm.  L. F. Cabrera et al. Web Services Atomic Transaction (WS-AtomicTransaction). 2008.
information it needs about the service at runtime. The service interfaces are discovered dynamically, and messages are constructed dynamically. The service consumer does not know the format of the request message, or the location of the service, until it needs the service. Overview of Service-Oriented Computing 9 Service contracts and other associated metadata (e.g., about policies and agreements ), lay the groundwork for enterprise SOAs that involve many clients operating with a complex,
build and maintain the service abstraction for client applications . To achieve less coupling between services and their clients, EDA requires event producers and consumers to be fully decoupled . That is, event producers need no speciﬁc knowledge of event consumers, and vice versa. Therefore, there is no need for a service contract (e.g., a WSDL speciﬁcation) that explicates the behavior of a service to the client. The only relationship between event consumers and producers is through the
analyzes the general aspects of the mediator systems in an attempt to provide an abstract view of a mediator. More details about the required functionality and the architectural elements are presented in followings sections. One of the most important issues of mediator systems is the involvement of the human expert in the mediation process. Even if the techniques for identifying, extracting, and making the semantics of both data and processes available to algorithms are becoming more effective,1
The requirements for this component are the following: 1. Scalability The number of clients that might need to use the services of a mediation system, as well as the number of heterogeneous data sources that need to be mediated, are continuously growing. The mediation system must be designed to be scalable in both these directions. 2. Flexibility The effort needed for adapting the mediation system to the changes that may appear in the structure of the ontologies must be minimal. 3. Correctness