Uh-oh, it looks like your Internet Explorer is out of date.

For a better shopping experience, please upgrade now.

Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services / Edition 1

Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services / Edition 1

4.7 3
by Thomas Erl

ISBN-10: 0131428985

ISBN-13: 9780131428980

Pub. Date: 04/30/2004

Publisher: Prentice Hall

Web services is the integration technology preferred by organizations implementing service-oriented architectures. I would recommend that anybody involved in application development obtain a working knowledge of these technologies, and I'm pleased to recommend Erl's book as a great place to begin.

—Tom Glover, Senior Program Manager


Web services is the integration technology preferred by organizations implementing service-oriented architectures. I would recommend that anybody involved in application development obtain a working knowledge of these technologies, and I'm pleased to recommend Erl's book as a great place to begin.

—Tom Glover, Senior Program Manager, Web Services Standards, IBM Software Group, and Chairman of the Web Services Interoperability Organization (WS-I).

An excellent guide to building and integrating XML and Web services, providing pragmatic recommendations for applying these technologies effectively. The author tackles numerous integration challenges, identifying common mistakes and providing guidance needed to get it right the first time. A valuable resource for understanding and realizing the benefits of service-oriented architecture in the enterprise.

—David Keogh, Program Manager, Visual Studio Enterprise Tools, Microsoft.

Leading-edge IT organizations are currently exploring second generation web service technologies, but introductory material beyond technical specifications is sparse. Erl explains many of these emerging technologies in simple terms, elucidating the difficult concepts with appropriate examples, and demonstrates how they contribute to service-oriented architectures. I highly recommend this book to enterprise architects for their shelves.

—Kevin P. Davis, Ph. D., Software Architect.

Service-oriented integration with less cost and less risk

The emergence of key second-generation Web services standards has positioned service-oriented architecture (SOA) as the foremost platform for contemporary business automation solutions. The integration of SOA principles and technology is empowering organizations to build applications with unprecedented levels of flexibility, agility, and sophistication (while also allowing them to leverage existing legacy environments).

This guide will help you dramatically reduce the risk, complexity, and cost of integrating the many new concepts and technologies introduced by the SOA platform. It brings together the first comprehensive collection of field-proven strategies, guidelines, and best practices for making the transition toward the service-oriented enterprise.

Writing for architects, analysts, managers, and developers, Thomas Erl offers expert advice for making strategic decisions about both immediate and long-term integration issues. Erl addresses a broad spectrum of integration challenges, covering technical and design issues, as well as strategic planning.

  • Covers crucial second-generation (WS-*) Web services standards: BPEL4WS, WS-Security, WS-Coordination, WS-Transaction, WS-Policy, WS-ReliableMessaging, and WS-Attachments
  • Includes hundreds of individual integration strategies and more than 60 best practices for both XML and Web services technologies
  • Includes a complete tutorial on service-oriented design principles for business and technical modeling
  • Explores design issues related to a wide variety of service-oriented integration architectures that integrate XML and Web services into legacy and EAI environments
  • Provides a clear roadmap for planning a long-term migration toward a standardized service-oriented enterprise

Service-oriented architecture is no longer an exclusive discipline practiced only by expensive consultants. With this book's help, you can plan, architect, and implement your own service-oriented environments-efficiently and cost-effectively.

About the Web Sites

Erl's Service-Oriented Architecture books are supported by two Web sites. http:// www.soabooks.com provides a variety of content resources and http:// www.soaspecs.com supplies a descriptive portal to referenced specifications.

Product Details

Prentice Hall
Publication date:
Prentice Hall Service Technology Series from Thomas Erl Series
Product dimensions:
7.00(w) x 8.90(h) x 1.30(d)

Table of Contents


1. Introduction.

Why this guide is important. The XML & Web Services Integration Framework (XWIF). How this guide is organized. www.serviceoriented.ws. Contact the author.


2. Introduction to XML technologies.

Extensible Markup Language (XML). Document Type Definitions (DTD). XML Schema Definition Language (XSD). Extensible Stylesheet Language Transformations (XSLT). XML Query Language (XQuery). XML Path Language (XPath).

3. Introduction to Web services technologies.

Web services and the service-oriented architecture (SOA). Web Services Description Language (WSDL). Simple Object Access Protocol (SOAP). Universal Description, Discovery, and Integration (UDDI).

4. Introduction to second-generation (WS-*) Web services technologies.

Second-generation Web services and the service-oriented enterprise (SOE). WS-Coordination and WS-Transaction. Business Process Execution Language for Web Services (BPEL4WS). WS-Security and the Web services security specifications. WS-ReliableMessaging. WS-Policy. WS-Attachments.


5. Integrating XML into applications.

Strategies for integrating XML data representation. Strategies for integrating XML data validation. Strategies for integrating XML schema administration. Strategies for integrating XML transformation. Strategies for integrating XML data querying.

