did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

We're the #1 textbook rental company. Let us show you why.

9780131488748

Web Services Platform Architecture SOAP, WSDL, WS-Policy, WS-Addressing, WS-BPEL, WS-Reliable Messaging, and More

by ; ; ; ;
  • ISBN13:

    9780131488748

  • ISBN10:

    0131488740

  • Edition: 1st
  • Format: Paperback
  • Copyright: 2005-03-22
  • Publisher: PEARSO
  • Purchase Benefits
List Price: $64.99

Summary

A comprehensive introduction to the Web services platform, written by the technical leaders who designed the architecture for IBM.

Author Biography

Donald E. Ferguson is chief architect and technical lead for IBM Software Group, and chairs IBM's SWG Architecture Board.

Table of Contents

Foreword by Steve Mills xxi
Foreword by Ronald Schmelzer xxiii
Preface xxix
Acknowledgments xxxi
About the Authors xxxiii
PART 1 INTRODUCTION 1(60)
1 Service-Oriented Architectures
3(20)
1.1 Virtual Enterprises
4(5)
1.1.1 Business Process Optimization
4(2)
1.1.2 Collaborations, Mergers, and Acquisitions
6(2)
1.1.3 Resource Sharing
8(1)
1.2 The Need for Loose Coupling
9(4)
1.2.1 Issues with Current Distributed System Technologies
9(1)
1.2.2 Advantages of Message-Oriented Middleware
10(2)
1.2.3 Future Proofing
12(1)
1.3 What Is a Service?
13(4)
1.3.1 Evolution of Major Software Granules
14(1)
1.3.2 The Software Version of a Service
15(2)
1.4 Service-Oriented Architecture
17(5)
1.4.1 Bind/Publish/Find
18(3)
1.4.2 Framework for SOA
21(1)
1.5 Summary
22(1)
2 Background
23(8)
2.1 XML
23(5)
2.1.1 XML Basics
23(2)
2.1.2 DTDs, XML Schema, and RelaxNG
25(1)
2.1.3 XML Namespaces
26(2)
2.2 World Wide Web
28(2)
2.2.1 URIs
28(1)
2.2.2 HTTP
29(1)
2.2.3 MIME
29(1)
2.3 Summary
30(1)
3 Web Services: A Realization of SOA
31(30)
3.1 Scope of the Architecture
33(3)
3.2 Transport Services
36(1)
3.3 Messaging Services
36(4)
3.3.1 SOAP
37(2)
3.3.2 WS-Addressing
39(1)
3.4 Service Description
40(2)
3.4.1 WSDL
40(1)
3.4.2 Policy
41(1)
3.5 Discovery Services
42(2)
3.5.1 UDDI
42(1)
3.5.2 MetaData Exchange
43(1)
3.6 Quality of Service
44(5)
3.6.1 WS-Security
45(1)
3.6.2 Reliable Messaging
46(1)
3.6.3 Transactions
47(2)
3.7 Service Components
49(1)
3.7.1 Composition of Web Services
50(1)
3.8 Composeability
50(2)
3.9 Interoperability
52(2)
3.9.1 WS-I
53(1)
3.10 REST
54(3)
3.10.1 "Representational" in REST
55(1)
3.10.2 "State Transfer" in REST
55(1)
3.10.3 REST Interface Structure
55(1)
3.10.4 REST and Web Services
56(1)
3.11 Scope of Applicability of SOA and Web Service
57(2)
3.12 Summary
59(2)
PART 2 MESSAGING FRAMEWORK 61(42)
4 SOAP
63(24)
4.1 A Brief History of SOAP
64(1)
4.2 Architectural Concepts
64(17)
4.2.1 Defining Some Terms
64(2)
4.2.2 The SOAP Processing Model
66(2)
4.2.3 SOAP Roles
68(5)
4.2.4 SOAP Faults
73(2)
4.2.5 Documents and RPC
75(1)
4.2.6 Message Exchange Patterns
75(3)
4.2.7 SOAP Bindings
78(3)
4.3 SOAP Attachments
81(3)
4.4 Differences Between SOAP 1.1 and 1.2
84(1)
4.5 Summary
85(2)
5 Web Services Addressing
87(16)
5.1 Addressing Web Services
88(2)
5.2 Architectural Concepts
90(10)
5.2.1 Endpoint References
90(2)
5.2.2 Comparing Endpoints
92(1)
5.2.3 Message Information Headers
93(3)
5.2.4 Binding Endpoint References to SOAP Messages
96(1)
5.2.5 Request-Reply Pattern in WS-Addressing
97(3)
5.3 Example
100(2)
5.4 Future Directions
102(1)
5.5 Summary
102(1)
PART 3 DESCRIBING METADATA 103(40)
6 Web Services Description Language (WSDL)
105(22)
6.1 Role of WSDL in WS-*/SOA
106(1)
6.2 History
107(1)
6.3 Architectural Concepts
108(3)
6.3.1 Extensibility
108(1)
6.3.2 Support for Multiple Type Systems
109(1)
6.3.3 Unifying Messaging and RPC
109(1)
6.3.4 Separation of "What" from "How" and "Where"
110(1)
6.3.5 Support for Multiple Protocols and Transports
110(1)
6.3.6 No Ordering
111(1)
6.3.7 No Semantics
111(1)
6.4 WSDL 1.1
111(11)
6.4.1 Language Structure
112(8)
6.4.2 Best Practices
120(1)
6.4.3 Problems and Limitations
121(1)
6.5 WSDL v2.0
122(4)
6.5.1 Overall Language Structure
122(1)
6.5.2 Interface Extensions
123(1)
6.5.3 Elimination of [message] 123
6.5.4 Message Exchange Patterns
124(1)
6.5.5 Services
125(1)
6.5.6 Features and Properties
125(1)
6.6 Future Directions
126(1)
6.7 Summary
126(1)
7 Web Services Policy
127(16)
7.1 Motivation for WS-Policy
128(2)
7.2 Architectural Concepts
130(10)
7.2.1 Policy Framework
131(6)
7.2.2 Attaching Policies to Web Services
137(3)
7.3 Future Directions
140(1)
7.4 Summary
141(2)
PART 4 DISCOVERING METADATA 143(42)
8 Universal Description, Discovery, and Integration (UDDI)
145(28)
8.1 Role of UDDI in SOA and the WS Stack
146(1)
8.1.1 Use of UDDI During Design and Development
146(1)
8.1.2 Use of UDDI at Runtime
147(1)
8.2 Motivation for UDDI
147(1)
8.3 Architectural Concepts
148(22)
8.3.1 UDDI V3 Data Model
148(4)
8.3.2 UDDI and WSDL
152(5)
8.3.3 UDDI and WS-Policy
157(1)
8.3.4 UDDI V3 Architecture and APIs
158(5)
8.3.5 New Features in UDDI V3
163(7)
8.4 Future Directions
170(1)
8.4.1 Standardization of Taxonomy Language
170(1)
8.4.2 Semantic Searching
170(1)
8.4.3 Instance-Based Security
170(1)
8.5 Summary
171(2)
9 Web Services Metadata Exchange
173(12)
9.1 Architectural Concepts
175(7)
9.1.1 Extensibility of Metadata Dialects
175(1)
9.1.2 Use of Indirection: Metadata References and Locations
176(1)
9.1.3 Metadata Request Operations
177(4)
9.1.4 Default Protocol Binding
181(1)
9.2 Future Directions
182(1)
9.3 Summary
183(2)
PART 5 RELIABLE INTERACTION 185(76)
10 Reliable Messaging
187(30)
10.1 Motivation for Reliable Messaging
188(3)
10.1.1 The Network Is Reliable
189(1)
10.1.2 Latency Is Zero
190(1)
10.1.3 There Is One Administrator
190(1)
10.2 Reliable Messaging Scenarios
191(2)
10.2.1 Store and Forward
191(1)
10.2.2 Batch Window
191(1)
10.2.3 Failure Recovery
192(1)
10.2.4 Long-Running Transactions
192(1)
10.3 Architectural Concepts
193(1)
10.4 Processing Model
194(13)
10.4.1 Sequence Lifecycle
196(2)
10.4.2 Basic Syntax
198(1)
10.4.3 Sequence Element
199(1)
10.4.4 SequenceAcknowledgement Element
200(2)
10.4.5 AckRequested Element
202(1)
10.4.6 SequenceFault Element
203(1)
10.4.7 Delivery Semantics Supported
204(1)
10.4.8 Policy Assertions
205(1)
10.4.9 Inactivity Timeout
205(1)
10.4.10 Retransmission Interval
205(1)
10.4.11 Acknowledgement Interval
206(1)
10.4.12 Basic WS-Reliable Messaging Profile
206(1)
10.5 Strengths and Weaknesses
207(1)
10.6 Examples
208(6)
10.7 Future Directions
214(1)
10.8 Summary
215(2)
11 Transactions
217(44)
11.1 Role of Transactions in Web Services/SOA
218(2)
11.2 Motivation for Transactions
220(8)
11.2.1 Classic Transactions
220(4)
11.2.2 Business Transactions
224(4)
11.3 Architectural Concepts
228(20)
11.3.1 Definition of Transaction Architectural Terms
228(2)
11.3.2 Services and Protocols
230(18)
11.4 Example
248(11)
11.4.1 Travel Agent Scenario Using Atomic Transaction
248(4)
11.4.2 Travel Agent Scenario Using Business Activity
252(7)
11.5 Summary
259(2)
PART 6 SECURITY 261(50)
12 Security
263(26)
12.1 A Motivating Example: Travel Agent Web Services
265(2)
12.2 Roles of Security in Web Services
267(1)
12.3 Motivation for Using WS-Security
268(2)
12.4 End-to-End Security When Intermediaries Are Present
270(2)
12.5 Federating Multiple Security Domains
272(1)
12.6 A Brief History
273(1)
12.7 Architectural Concepts
273(3)
12.8 Processing Model
276(3)
12.8.1 XML Signature
277(1)
12.8.2 XML Encryption
278(1)
12.9 Putting the Pieces Together
279(6)
12.9.1 The Basic Model
279(3)
12.9.2 Model with Intermediary
282(1)
12.9.3 Trust Relationships
283(2)
12.10 Interoperability
285(2)
12.10.1 Basic Security Profile
285(2)
12.11 Future Directions
287(1)
12.12 Summary
288(1)
13 Advanced Security
289(22)
13.1 WS-Trust
290(4)
13.1.1 In-Band
294(1)
13.1.2 Out-of-Band
294(1)
13.2 WS-SecureConversation
294(1)
13.3 WS-Privacy
295(1)
13.4 WS-Federation
296(2)
13.5 WS-Authorization
298(1)
13.6 Web Services Authorization Model
299(2)
13.7 Security and Policy
301(1)
13.8 Assertion Model
301(2)
13.9 Other Security Topics
303(1)
13.9.1 Public-Key Cryptography
303(1)
13.10 Non-Repudiation
304(5)
13.10.1 Data Integrity and Data-Origin Authentication
304(3)
13.10.2 Proof of Message Origin
307(1)
13.10.3 Proof of Message Receipt
308(1)
13.10.4 Delivery of Proof of Message Receipt
309(1)
13.11 Summary
309(2)
PART 7 SERVICE COMPOSITION 311(30)
14 Modeling Business Processes: BPEL
313(28)
14.1 Motivation for BPEL
315(2)
14.1.1 A Brief History
316(1)
14.2 Architectural Concepts
317(16)
14.2.1 Overview of the Process Composition Model
318(3)
14.2.2 Abstract and Executable Processes
321(1)
14.2.3 Recursive, Type-Based Composition
322(5)
14.2.4 Process Instance Lifecycle
327(3)
14.2.5 Event Handling
330(1)
14.2.6 Dealing with Exceptional Behavior
330(2)
14.2.7 Extensibility and the Role of Web Services Policies
332(1)
14.3 BPEL Processing Model
333(6)
14.3.1 Deployment
333(1)
14.3.2 Interacting with the Process
334(1)
14.3.3 Navigating the Process Model
335(2)
14.3.4 Scopes and Handlers
337(2)
14.4 Future Directions
339(1)
14.5 Summary
340(1)
PART 8 CASE STUDIES 341(30)
15 Case Study: Car Parts Supply Chain
343(16)
15.1 Scenario Description
343(1)
15.2 Architecture
344(4)
15.3 Web Service Descriptions
348(4)
15.4 Messages and Protocols
352(5)
15.5 Summary
357(2)
16 Case Study: Ordering Service Packs
359(12)
16.1 Scenario Description
359(1)
16.2 Architecture
360(2)
16.3 Web Service Descriptions
362(4)
16.4 Messages and Protocols
366(3)
16.5 Summary
369(2)
PART 9 CONCLUSION 371(22)
17 Futures
373(8)
17.1 Semantics
373(2)
17.2 Wiring
375(3)
17.3 Ordering Constraints
378(1)
17.4 Contracting
379(1)
17.5 Summary
380(1)
18 Conclusion
381(12)
18.1 A Summary of the Web Services Platform
381(2)
18.2 Standardization
383(2)
18.2.1 Concerns About the Standardization Process
384(1)
18.3 Competing Specifications
385(2)
18.4 Perspectives
387(2)
18.4.1 Why Will It Succeed?
387(1)
18.4.2 Risks
388(1)
18.5 Building on the Core Platform
389(3)
18.6 Summary
392(1)
References 393(6)
Index 399

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Excerpts

