Understanding SOA with Web Services (Independent Technology Guides Series) / Edition 1by Eric Newcomer, Greg Lomow, Greg A. Lomow
Pub. Date: 12/28/2004
Praise for Understanding SOA with Web Services
"This book does the best job of describing not only "where we are" in the timeline of enterprise integration efforts, but also providing strategic guidance for where we need to be. The authors have worked diligently to break down the integration problem into functional areas, and send/b>/i>
Praise for Understanding SOA with Web Services
"This book does the best job of describing not only "where we are" in the timeline of enterprise integration efforts, but also providing strategic guidance for where we need to be. The authors have worked diligently to break down the integration problem into functional areas, and send you down the path of strategic integration utilizing XML Web Services and Service-Oriented Architecture as the vehicle of choice. You will love this book!"
Daniel Edgar, Architect, Portland General Electric
"E-Government needs a comprehensive guide to SOA with Web Services standards and best practices for implementation to get from the current "as is" to the future "to be" architecture. This book meets that need superbly."
Brand Niemann, Ph.D., Co-Chair, Semantic (Web Services) Interoperability Community of Practice, U.S. Federal CIO Council.
"There are many books on SOA available today, but Understanding SOA with Web Services stands out from the pack because of its thorough, outstanding coverage of transactions, reliability, and process. Where most SOA books focus on integration and architecture basics, Lomow and Newcomer fearlessly dive into these more advanced, yet critical, topics, and provide a depth of treatment unavailable anywhere else."
Jason Bloomberg, Senior Analyst, ZapThink LLC
"This book provides a wealth of content on Web Services and SOA not found elsewhere. Although the book is technical in nature, it is surprisingly easy to read and digest. Managers who would like to keep up with the most effective technical strategies will find this book required reading."
Hari Mailvaganam, University of British Columbia, Vancouver
"I have been teaching companies and lecturing on SOA and XML Web Services for years and sort of felt at home with these technologies. I didn't think anyone else could teach me anything more significant about either of them. This book surprised me. If a person teaching SOA and Web Services can learn something from this book, you can too. This book is a must-read for all architects, senior developers, and concerned CTOs."
Sayed Y. Hashimi, SOA Consultant
"Newcomer and Lomow are no doubt the industry luminaries on the topics of Web Services, Service-Oriented Architecture, and integration. This book is sure to be a must-have for developers and architects looking to take advantage of the coming wave of standards-based, loosely coupled integration."
Ronald Schmelzer, Senior Analyst, ZapThink, LLC
Author of XML and Web Services Unleashed (Sams, 2002)
"The author makes it quite clear: SOA is an organizational principle and Web Service technology is a means to realize enterprise solutions according to this. SOA is the federative concept of nature and efficient societies. The book is an excellent starting-point to discover the new world of an IT-infrastructure adjusted to efficient business strategies and processes in a global value-add network."
Johann Wagner, Senior Architect, Siemens Business Services Author of Föderative Unternehmensprozesse
"Finally, here's a third-generation Web services book that delivers pragmatic solutions using SOAs. Newcomer and Lomow draw from their years of real-world experience ranging from developing Web services standards to hands-on applications. Listen to them."
DOUG KAYE, author of Loosely Coupled: The Missing Pieces of Web Services
Host and producer, IT Conversations (www.itconversations.com)
The definitive guide to using Service-Oriented Architecture (SOA) and Web services technologies to simplify IT infrastructure and improve business agility. Renowned experts Eric Newcomer and Greg Lomow offer practical strategies and proven best practices for every facet of SOA planning and implementation. Newcomer and Lomow pick up where Newcomer's widely read Understanding Web Services left off, showing how to fully leverage today's latest Web services standards for metadata management, security, reliable messaging, transactions, and orchestration.
Along the way, they present specific approaches and solutions for a wide range of enterprise integration and development challenges, including the largest and most complex.
- Why SOA has emerged as the dominant approach to enterprise integration
- How and why Web services provide the ideal foundation for SOA
- Underlying concepts shared by all SOAs: governance, service contracts, Web services platforms, service-oriented development, and more
- Implementing service-level communications, discovery, security, data handling, transaction management, and system management
- Using SOA to deliver application interoperability, multichannel client access, and business process management
- Practical tutorials on WS-Security, WS-Reliable Messaging, WS-AtomicTransactions, WS-Composite Application Framework, WS-Addressing, WS-Policy, and WS-BPEL
Whether you're an architect, developer, or IT manager, Understanding SOA with Web Services will help you get SOA rightand achieve both the business and technical goals you've set for it.
Table of Contents
About the Authors.
What's in the Book.
Organization of the Book.
1. Introduction to SOA with Web Services.
The Service-Oriented Enterprise.
What Are Services?
What Is Service-Oriented Architecture?
Challenges to Adoption.
SOA and Web Services.
Occasionally Connected Computing.
Business Process Management.
Extended Web Services Specifications.
Reliability and Messaging.
I. SOA AND BUSINESS PROCESS MANAGEMENT CONCEPTS.
2. Overview of Service-Oriented Architecture.
Service-Oriented Business and Government.
Service-Oriented Architecture Concepts.
SOA Processes, Principles, and Tools.
Line of Business Services.
Reusable Technical Services.
Web Services Platform.
Service Requesters and Service Providers.
Approved Products, Technologies, and Facilities.
Service Governance, Processes, Guidelines, Principles, Methods, and Tools.
SOA Governance Policies and Processes.
SOA Principles and Guidelines.
Key Service Characteristics.
SOA Guidelines for Service Requesters.
SOA Guidelines for Legacy Systems and Legacy Services.
Technical Benefits of a Service-Oriented Architecture.
Service-Oriented Architecture-Business Benefits.
Increased Business Agility.
Better Business Alignment.
Improved Customer Satisfaction.
Reduced Vendor Lock-In and Reduced Switching Costs.
Reduced Integration Costs.
Improved ROI of Existing IT Assets.
3. SOA and Web Services.
The Web Services Platform.
Elements of the Web Services Platform.
Web Services Platform Principles.
Service Contract Elements.
Documenting and Defining Service Contracts.
Service Contract Principles.
Service Contracts Focus on Service-Level Abstractions.
WSDL and Service Contracts.
WSDL Service Contract Architecture.
Example WSDL Service Contract-Calendar Service.
Service-Level Data Model.
Relationship Between Service-Level Data Models and Internal Data Models.
Reconciling Disparate Data Models Across Different Service Domains.
Using XML-Related Technologies for the Service-Level Data Model and Data Handling.
Service Discovery-Registration and Lookup.
Service-Level Interaction Patterns.
A Quick Look at SOAP and HTTP.
Request/Callback Interaction Paradigm.
Asynchronous Store-and-Forward Messaging.
Example Business Scenario Using Request/Response and Asynchronous Messaging
Publish/Subscribe Interaction Paradigm.
Atomic Services and Composite Services.
Generating Proxies and Skeletons from Service Contracts.
Generating Java Classes from Service Contracts.
Generating C# Classes from Service Contracts.
Generating C++ Classes from Service Contracts.
Service-Level Communication and Alternative Transports.
SOAP over IBM WebSphere MQ.
SOAP over JMS.
SOAP over CORBA IIOP.
SOAP over Tibco Rendezvous.
A Retrospective on Service-Oriented Architectures.
Overview of Selected Technologies That Have Been Used to Implement SOAs.
Detailed Comparison of SOA Technologies.
4. SOA and Web Services for Integration.
Overview of Integration.
Common Business Drivers for Integration.
Common Technical Challenges Faced During Integration.
Requirements That the "Ideal" Integration Solution Must Satisfy.
Integration Can Be Performed at Different Layers of the Technology Stack.
Integration and Interoperability Using XML and Web Services.
Two Approaches for Using XML and Web Services for Integration and Interoperability.
Web Services Integration (WSI).
Service-Oriented Integration (SOI).
Applying SOA and Web Services for Integration-.NET and J2EE Interoperability.
Applying SOA and Web Services for Integration-Service-Enabling Legacy Systems.
Example #1-CICS and IMS.
Applying SOA and Web Services for Integration-Enterprise Service Bus Pattern.
Summary-SOA and Web Services for Integration.
5. SOA and Multi-Channel Access.
Business Benefits of SOA and Multi-Channel Access.
Multi-Channel Access Reduces Staffing Costs.
Multi-Channel Access Eliminates Obsolete and Expensive Infrastructure.
Service-Oriented Architecture Reduces Costs and Improves Efficiency.
A Service-Oriented Architecture for Multi-Channel Access.
Architecture for Multi-Channel Access.
Channel Access Tier.
Business Service Access Tier.
Business Service Tier.
Example-SOA for Developing Composite Applications.
Example-SOA for Multi-Channel Access Architecture.
6. SOA and Business Process Management.
Basic Business Process Management Concepts.
Business Process Management Systems.
Business Activity Monitoring.
Example Business Process.
Combining BPM, SOA, and Web Services.
Benefits of BPM, SOA, and Web Services.
Defining Atomic and Composite Services.
Orchestration and Choreography Specifications.
Comparing Web Services Orchestration and Choreography.
Choreography Description Language.
Example of Web Services Composition.
Comparing Orchestration-Centric and Choreography-Centric Approaches.
Part I Summary: Benefits of Combining BPM, SOA, and Web Services.
Individual Features and Benefits of BPM, SOA, Web Services, and XML.
Complementary Features and Benefits of BPM, SOA, and Web Services.
II. EXTENDED WEB SERVICES SPECIFICATIONS.
7. Metadata Management.
The Simple Approach to Metadata Management.
Using Plain SOAP and WSDL.
Web Services Policy Language (WSPL).
WSDL 2.0 Features and Properties.
Comparing the Policy Specifications.
8. Web Services Security.
Summary of Challenges, Threats, and Remedies.
Person in the Middle Attacks.
Securing the Communications Layer.
IP Layer Security.
The WS-Security Framework.
Security Assertion Markup Language (SAML).
XACML: Communicating Policy Information.
XML Key Management Specification (XKMS).
9. Advanced Messaging.
Concepts and Technologies.
Benefits of Reliable Messaging.
Usage Scenarios for Reliable Messaging.
Web Services Reliable Messaging Specifications.
Comparing Web Services Reliable Messaging and Asynchronous Message Queuing.
Mobile Workers and Occasionally Connected Computing.
10. Transaction Processing.
The Transaction Paradigm.
Impact of Web Services on Transactions.
Protocols and Coordination.
The Web Services Coordinator.
Orchestration Historical References.
and post it to your social network
Most Helpful Customer Reviews
See all customer reviews >
Reading this book left me overwhelmed with the acronymic promiscuity resplendent in this field. The authors describe SOA in conjunction with XML, Web Services and a whole slew of Web Services subsets, like WS-Transactions, WS-Trust, WSDL and WS-BPEL. At some point, this jargon acts as a conceptual barrier to newcomers. The book strives to overcome this, and does a creditable job. But it still can be confusing. Perhaps the key note is how the book's subject differs from other topics, like Web Services or BPM. Much detail is given about this. There is one simplifying point. Do you come from a Java or C# background? If so, then you are familiar with interfaces. And how if you are coding a large project, good practice is to have major classes implement interfaces. So that one class does not call another directly, but instead uses an instantiation of an interface. This leads to a more modular and robust design. By analogy, this carries over well into SOA, in the context of Web Services. Of course, you should be aware of the limitations of pushing the analogy too far. As the book shows, SOA is for distributed systems. Which is more complicated that running one Java program on one computer. Still, you can migrate a design attitude. But once you realise the analogy, a lot of the book's complexity can be pushed to a lower level of detail.