Wu Service Computing: Concept, Method and Technology

1. Auflage 2014
ISBN: 978-0-12-802597-0
Verlag: Elsevier Science & Techn.
Format: EPUB
Kopierschutz: 6 - ePub Watermark

E-Book, Englisch, 356 Seiten

Service computing is a cross-disciplinary field that covers science and technology, and represents a promising direction for distributed computing and software development methodologies. It aims to bridge the gap between business services and IT services by supporting the whole lifecycle of services innovation. Over the last ten years applications in industry and academic research have produced considerable progress and success Service Computing: Concept, Method and Technology presents the concept of service computing and a proposed reference architecture for service computing research before proceeding to introduce two underlying technologies: Web services and service-oriented architecture. It also presents the authors' latest research findings on hot topics such as service discovery, recommendation, composition, verification, service trust, dynamic configuration and big data service. Some new models and methods are proposed including three service discovery methods based on semantics and skyline technologies, two service recommendation methods using graph mining and QoS prediction, two service composition methods with graph planning and one service verification method using p calculus and so on. Moreover, this book introduces JTang, an underlying platform supporting service computing, which is a product of the authors' last ten years of research and development. - Systematically reviews all the research on service computing - Introduces state-of-art research works on service computing and provides a road map for future directions - Bridges the gap between service computing theory and practice - Provides guidance for both industry and academia

Department of Computer Science, Zhejiang University, Hangzhou, China

Autoren/Hrsg.

Wu, Zhaohui

Inhaltsverzeichnis

1;Front Cover;1
2;Service Computing;4
3;Copyright;5
4;Contents;6
5;Preface;12
6;Chapter 1 - Introduction;14
6.1;1.1 Overview;14
6.2;1.2 Technical Framework of Service Computing;18
6.3;1.3 The State-of-the-Art of Service Computing;23
6.4;1.4 Organization;27
6.5;References;27
7;Chapter 2 - Service-Oriented Architecture and Web Services;30
7.1;2.1 Web Services;31
7.2;2.2 Service-Oriented Architecture;45
7.3;2.3 Service Component Architecture;48
7.4;2.4 Service Data Objects;51
7.5;2.5 Open-Source Platforms for SOA;53
7.6;2.6 Summary;54
7.7;References;54
8;Chapter 3 - Web Service Quality of Service and Its Prediction;56
8.1;3.1 Introduction;56
8.2;3.2 Collaborative Filtering-Based Quality of Service Prediction;58
8.3;3.3 Matrix Factorization-Based Quality of Service Prediction;66
8.4;3.4 Summary;89
8.5;References;90
9;Chapter 4 - Service Discovery;92
9.1;4.1 Introduction;92
9.2;4.2 Related Work;94
9.3;4.3 Interface-Level Service Discovery;97
9.4;4.4 Behavior Level Service Discovery;106
9.5;4.5 Summary;116
9.6;References;117
10;Chapter 5 - Service Selection;118
10.1;5.1 Introduction;119
10.2;5.2 QoS-Based Skyline Service Selection;121
10.3;5.3 MapReduce and Skyline Service Selection;132
10.4;5.4 Summary;143
10.5;References;144
11;Chapter 6 - Service Recommendation;146
11.1;6.1 Overview of Service Recommendation;146
11.2;6.2 Bayes-Based Service Recommendation;148
11.3;6.3 Instant Service Recommendation;167
11.4;6.4 Summary;187
11.5;References;188
12;Chapter 7 - Service Composition;190
12.1;7.1 Introduction;191
12.2;7.2 Top-k QoS Composition;194
12.3;7.3 Parallel Optimization for Service Composition;210
12.4;7.4 Service Composition Based on Historical Records;219
12.5;7.5 Summary;238
12.6;References;239
13;Chapter 8 - Service Verification and Dynamic Reconfiguration;242
13.1;8.1 Introduction;243
13.2;8.2 Service Verification;246
13.3;8.3 The Dynamic Reconfiguration of a Service-Based Application;264
13.4;8.4 Summary;275
13.5;References;276
14;Chapter 9 - Complex Service Computing;280
14.1;9.1 Introduction;281
14.2;9.2 Service Computing with Big Data;284
14.3;9.3 Service Computing with a Complex Mobile Environment;296
14.4;9.4 Service Computing with Service Pattern Model;316
14.5;9.5 Summary;326
14.6;References;327
15;Chapter 10 - JTang Middleware Platform;330
15.1;10.1 Overview of JTang;330
15.2;10.2 Platform Architecture;331
15.3;10.3 JTang Development Environment for Service Components;336
15.4;10.4 JTang Distributed File Storage Service;339
15.5;10.5 JTang Enterprise Service Bus;344
15.6;10.6 JTang-Plus;348
15.7;10.7 Summary;349
16;Index;350

