BN.com Gift Guide

Understanding SOA with Web Services (Independent Technology Guides Series) / Edition 1

Paperback (Print)
Buy Used
Buy Used from BN.com
$32.35
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 96%)
Other sellers (Paperback)
  • All (22) from $1.99   
  • New (4) from $3.29   
  • Used (18) from $1.99   

Overview

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.

Coverage includes

  • 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 right—and achieve both the business and technical goals you've set for it.

Read More Show Less

Product Details

  • ISBN-13: 9780321180865
  • Publisher: Addison-Wesley
  • Publication date: 12/28/2004
  • Series: Independent Technology Guides Series
  • Edition description: New Edition
  • Edition number: 1
  • Pages: 444
  • Product dimensions: 7.00 (w) x 9.20 (h) x 0.90 (d)

Meet the Author

About the Authors

In the role of Chief Technology Officer at IONA, Eric Newcomer is responsible for IONA's technology roadmap and direction as relates to standards adoption, architecture, and product design. Eric joined IONA in November 1999 as transaction architect, and most recently served as Vice President of Engineering, Web Services Integration Products. Eric has 26 years experience in the computer industry, including more than 15 years at Digital Equipment Corporation/Compaq Computer, where he held a variety of technical and management positions before receiving a corporate-level technical appointment. Eric received his BA in American Studies from Antioch College, with a minor in computer science.

In addition to Understanding Web Services, published in 2002, Eric is co-author of Principles of Transaction Processing, published in 1997 by Morgan Kaufman, and co-author of a chapter called "The Keys to the Highway" in The Future of Software, published in 1995 by MIT Press. Eric is also the author of numerous white papers and articles, co-author and editor of the Structured Transaction Definition Language specification published by X/Open (now The Open Group) in 1994, former member of the Transaction Internet Protocol working group at IETF, former member of the X/Open Distributed Transaction Processing committee that created the XA specification, former chair of the OTS RTF at OMG, and chair of the team that developed the XML Valuetype specification at OMG to map XML to CORBA. He was a charter member of the XML Protocols Working Group at W3C, where he served as an editor of the requirements document that led to SOAP 1.2. He served for nearly two years as an editor of the W3C Web Services Architecture Specification, and most recently served as co-chair and editor of the Web Services Composite Application Framework set of specifications at OASIS.

Greg Lomow, Ph.D., is a senior manager and consultant for BearingPoint, Inc. Greg has 12 years of experience as a consultant and enterprise architect working in the financial services, telecom, and federal government sectors designing business applications using service-oriented architecture, developing simulation applications using distributed object technology, and training developers in object-oriented design and programming techniques. He also worked for eight years as a product manager at Jade Simulations, Level 8 Systems, and IONA Technologies responsible for integration, web services, and middleware products. Greg co-authored C++ Frequently Asked Questions published by Addison-Wesley in October 1999 (1st ed.) and again in January 1999 (2nd ed.). He completed his Ph.D. in computer science at the University of Calgary, Canada, in 1988. Greg is an active member of the Web Services Interoperability (WS-I) Organization.

Read More Show Less

Read an Excerpt

PrefacePreface

The widely adopted and implemented core Web services standards (SOAP and WSDL) have achieved unprecedented interoperability across highly disparate software systems. As a result, new Web services standards have been proposed for extended features such as security, reliability, transactions, metadata management, and orchestration that extend Web services for use in a broad range of new applications.

The service-oriented architecture (SOA) has also become widely recognized for its important role in information technology projects. An SOA is a style of design that guides an organization during all aspects of creating and using business services (including conception, modeling, design, development, deployment, management, versioning, and retirement).

Despite some limitations (which we document), an SOA with Web services is the ideal combination of architecture and technology for consistently delivering robust, reusable services that support today's business needs and that can be easily adapted to satisfy changing business requirements.

Think about an SOA as an assembly line in a factory. It's an investment in the future operation of your business, so a significant amount of planning, design, and development may have to go into it before it starts to really pay off. The first car off a production line is more expensive than the thousandth. Similarly, the first service deployed in an SOA is more expensive than the hundredth. The major benefits of SOA arrive over time, although as we will see, it is possible to start small and incrementally build up to a full-fledged SOA.

SOA with Web services is important because it aligns informationtechnology (IT) with business requirements and because it reduces the costs of IT systems and applications. An SOA gives you the ability to more easily integrate IT systems, provide multi-channel access to your systems, and to automate business processes.

Rather than relying entirely upon the skill and knowledge of certain specific individuals to implement business requirements in technology, SOA provides a foundation for rapidly assembling and composing new applications out of a library of reusable services that anyone can understand. When an SOA is in place and services are developed, developers can easily reuse existing services in their new applications and automated business processes.

Like any new investment in technology and infrastructure, it's important to understand the right way to do it and what you can and can't do. SOA and Web services are great, but they can't do everything. We hope that this book will help you achieve the benefits of SOA with Web services while avoiding the pitfalls.

© Copyright Pearson Education. All rights reserved.

Read More Show Less

Table of Contents

Preface.

Acknowledgments.

About the Authors.

Introduction.

What's in the Book.

Organization of the Book.

Part I.

Part II.

1. Introduction to SOA with Web Services.

The Service-Oriented Enterprise.

Service-Oriented Development.

Service Abstraction.

Service-Oriented Architecture.

What Are Services?

What Is Service-Oriented Architecture?

Challenges to Adoption.

SOA and Web Services.

Rapid Integration.

Multi-Channel Access.

Occasionally Connected Computing.

Business Process Management.

