Home > Store

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

Register your product to gain access to bonus material or receive a coupon.

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


  • Sorry, this book is no longer in print.
Not for Sale


  • Copyright 2005
  • Dimensions: 7" x 9-1/4"
  • Pages: 456
  • Edition: 1st
  • Book
  • ISBN-10: 0-13-148874-0
  • ISBN-13: 978-0-13-148874-8

"Other books claim to present the complete Web services platform architecture, but this is the first one I've seen that really does. The authors have been intimately involved in the creation of the architecture. Who better to write this book?"

—Anne Thomas Manes, Vice President and Research Director, Burton Group

"This is a very important book, providing a lot of technical detail and background that very few (if any) other books will be able to provide. The list of authors includes some of the top experts in the various specifications covered, and they have done an excellent job explaining the background motivation for and pertinent details of each specification. The benefit of their perspectives and collective expertise alone make the book worth reading."

—Eric Newcomer, CTO, IONA Technologies

"Most Web services books barely cover the basics, but this book informs practitioners of the "real-world" Web services aspects that they need to know to build real applications. The authors are well-known technical leaders in the Web services community and they helped write the Web services specifications covered in this book. Anyone who wants to do serious Web services development should read this book."

—Steve Vinoski, Chief Engineer, Product Innovation, IONA Technologies

"There aren't many books that are as ambitious as this one is. The most notable distinguishing factor of this book is that the authors have tried to pair down the specifications for the user and rather than focusing on competing specifications, they focus on complementary ones. Nearly every chapter provides a business justification and need for each feature discussed in the Web services stack. I would recommend this book to developers, integrators, and architects."

—Daniel Edgar, Systems Architect, Portland General Electric

"Rarely does a project arrive with such a list of qualified and talented authors. The subject matter is timely and significant to the industry. "

—Eric Newcomer, author of Understanding SOA with Web Services and Understanding Web Services and Chief Technology officer, IONA

The Insider's Guide to Building Breakthrough Services with Today'sNew Web Services Platform

Using today's new Web services platform, you can build services that are secure, reliable, efficient at handling transactions, and well suited to your evolving service-oriented architecture. What's more, you can do all that without compromising the simplicity or interoperability that made Web services so attractive. Now, for the first time, the experts who helped define and architect this platform show you exactly how to make the most of it.

Unlike other books, Web Services Platform Architecture covers the entire platform. The authors illuminate every specification that's ready for practical use, covering messaging, metadata, security, discovery, quality of service, business-process modeling, and more. Drawing on realistic examples and case studies, they present a powerfully coherent view of how all these specifications fit together—and how to combine them to solve real-world problems.

  • Service orientation: Clarifying the business and technical value propositions

  • Web services messaging framework: Using SOAP and WS-Addressing to deliver Web services messages

  • WSDL: Documenting messages and supporting diverse message interactions

  • WS-Policy: Building services that specify their requirements and capabilities, and how to interface with them

  • UDDI: Aggregating metadata and making it easily available

  • WS-MetadataExchange: Bootstrapping efficient, customized communication between Web services

  • WS-Reliable Messaging: Ensuring message delivery across unreliable networks

  • Transactions: Defining reliable interactions with WS-Coordination, WS-AtomicTransaction, and WS-BusinessActivity

  • Security: Understanding the roles of WS-Security, WS-Trust, WS-SecureConversation, and WS-Federation

  • BPEL: Modeling and executing business processes as service compositions

Web Services Platform Architecture gives you an insider's view of the platform that will change the way you deliver applications. Whether you're an architect, developer, technical manager, or consultant, you'll find it indispensable.

Sanjiva Weerawarana, research staff member for the component systems group at IBM Research, helps define and coordinate IBM's Web services technical strategy and activities. A member of the Apache Software Foundation, he contributed to many specifications including the SOAP 1.1 and WSDL 1.1 specifications and built their first implementations. Francisco Curbera, IBM research staff member and component systems group manager, coauthored BPEL4WS, WS-Addressing, and other specifications. He represents IBM on the BPEL and Web Services Addressing working groups. Frank Leymann directs the Institute of Architecture of Application Systems at the University of Stuttgart. As an IBM distinguished engineer, he helped architect IBM's middleware stack and define IBM's On Demand Computing strategy. IBM Fellow Tony Storey has helped lead the development of many of IBM's middleware, Web services, and grid computing products. IBM Fellow Donald F. Ferguson is chief architect and technical lead for IBM Software Group, and chairs IBM's SWG Architecture Board.

© Copyright Pearson Education. All rights reserved.

Sample Content

Online Sample Chapter

Web Services: A Realization of SOA

Downloadable Sample Chapter

Untitled Document Download the Sample Chapter related to this title.

Table of Contents

Foreword by Steve Mills.

Foreword by Ronald Schmelzer.



About the Authors.


1. Service-Oriented Architectures.

    Virtual Enterprises.

      Business Process Optimization.

      Collaborations, Mergers, and Acquisitions.

      Resource Sharing.

     The Need for Loose Coupling.

      Issues with Current Distributed System Technologies.

      Advantages of Message-Oriented Middleware.

      Future Proofing.

    What Is a Service?

      Evolution of Major Software Granules.

      The Software Version of a Service.

    Service-Oriented Architecture.


      Framework for SOA.


2. Background.


      XML Basics.

      DTDs, XML Schema, and RelaxNG.

      XML Namespaces.

    World Wide Web.