Leseproben

Chapter 2

Service-Oriented Architecture and Web Services

Abstract

Service-oriented architecture (SOA), a hot topic in software design and development, is independent of any vendor, product, or technology. Web services, which make functional building blocks accessible over standard Internet protocols, independent of platforms and programing languages, can implement a SOA. This chapter will first provide an overview of web services, SOA, service component architecture, and service data objects. Then some open-source platforms for SOA will be introduced.

Keywords

Servie component architecture; Service data objects; Service-oriented architecture; Web service

Chapter Outline

2.1 Web Services 18

2.1.1 Overview of Web Services 18

2.1.2 Basic Standards of Web Services 20

2.1.2.1 Simple Object Access Protocol 20

2.1.2.2 Web Service Description Language 22

2.1.2.3 Universal Description, Discovery and Integration 24

2.1.3 Web Services Security 26

2.1.3.1 WS-Security 27

2.1.3.2 WS-Policy 28

2.1.3.3 WS-Trust 29

2.1.4 Web Services Transaction 30

2.1.4.1 WS-Coordination 30

2.1.4.2 WS-AtomicTransaction 30

2.1.4.3 WS-BusinessActivity 31

2.1.5 Semantic Web Services 31

2.1.5.1 OWL-S 31

2.1.5.2 Web Service Modeling Ontology 31

2.1.5.3 Semantic Web Service Ontology 32

2.1.5.4 WSDL-S 32

2.2 Service-Oriented Architecture 32

2.2.1 Overview of SOA 32

2.2.2 Model of SOA 33

2.2.2.1 Service 34

2.2.2.2 Visibility 34

2.2.2.3 Service description 34

2.2.2.4 Interaction 34

2.2.2.5 Real-world effects 34

2.2.2.6 Contract and policy 34

2.2.2.7 Execution context 35

2.3 Service Component Architecture 35

2.3.1 Concepts of SCA 35

2.3.2 Model of SCA 35

2.3.2.1 Property 36

2.3.2.2 Reference 36

2.3.2.3 Service 37

2.3.2.4 Wire 37

2.3.3 Strategy Framework 38

2.4 Service Data Objects 38

2.4.1 Concepts of Service Data Object 38

2.4.2 Framework of Service Data Object 39

2.5 Open-Source Platforms for SOA 40

2.5.1 Apache Tuscany 40

2.5.2 Eclipse SOA Tools Project 40

2.6 Summary 41

References 41

2.1. Web Services

2.1.1. Overview of Web Services

A web service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other web-related standards. [1]

A web service is a concrete manifestation and function carrier of the concept of service computing. It is a kind of application, based on a web environment, that is adaptive, self-describing, and modular and has good interoperability. However, different organizations for the web service concept and its connotation may create different understanding and awareness.

IBM believes that a web service should use XML to describe a group of messaging through XML for its operation, but these operations can be accessed via the network and still meet the target task. The description of the service provides all the details of what is necessary to interact with the service, including message formats, transport protocols, and location.

