book

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

by Sanjiva Weerawarana, Francisco Curbera, Frank Leymann, Tony Storey, Donald F. Ferguson

March 2005

Intermediate to advanced

456 pages

9h 29m

English

Pearson

Read now

Unlock full access

Dedication
Who Should Read this Book?
1.1. Virtual Enterprises1.1.1. Business Process Optimization1.1.2. Collaborations, Mergers, and Acquisitions1.1.3. Resource Sharing1.2. The Need for Loose Coupling1.2.1. Issues with Current Distributed System TechnologiesFragility of Object SystemsLack of Interoperability1.2.2. Advantages of Message-Oriented MiddlewareAdapters and ChannelsInteraction Patterns1.2.3. Future ProofingTechnology AbstractionProvider Abstraction1.3. What Is a Service?1.3.1. Evolution of Major Software GranulesFunctions and PackagesObjects and ClassesComponents1.3.2. The Software Version of a ServiceCharacteristics of a ServiceSolutions—Composition of Services1.4. Service-Oriented Architecture1.4.1. Bind/Publish/Find1.4.2. Framework for SOA1.5. Summary
2.1. XML2.1.1. XML Basics2.1.2. DTDs, XML Schema, and RelaxNGDTDsXML SchemaRelaxNG2.1.3. XML NamespacesXML InfosetDOM, SAX, and So OnXPath2.2. World Wide Web2.2.1. URIs2.2.2. HTTP2.2.3. MIME2.3. Summary