3. Web Services: A Realization of SOA.

    Scope of the Architecture.

    Transport Services.

    Messaging Services.



    Service Description.



    Discovery Services.


      MetaData Exchange.

    Quality of Service.


      Reliable Messaging.


    Service Components.

      Composition of Web Services.





       “Representational” in REST.

       “State Transfer” in REST.

      REST Interface Structure.

       REST and Web Services.

    Scope of Applicability of SOA and Web Service.



4. SOAP.

    A Brief History of SOAP.

    Architectural Concepts.

      Defining Some Terms.

      The SOAP Processing Model.

      SOAP Roles.

      SOAP Faults.

      Documents and RPC.

      Message Exchange Patterns.

      SOAP Bindings.

    SOAP Attachments.

    Differences Between SOAP 1.1 and 1.2.


5. Web Services Addressing.

    Addressing Web Services.

    Architectural Concepts.

      Endpoint References.

      Comparing Endpoints.

      Message Information Headers.

      Binding Endpoint References to SOAP Messages.

      Request-Reply Pattern in WS-Addressing.


    Future Directions.



6. Web Services Description Language (WSDL).

    Role of WSDL in WS-*/SOA.


    Architectural Concepts.


      Support for Multiple Type Systems.

      Unifying Messaging and RPC.

      Separation of “What” from “How” and “Where”.

      Support for Multiple Protocols and Transports.

      No Ordering.

      No Semantics.

    WSDL 1.1.

      Language Structure.

      Best Practices.

      Problems and Limitations.

    WSDL v2.0.

      Overall Language Structure.

      Interface Extensions.

      Elimination of <message>.

      Message Exchange Patterns.


      Features and Properties.

    Future Directions.


7. Web Services Policy.

    Motivation for WS-Policy.

    Architectural Concepts.

      Policy Framework.

      Attaching Policies to Web Services.

    Future Directions.



8. Universal Description, Discovery, and Integration (UDDI).

    Role of UDDI in SOA and the WS Stack.

      Use of UDDI During Design and Development.

      Use of UDDI at Runtime.

    Motivation for UDDI.

    Architectural Concepts.

      UDDI V3 Data Model.

      UDDI and WSDL.

      UDDI and WS-Policy.

      UDDI V3 Architecture and APIs.

      New Features in UDDI V3.

    Future Directions.

      Standardization of Taxonomy Language.

      Semantic Searching.

      Instance-Based Security.


9. Web Services Metadata Exchange.

    Architectural Concepts.

      Extensibility of Metadata Dialects.

      Use of Indirection: Metadata References and Locations.

      Metadata Request Operations.

      Default Protocol Binding.

    Future Directions.



10. Reliable Messaging.

    Motivation for Reliable Messaging.

      The Network Is Reliable.

      Latency Is Zero.

      There Is One Administrator.

    Reliable Messaging Scenarios.

      Store and Forward.

      Batch Window.

      Failure Recovery.

      Long-Running Transactions.

    Architectural Concepts.

    Processing Model.

      Sequence Lifecycle.

      Basic Syntax.

      Sequence Element.

      SequenceAcknowledgement Element.

      AckRequested Element.

      SequenceFault Element.

      Delivery Semantics Supported.

      Policy Assertions.

      Inactivity Timeout.

      Retransmission Interval.

      Acknowledgement Interval.

      Basic WS-Reliable Messaging Profile.

    Strengths and Weaknesses.


    Future Directions.


11. Transactions.

    Role of Transactions in Web Services/SOA.

    Motivation for Transactions.

      Classic Transactions.

      Business Transactions.

    Architectural Concepts.

      Definition of Transaction Architectural Terms.

      Services and Protocols.


      Travel Agent Scenario Using Atomic Transaction.

      Travel Agent Scenario Using Business Activity.



12. Security.

    A Motivating Example: Travel Agent Web Services.

    Roles of Security in Web Services.

    Motivation for Using WS-Security.

    End-to-End Security When Intermediaries Are Present.

    Federating Multiple Security Domains.

    A Brief History.

    Architectural Concepts.

    Processing Model.

      XML Signature.

      XML Encryption.

    Putting the Pieces Together.

      The Basic Model.

      Model with Intermediary.

      Trust Relationships.


      Basic Security Profile.

    Future Directions.


13. Advanced Security.








    Web Services Authorization Model.

    Security and Policy.

    Assertion Model.

    Other Security Topics.

      Public-Key Cryptography.


      Data Integrity and Data-Origin Authentication.

      Proof of Message Origin.

      Proof of Message Receipt.

      Delivery of Proof of Message Receipt.



14. Modeling Business Processes: BPEL.

    Motivation for BPEL.

      A Brief History.

    Architectural Concepts.

      Overview of the Process Composition Model.

      Abstract and Executable Processes.

      Recursive, Type-Based Composition.

      Process Instance Lifecycle.

      Event Handling.

      Dealing with Exceptional Behavior.

      Extensibility and the Role of Web Services Policies.

    BPEL Processing Model.


      Interacting with the Process.

      Navigating the Process Model.

      Scopes and Handlers.

    Future Directions.



15. Case Study: Car Parts Supply Chain.

    Scenario Description.


    Web Service Descriptions.

    Messages and Protocols.


16. Case Study: Ordering Service Packs.

    Scenario Description.


    Web Service Descriptions.

    Messages and Protocols.



17. Futures.



    Ordering Constraints.



18. Conclusion.

    A Summary of the Web Services Platform.


      Concerns About the Standardization Process.

    Competing Specifications.


      Why Will It Succeed?


    Building on the Core Platform.





Untitled Document

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


Untitled Document Download the Foreword file related to this title.


Untitled Document Download the Index file related to this title.


Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020