6. Integrating Web services into applications.

Service models. Modeling service-oriented component classes and Web service interfaces. Strategies for integrating service-oriented encapsulation. Strategies for integrating service assemblies. Strategies for enhancing service functionality. Strategies for integrating SOAP messaging.

7. Integrating XML and databases.

Comparing XML and relational databases. Integration architectures for XML and relational databases. Strategies for integrating XML with relational databases. Techniques for mapping XML to relational data. Database extensions. Native XML databases.


8. The mechanics of application integration.

Understanding application integration. Integration levels. A guide to middleware. Choosing an integration path.

9. Service-oriented architectures for legacy integration.

Service models for application integration. Fundamental integration components. Web services and one-way integration architectures. Web services and point-to-point architectures. Web services and centralized database architectures. Service-oriented analysis for legacy architectures.

10. Service-oriented architectures for enterprise integration.

Service models for enterprise integration architectures. Fundamental enterprise integration architecture components. Web services and enterprise integration architectures. Hub and spoke. Messaging bus. Enterprise Service Bus (ESB).

11. Service-oriented integration strategies.

Strategies for streamlining integration endpoint interfaces. Strategies for optimizing integration endpoint services. Strategies for integrating legacy architectures. Strategies for enterprise solution integration. Strategies for integrating Web services security.


12. Thirty best practices for integrating XML.

Best practices for planning XML migration projects. Best practices for knowledge management within XML projects. Best practices for standardizing XML applications. Best practices for designing XML applications.

13. Thirty best practices for integrating Web services.

Best practices for planning service-oriented projects. Best practices for standardizing Web services. Best practices for designing service-oriented environments. Best practices for managing service-oriented development projects. Best practices for implementing Web services.

14. Building the service-oriented enterprise (SOE).

SOA modeling basics. SOE building blocks. SOE migration strategy.

About the Author.

About the Photographs.


Customer Reviews

Average Review:

Post to your social network


Most Helpful Customer Reviews

See all customer reviews

Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services 4.7 out of 5 based on 0 ratings. 3 reviews.
Guest More than 1 year ago
This book is valuable resource for understanding and realizing the benefits of SOA and provides pragmatic recomendations for building and integrating XML and Web services effectively.
Guest More than 1 year ago
It's interesting how this book simplifies the complex topics and issues surrounding the incorporation of XML data and Web Service Endpoints into the common enterprise. It breaks down the topics into different levels of integration so you can find advice for approaching a task not based on what it is you're integrating but based on the scope of your integration. Of most value to us were the unique tips and recommendations that I have not yet seen anywhere else. I think this type of information is not yours tandard textbook-level how to content. It is knowledge passed along from experience.
Guest More than 1 year ago
There has been a tremendous buildout in Web Services standards over the last two years. Its description forms the bulk of this book. The book factors neatly into two parts, which are interspersed as different chapters. One part is the above. The other deals with XML. Consider the XML part first, because that is simpler, and Web Services build upon it. Even if you have no intention of using Web Services, this book has excellent advice on XML development. It assumes that you know about the syntax and parsing. So it doesn't waste any time going over that. Rather, it focuses on suggesting how to best implement/deploy it. Chapter 5 includes a nice analysis of the limitations of XML Schema and DTDs. Plus, there is something which lower level XML books often don't discuss. In those, XML examples are given using lengthy labels in tags, that have human-readable utility. Which is a strength of XML. But this comes at a cost of greater storage and processing time and bandwidth (when you transmit the XML). Given that XML is meant to be processed by software, and that humans should often only view it directly as a manual exception handling process, then having shorter tags might sometimes be acceptable, if you want to improve performance. This is something I've encountered in my own coding, when I write/read 100Mb XML files. The sheer size of these leads me to define tags with labels of just one or two characters. Which does make them harder to manually read. But my reading routines run faster. Erl also suggests that if you have personnel who want to learn XML, books may be far cheaper than training courses offered by third parties. Granted, this is a little self-serving, because he is saying this in his book. But no more so than asking some consulting company if you should hire them to teach XML. Now consider the Web Services part of the book. There has been a veritable laundry list of second generation technologies developed. Like Transaction, Coordination, Security, Policy, BPEL4WS, Attachment and Addressing. Erl tries to pull these together into a coherent usage framework. The book does not go into the details to each technology. That is the purview of other books. Rather, Erl discusses integrating these into your development. Helpfully, he points out that any specific application usually only needs a subset of the above. Which is vital in learning and using them in a modular fashion. Analogous to how in java, you don't have to know all the class libraries that come with the latest java, in order to usefully program. He offers another tip which alone may justify the entire book to you. If you asking a vendor for a full enterprise WS conversion of your legacy applications, she often gives a hub and spoke model. In this, the spokes are modifications of your applications, and the hub is written by the vendor. Typically, this gives a vendor lockin. So beware!