---

Web Services Platform Architecture(c) SOAP, WSDL, WS-Policy, WS-Addressing, WS-BP[. .. ] More

ISBN: N/A
EAN: N/A

Year: 2005
Pages: 176

BUY ON AMAZON

• Web Services Platform Architecture: SOAP, WSDL, WS-Policy, WS-Addressing, WS-BPEL, WS-Reliable Messaging, and More
• Table of Contents
• Copyright
• Praise for Web Services Platform Architecture
• Foreword by Steve Mills
• Foreword by Ronald Schmelzer
• Preface
• Who Should Read this Book?
• Acknowledgments
• About the Authors
• Part 1: Introduction
• Chapter 1. Service-Oriented Architectures
• Section 1.1. Virtual Enterprises
• Section 1.2. The Need for Loose Coupling
• Section 1.3. What Is a Service?
• Section 1.4. Service-Oriented Architecture
• Section 1.5. Summary
• Chapter 2. Background
• Section 2.1. XML
• Section 2.2. World Wide Web
• Section 2.3. Summary
• Chapter 3. Web Services: A Realization of SOA
• Section 3.1. Scope of the Architecture
• Section 3.2. Transport Services
• Section 3.3. Messaging Services
• Section 3.4. Service Description
• Section 3.5. Discovery Services
• Section 3.6. Quality of Service
• Section 3.7. Service Components
• Section 3.8. Composeability
• Section 3.9. Interoperability
• Section 3.10. REST
• Section 3.11. Scope of Applicability of SOA and Web Service
• Section 3.12. Summary
• Part 2: Messaging Framework
• Chapter 4. SOAP
• Section 4.1. A Brief History of SOAP
• Section 4.2. Architectural Concepts
• Section 4.3. SOAP Attachments
• Section 4.4. Differences Between SOAP 1.1 and 1.2
• Section 4.5. Summary
• Chapter 5. Web Services Addressing
• Section 5.1. Addressing Web Services
• Section 5.2. Architectural Concepts
• Section 5.3. Example
• Section 5.4. Future Directions
• Section 5.5. Summary
• Part 3: Describing Metadata
• Chapter 6. Web Services Description Language (WSDL)
• Section 6.1. Role of WSDL in WS-SOA
• Section 6.2. History
• Section 6.3. Architectural Concepts
• Section 6.4. WSDL 1.1
• Section 6.5. WSDL v2.0
• Section 6.6. Future Directions
• Section 6.7. Summary
• Chapter 7. Web Services Policy
• Section 7.1. Motivation for WS-Policy
• Section 7.2. Architectural Concepts
• Section 7.3. Future Directions
• Section 7.4. Summary
• Part 4: Discovering Metadata
• Chapter 8. Universal Description, Discovery, and Integration (UDDI)
• Section 8.1. Role of UDDI in SOA and the WS Stack
• Section 8.2. Motivation for UDDI
• Section 8.3. Architectural Concepts
• Section 8.4. Future Directions
• Section 8.5. Summary
• Chapter 9. Web Services Metadata Exchange
• Section 9.1. Architectural Concepts
• Section 9.2. Future Directions
• Section 9.3. Summary
• Part 5: Reliable Interaction
• Chapter 10. Reliable Messaging
• Section 10.1. Motivation for Reliable Messaging
• Section 10.2. Reliable Messaging Scenarios
• Section 10.3. Architectural Concepts
• Section 10.4. Processing Model
• Section 10.5. Strengths and Weaknesses
• Section 10.6. Examples
• Section 10.7. Future Directions
• Section 10.8. Summary
• Chapter 11. Transactions
• Section 11.1. Role of Transactions in Web ServicesSOA
• Section 11.2. Motivation for Transactions
• Section 11.3. Architectural Concepts
• Section 11.4. Example
• Section 11.5. Summary
• Part 6: Security
• Chapter 12. Security
• Section 12.1. A Motivating Example: Travel Agent Web Services
• Section 12.2. Roles of Security in Web Services
• Section 12.3. Motivation for Using WS-Security
• Section 12.4. End-to-End Security When Intermediaries Are Present
• Section 12.5. Federating Multiple Security Domains
• Section 12.6. A Brief History
• Section 12.7. Architectural Concepts
• Section 12.8. Processing Model
• Section 12.9. Putting the Pieces Together
• Section 12.10. Interoperability
• Section 12.11. Future Directions
• Section 12.12. Summary
• Chapter 13. Advanced Security
• Section 13.1. WS-Trust
• Section 13.2. WS-SecureConversation
• Section 13.3. WS-Privacy
• Section 13.4. WS-Federation
• Section 13.5. WS-Authorization
• Section 13.6. Web Services Authorization Model
• Section 13.7. Security and Policy
• Section 13.8. Assertion Model
• Section 13.9. Other Security Topics
• Section 13.10. Non-Repudiation
• Section 13.11. Summary
• Part 7: Service Composition
• Chapter 14. Modeling Business Processes: BPEL
• Section 14.1. Motivation for BPEL
• Section 14.2. Architectural Concepts
• Section 14.3. BPEL Processing Model
• Section 14.4. Future Directions
• Section 14.5. Summary
• Part 8: Case Studies
• Chapter 15. Case Study: Car Parts Supply Chain
• Section 15.1. Scenario Description
• Section 15.2. Architecture
• Section 15.3. Web Service Descriptions
• Section 15.4. Messages and Protocols
• Section 15.5. Summary
• Chapter 16. Case Study: Ordering Service Packs
• Section 16.1. Scenario Description
• Section 16.2. Architecture
• Section 16.3. Web Service Descriptions
• Section 16.4. Messages and Protocols
• Section 16.5. Summary
• Part 9: Conclusion
• Chapter 17. Futures
• Section 17.1. Semantics
• Section 17.2. Wiring
• Section 17.3. Ordering Constraints
• Section 17.4. Contracting
• Section 17.5. Summary
• Chapter 18. Conclusion
• Section 18.1. A Summary of the Web Services Platform
• Section 18.2. Standardization
• Section 18.3. Competing Specifications
• Section 18.4. Perspectives
• Section 18.5. Building on the Core Platform
• Section 18.6. Summary
• Appendix AReferences
• Index
• A
• B
• C
• D
• E
• F
• G
• H
• I
• J
• K
• L
• M
• N
• O
• P
• Q
• R
• S
• T
• U
• V
• W
• X
• Z