Microsoft thinks that a web service is an application logic unit providing data and services to other applications. The application accesses the web service by the ubiquitous web service protocols and data formats, such as HTTP, XML, and Simple Object Access Protocol (SOAP), and it does not need to care about how to implement each web service.

SUN thinks that a web service is a software component that has the features of being discoverable, reusable, and re-combinable, solving the problems or requirements of users.

W3C thinks that a web service is a system supporting interoperability interaction through the network. It uses the Web Services Description Language (WSDL) to describe the service interface and uses the SOAP message based on HTTP protocol to implement the implementation between the service and the service and customer communication.

Each view above emphasizes some parts of a web service, and there are no conflicts. By combining the above views, we think that the biggest characteristics of a web service lies in its interoperability and reusability. The interoperability makes the web service become a kind of attractive adhesive, used for seamless integration of heterogeneous applications and systems; and the feature of reuse makes the web service a good carrier to convert a software to service. Compared with other software entities, a web service has the following features:

• Can be described: A web service can be described by a service description language.

• Can be released: A web service can be registered in the registering center and released.

• Can be found: The user can send a search request to a registering center to find the service and the access information.

• Can be bound: The web service description information can be bound with a runable service instance or service proxy.

• Can be called: A web service can be called by remote code with the description information.

• Can be composited: The web services can be composited together to a large granularity service.

In recent years, web service technology went through a long development period and formed the web service protocol stack as shown in Figure 2.1, with service communication, service description, service quality, and service processes. We can divide the development process into two parts: the web service foundation protocol developing period and the web service high-level protocol developing period. The first period completed the foundation protocols, such as SOAP [2], Web Service Description Language (WSDL) [3], and Universal Description, Discovery and Integration (UDDI) [4]. In this period, the majority of the research in technology was about service developing, testing, calling, and other basic problems. The second period completed the high-level protocols, such as Business Process Execution Language (BPEL) [5], Web Service Choreography Language (WS-CDL) [6], and Web Service Choreography Interface (WSCI) [7]. The technologies were about service interaction and cooperation. Now we are in the second period, and the service composition, service process management, service interaction, and service adoption are the hot topics. The concept of web service totally satisfies the definitions in service-oriented computing (SOC) and service-oriented architecture (SOA). Web service technology is thought to be the best for supporting SOC and SOA.

Figure 2.1 Web service protocol stack.

2.1.2. Basic Standards of Web Services

With the development of standards and protocols, web service computing has stepped into the mature period. The basic standards include SOAP, WSDL, and UDDI.

2.1.2.1. Simple Object Access Protocol

SOAP is a light protocol used in the distribution environment to exchange information, which was published by W3C in 1999. SOAP 1.0 is based totally on the HTTP protocol, while SOAP 1.1 published in May 2000 supports several different transport protocols. The latest version is SOAP 1.2, which was published in July 2001 by W3C.

SOAP is a no-state single-direction message exchange protocol, containing the following four aspects:

1. Defining a format used for single-direction message exchange, it describes how to organize the information into an XML document.

2. Describing how to transfer the SOAP message, it uses many different carriers, such as the web (using HTTP protocol) and e-mail (using simple mail transfer protocol).

3. Defining a group of rules compiled within the process of an operating SOAP message and the classification of related entities; it can assign a particular receiver and can handle strategies when the messages cannot be parsed.

4. Defining a group contract about Remote Procedure Call Protocol (RPC) calling and SOAP message exchanging, it solves the problem about how to encapsulate the RPC calling into the SOAP message, re-encapsulate the SOAP message to RPC, calling back to the server and returning the final result in the same strategy to the client.

The main design purpose is simple and extendable. To implement these two destinations, the core message framework of SOAP does not include some of the normal features found in other distribute systems, e.g., reliability, security, and Message Exchange Patterns (MEPs).

A SOAP message consists of a SOAP envelope, encoding rules, RPC representation, and a SOAP binding.

1. SOAP envelope: SOAP protocol is based on message exchange. Each message can be thought of as an envelope with some data...