Extended Web Services Specifications.

Standardization.

Specification Composability.

Metadata Management.

Security.

Reliability and Messaging.

Transactions.

Orchestration.

Summary.

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.

Services.

Line of Business Services.

Reusable Technical Services.

Service Contracts.

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.

Primary Characteristics.

Secondary Characteristics.

SOA Guidelines for Service Requesters.

SOA Guidelines for Legacy Systems and Legacy Services.

Technical Benefits of a Service-Oriented Architecture.

Efficient Development.

More Reuse.

Simplified Maintenance.

Incremental Adoption.

Graceful Evolution.

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.

Summary.

3. SOA and Web Services.

The Web Services Platform.

Elements of the Web Services Platform.

Web Services Platform Principles.

Service Contracts.

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

Service-Level Interaction Patterns.

A Quick Look at SOAP and HTTP.

Request/Response Interactions.

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.

WSDL Extensibility.

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.

Summary.

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.

Example #2-CORBA.

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.

Architectural Challenges.

Architecture for Multi-Channel Access.

Client/Presentation Tier.

Channel Access Tier.

Communication Infrastructure.

Business Service Access Tier.

Business Service Tier.

Example-SOA for Developing Composite Applications.

Example-SOA for Multi-Channel Access Architecture.

Summary.

6. SOA and Business Process Management.

Basic Business Process Management Concepts.

Business Process Management Systems.

Process Modeling.

Process Execution.

Process Monitoring.

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.

WS-BPEL.

Choreography Description Language.

Example of Web Services Composition.

Orchestration-Centric Approach.

Choreography-Centric Approach.

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.

Metadata Specifications.

XML.

WSDL 2.0.

UDDI.

Addressing.

Policy.

WS-Policy.

Web Services Policy Language (WSPL).

WSDL 2.0 Features and Properties.

Comparing the Policy Specifications.

WS-MetadataExchange.

Summary.

8. Web Services Security.

Overarching Concern.

Core Concepts.

Identity.

Authentication.

Digital Signature.

Summary of Challenges, Threats, and Remedies.

Message Interception.

Person in the Middle Attacks.

Spoofing.

Replay Attacks.

Denial-of-Service Attacks.

Securing the Communications Layer.

IP Layer Security.

Transport-Level Security.

Message-Level Security.

The WS-Security Framework.

WS-SecurityPolicy.

WS-Trust.

WS-SecureConversation.

WS-Federation.

Security Assertion Markup Language (SAML).

XACML: Communicating Policy Information.

XML Key Management Specification (XKMS).

Data-Level Security.

XML Encryption.

XML Signature.

Summary.

9. Advanced Messaging.

Reliable Messaging.

Overview.

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.

Notification.

WS-Eventing.

WS-Notification.

Mobile Workers and Occasionally Connected Computing.

Summary.

10. Transaction Processing.

Overview.

The Transaction Paradigm.

Impact of Web Services on Transactions.

Protocols and Coordination.

Activity.

Context.

Addressing.

Policy.

Coordination.

Protocol Types.

Transaction Specifications.

The Web Services Coordinator.

WS-AtomicTransaction.

WS-BusinessActivity.

WS-Context.

WS-Coordination Framework.

WS-Transaction Management.

Summary.

Bibliography.

Books.

Technology References.

Articles.

Specifications.

General.

Metadata.

Security.

Reliability.

Notification.

Transactions.

Orchestration.

Orchestration Historical References.

Other Resources.

Index.

Read More Show Less

Preface

Preface

The widely adopted and implemented core Web services standards (SOAP and WSDL) have achieved unprecedented interoperability across highly disparate software systems. As a result, new Web services standards have been proposed for extended features such as security, reliability, transactions, metadata management, and orchestration that extend Web services for use in a broad range of new applications.

The service-oriented architecture (SOA) has also become widely recognized for its important role in information technology projects. An SOA is a style of design that guides an organization during all aspects of creating and using business services (including conception, modeling, design, development, deployment, management, versioning, and retirement).

Despite some limitations (which we document), an SOA with Web services is the ideal combination of architecture and technology for consistently delivering robust, reusable services that support today's business needs and that can be easily adapted to satisfy changing business requirements.

Think about an SOA as an assembly line in a factory. It's an investment in the future operation of your business, so a significant amount of planning, design, and development may have to go into it before it starts to really pay off. The first car off a production line is more expensive than the thousandth. Similarly, the first service deployed in an SOA is more expensive than the hundredth. The major benefits of SOA arrive over time, although as we will see, it is possible to start small and incrementally build up to a full-fledged SOA.

SOA with Web services is important because it aligns information technology (IT) with business requirements and because it reduces the costs of IT systems and applications. An SOA gives you the ability to more easily integrate IT systems, provide multi-channel access to your systems, and to automate business processes.

Rather than relying entirely upon the skill and knowledge of certain specific individuals to implement business requirements in technology, SOA provides a foundation for rapidly assembling and composing new applications out of a library of reusable services that anyone can understand. When an SOA is in place and services are developed, developers can easily reuse existing services in their new applications and automated business processes.

Like any new investment in technology and infrastructure, it's important to understand the right way to do it and what you can and can't do. SOA and Web services are great, but they can't do everything. We hope that this book will help you achieve the benefits of SOA with Web services while avoiding the pitfalls.

© Copyright Pearson Education. All rights reserved.

Read More Show Less

Customer Reviews

Average Rating 4
( 1 )
Rating Distribution

5 Star

(0)

4 Star

(1)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Anonymous

    Posted January 25, 2005

    SOA = interface

    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.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)