Preface Preface"Web services are a mess!""There are more than 150 Web services (WS-*) specs!""Simple? This stuff is more complicated than CORBA!""There is no architecture; just a bunch of competing specs!""These specs are denser than plutonium!"Those are some of the statements we've heard from people--including our own colleagues--about Web services. That's why we wrote this book: to show that the WS-* platform is not a random walk through a space of WS-* specifications but rather an organized, structured architecture with well-defined design and architectural objectives. We apply these objectives when working on WS-* specifications and when deciding whether or not we need a new specification in a certain area.The objective of this book is to present the cohesive, structured architecture of the Web services platform that we have been helping to define. The architecture is designed to enable loosely coupled interaction between services with business-quality reliability, security, and transactional capabilities. We start by presenting some of the business world-driving forces that are motivating the creation of the service-oriented computing platform (Chapter 1, "Service-Oriented Architectures"). Then we focus on Web services as a realization of this service-oriented computing platform and indicate which specifications contribute to the platform (Chapter 3, "Web Services"). After that, we consider each major part of the platform and offer the insight that went into defining the specifications that govern that component. We cover the messaging framework, describing metadata, reliable interaction, security, and service composition in different parts of the book. Before concluding, we consider two case studies to illustrate how the Web services platform can address both intranet and extranet integration scenarios. In the concluding part, we summarize the platform and give our perspectives on why the integrated architecture we present makes sense and will "win" the standards battle. Finally, we present our thoughts on the future of the Web services platform.At the end of this book, you should no longer feel that Web services has no architecture or that the architecture is hidden somewhere between 150+ WS-* specifications. You might not agree with our choice of components that comprise the architecture, but we chose the set based on the fact that those were designed from the ground up to work together to solve a single problem: that of being a ubiquitous platform for integrating heterogeneous systems to enable rich business communication. Who Should Read This Book?We wrote this book for technical professionals and students. Although Chapter 2, "Background," briefly introduces the requisite background material about major XML technologies, we assume that you have a fair grasp of those technologies coming into this book. Developers who want to understand the overall Web services platform will appreciate this book. However, this is not a "developer book" in the sense of providing detailed, code-level understanding. That was not our objective. Architects, consultants, and technically oriented management should find this book useful. Students who have already attended introductory courses in distributed systems or database systems will be able to understand the Web services platform. Copyright Pearson Education. All rights reserved.

Rewards Program