3.1. Scope of the Architecture3.2. Transport Services3.3. Messaging Services3.3.1. SOAP3.3.2. WS-Addressing3.4. Service Description3.4.1. WSDL3.4.2. Policy3.5. Discovery Services3.5.1. UDDI3.5.2. MetaData Exchange3.6. Quality of Service3.6.1. WS-Security3.6.2. Reliable Messaging3.6.3. Transactions3.7. Service Components3.7.1. Composition of Web Services3.8. Composeability3.9. Interoperability3.9.1. WS-I3.10. REST3.10.1. “Representational” in REST3.10.2. “State Transfer” in REST3.10.3. REST Interface Structure3.10.4. REST and Web Services3.11. Scope of Applicability of SOA and Web Service3.12. Summary
4.1. A Brief History of SOAP4.2. Architectural Concepts4.2.1. Defining Some Terms4.2.2. The SOAP Processing Model4.2.3. SOAP RolesEnforcing SOAP Roles—The “mustUnderstand” AttributePassing Headers—The “relay” Attribute4.2.4. SOAP Faults4.2.5. Documents and RPC4.2.6. Message Exchange PatternsRequest/Response MEPLong-Running Conversational MEP4.2.7. SOAP BindingsSOAP and HTTPSOAP and WebSphereMQ4.3. SOAP Attachments4.4. Differences Between SOAP 1.1 and 1.24.5. Summary
5.1. Addressing Web Services5.2. Architectural Concepts5.2.1. Endpoint References5.2.2. Comparing Endpoints5.2.3. Message Information Headers5.2.4. Binding Endpoint References to SOAP Messages5.2.5. Request-Reply Pattern in WS-AddressingRequest MessageReply Message5.3. Example5.4. Future Directions5.5. Summary
6.1. Role of WSDL in WS-*/SOA6.2. History6.3. Architectural Concepts6.3.1. Extensibility6.3.2. Support for Multiple Type Systems6.3.3. Unifying Messaging and RPC6.3.4. Separation of “What” from “How” and “Where”6.3.5. Support for Multiple Protocols and Transports6.3.6. No Ordering6.3.7. No Semantics6.4. WSDL 1.16.4.1. Language StructureDefinitionsTypesMessagesPortTypesBindingsSOAP BindingHTTP & MIME BindingServices6.4.2. Best Practices6.4.3. Problems and Limitations6.4.3.1. Messages6.4.3.2 . SOAP Binding6.4.3.3 . Services6.5. WSDL v2.06.5.1. Overall Language Structure6.5.2. Interface Extensions6.5.3. Elimination of <message>6.5.4. Message Exchange Patterns6.5.5. Services6.5.6. Features and Properties6.6. Future Directions6.7. Summary
7.1. Motivation for WS-Policy7.2. Architectural Concepts7.2.1. Policy FrameworkThe Policy ContainerPolicy OperatorsExactlyOne OperatorAll Operator“Optional” OperatorPolicy VocabularyPolicy Identification and InclusionPolicy Intersection7.2.2. Attaching Policies to Web Services7.3. Future Directions7.4. Summary
8.1. Role of UDDI in SOA and the WS Stack8.1.1. Use of UDDI During Design and Development8.1.2. Use of UDDI at Runtime8.2. Motivation for UDDI8.3. Architectural Concepts8.3.1. UDDI V3 Data ModelCategorizationbusinessEntitybusinessServicebindingTemplatetModelpublisherAssertion8.3.2. UDDI and WSDLMapping of WSDL portType ElementMapping of WSDL Binding ElementMapping of WSDL Service ElementMapping of WSDL Port ElementUDDI and WSDL at Development TimeUDDI and WSDL at Runtime8.3.3. UDDI and WS-PolicyReferencing Remote Policy Expressions DirectlyReferencing Remote Policy Expressions IndirectlyQuerying UDDI Using Policy Expressions8.3.4. UDDI V3 Architecture and APIsClient to Node OperationsNode to Client OperationsNode to Node OperationsNode to Taxonomy Server Operations8.3.5. New Features in UDDI V3Publisher-Assigned KeysSupport for Digital SignaturesUDDI PolicySubscription APICategorization EnhancementsChanges in Authentication8.4. Future Directions8.4.1. Standardization of Taxonomy Language8.4.2. Semantic Searching8.4.3. Instance-Based Security8.5. Summary
9.1. Architectural Concepts9.1.1. Extensibility of Metadata DialectsDialects and Identifiers9.1.2. Use of Indirection: Metadata References and Locations9.1.3. Metadata Request OperationsGetMetadata RequestsGetMetadata ResponsesGet RequestMetadata Exchange Example9.1.4. Default Protocol Binding9.2. Future Directions9.3. Summary
10.1. Motivation for Reliable Messaging10.1.1. The Network Is Reliable10.1.2. Latency Is Zero10.1.3. There Is One Administrator10.2. Reliable Messaging Scenarios10.2.1. Store and Forward10.2.2. Batch Window10.2.3. Failure Recovery10.2.4. Long-Running Transactions10.3. Architectural Concepts10.4. Processing Model10.4.1. Sequence Lifecycle10.4.2. Basic Syntax10.4.3. Sequence Element10.4.4. SequenceAcknowledgement Element10.4.5. AckRequested Element10.4.6. SequenceFault Element10.4.7. Delivery Semantics Supported10.4.8. Policy Assertions10.4.9. Inactivity Timeout10.4.10. Retransmission Interval10.4.11. Acknowledgement Interval10.4.12. Basic WS-Reliable Messaging Profile10.5. Strengths and Weaknesses10.6. Examples10.7. Future Directions10.8. Summary
11.1. Role of Transactions in Web Services/SOA11.2. Motivation for Transactions11.2.1. Classic Transactions11.2.2. Business Transactions11.3. Architectural Concepts11.3.1. Definition of Transaction Architectural TermsCoordinationProtocols for Atomic Transactions (WS-Atomic Transaction)Protocols for Business Transactions (WS-BusinessActivity)11.3.2. Services and ProtocolsWS-Coordination ServiceContextActivation ServiceRegistration ServiceTransaction ProtocolsWS-Atomic TransactionCompletion ProtocolDurable Two-Phase Commit ProtocolVolatile Two-Phase Commit ProtocolWS-Business ActivityBusiness Agreement with Participant CompletionBusiness Agreement with Coordinator CompletionGeneral Considerations11.4. Example11.4.1. Travel Agent Scenario Using Atomic TransactionActivationApplication Calls Web ServiceRegistrationCompletion/Coordination11.4.2. Travel Agent Scenario Using Business ActivityActivationApplication Calls Web ServiceRegistrationWeb Service CompletionCoordination11.5. Summary
12.1. A Motivating Example: Travel Agent Web Services12.2. Roles of Security in Web Services12.3. Motivation for Using WS-Security12.4. End-to-End Security When Intermediaries Are Present12.5. Federating Multiple Security Domains12.6. A Brief History12.7. Architectural Concepts12.8. Processing Model12.8.1. XML Signature12.8.2. XML Encryption12.9. Putting the Pieces Together12.9.1. The Basic Model12.9.2. Model with Intermediary12.9.3. Trust Relationships12.10. Interoperability12.10.1. Basic Security Profile12.11. Future Directions12.12. Summary
13.1. WS-Trust13.1.1. In-Band13.1.2. Out-of-Band13.2. WS-SecureConversation13.3. WS-Privacy13.4. WS-Federation13.5. WS-Authorization13.6. Web Services Authorization Model13.7. Security and Policy13.8. Assertion Model13.9. Other Security Topics13.9.1. Public-Key Cryptography13.10. Non-Repudiation13.10.1. Data Integrity and Data-Origin Authentication13.10.2. Proof of Message Origin13.10.3. Proof of Message Receipt13.10.4. Delivery of Proof of Message Receipt13.11. Summary
14.1. Motivation for BPEL14.1.1. A Brief History14.2. Architectural Concepts14.2.1. Overview of the Process Composition Model14.2.2. Abstract and Executable Processes14.2.3. Recursive, Type-Based CompositionComposing ServicesBinding to Concrete Endpoints of Partner ServicesA Conversational ApproachProcess Views14.2.4. Process Instance LifecycleCorrelation14.2.5. Event Handling14.2.6. Dealing with Exceptional BehaviorFault HandlingCompensationCompensation and Business Agreement Protocols14.2.7. Extensibility and the Role of Web Services Policies14.3. BPEL Processing Model14.3.1. Deployment14.3.2. Interacting with the Process14.3.3. Navigating the Process ModelDead Path Elimination14.3.4. Scopes and HandlersFault Handling and Compensation14.4. Future Directions14.5. Summary
15.1. Scenario Description15.2. Architecture15.3. Web Service Descriptions15.4. Messages and Protocols15.5. Summary
16.1. Scenario Description16.2. Architecture16.3. Web Service Descriptions16.4. Messages and Protocols16.5. Summary
17.1. Semantics17.2. Wiring17.3. Ordering Constraints17.4. Contracting17.5. Summary
18.1. A Summary of the Web Services Platform18.2. Standardization18.2.1. Concerns About the Standardization Process18.3. Competing Specifications18.4. Perspectives18.4.1. Why Will It Succeed?18.4.2. Risks18.5. Building on the Core Platform18.6. Summary

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

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 ...