Service-Oriented Architecture. A Field Guide to Integrating XML and Web Services

By:

Erl, Thomas

Material type: Text

TextSeries: Prentice Hall service-oriented computing series from Thomas ErlPublication details: New Jersey: Pearson Education Inc.: 2004Edition: FirstDescription: PaperbackISBN:

0131428985

Subject(s):

Holdings
Item type	Current library	Call number	Copy number	Status	Date due	Barcode
Standard Loan	Thurles Library Main Collection	004.36 ERL (Browse shelf(Opens below))	1	Available		30026000010008

Enhanced descriptions from Syndetics:

As XML becomes an increasingly significant part of the IT mainstream, expert guidance and common-sense strategies are required to avoid the many pitfalls of applying XML incorrectly or allowing it to be used in an uncontrolled manner. This book acts as a knowledge base for issues relating to integration, and provides clear, concise advice on how to best determine the manner and direction XML technology should be positioned and integrated. The book will be one of the first to provide documentation for second-generation Web services technologies (also known as WS-*). The importance of these specifications (which include BPEL, WS-Transaction, WS-Coordination, WS-Security, WS-Policy, and WS-Reliable Messaging) cannot be understated. Major standards organizations and vendors are supporting and developing these standards. ***David Keogh, Program Manager for Enterprise Frameworks and Tools, Microsoft, will provide a front cover quotation for the book.

Table of contents provided by Syndetics

Preface
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
I The Technical Landscape
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-&ast;) 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
II Integrating Technology
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
III Integrating Applications
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
IV Integrating the Enterprise
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
Index

Excerpt provided by Syndetics

Preface My father runs a placer mine, far North in a remote part of the Yukon wilderness. For almost half a century, he's made his living plowing through mountains with his bulldozers, looking for gold. Due to the climate, he gets only a limited amount of time during which he can actually mine. His priority, therefore, is to keep his business fully operational throughout this period. Any disruption results in lost revenue. Despite his best efforts, though, he is constantly faced with obstacles. He's had to contend with volatile, sometimes even violent environmental conditions. He's had to confront bears that roamed into his camp, looking for food. He's even chased thieves off his land in the middle of the night. Once, the hydraulic pump on his front-end loader collapsed, crushing his hand. Instead of "wasting" two days to get to the nearest hospital, he simply wrapped a diesel soaked rag around his broken fingers and kept on going. The worst kind of problem he's ever had to face, though, is mechanical failure. If a key piece of equipment breaks, if an engine slows or stops, or if any other part of his infrastructure seizes, his business comes to a (literally) grinding halt. It can take weeks to get new equipment or spare parts -- a delay that can be devastating to his bottom line. When faced with these challenges in the past, he's had only himself to rely on. I asked him once how he deals with these situations. He told me that there are very few problems in life that can't be solved with a blowtorch and a welding rod. I think about that "life philosophy" sometimes, when staring at the cursor, blinking hypnotically amidst some problem displayed on my computer screen. I've always been involved with new technology. It has the mystery of the unknown and the attraction of potential. It's also put me in more "impossible" situations than I care to remember. Although I have respect for the expertise required to produce product documentation and tutorials, I generally classify this information as "option A." It is surprising how often option A does not work in integrated environments. But, that's what option B is for. Option B is when I roll up my sleeves and light my own blowtorch. This attitude is important when working on integration projects. Some integration tasks are easy. Making two compatible pieces of software talk to each other can be straightforward, involving a predictable development and deployment effort. Others, though, can be a nightmare. Sometimes two pieces of software aren't just "not compatible," they seem violently opposed to each other's very existence. The goal of this guide is to help you define your own options for whatever integration challenges you might be facing. I am fortunate to be writing a book about integration strategy at a time when the IT community has at its disposal a platform that fosters integration and interoperability like never before. I hope that you will find this guide not only useful, but that it will lead you to view XML, Web services, and service-oriented principles as problem-solving tools. So that no matter what obstacles cross your path, you will be able to use your own blowtorch to carve out that perfect solution. (c) Copyright Pearson Education. All rights reserved. Excerpted from Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services by Thomas Erl All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Author notes provided by Syndetics

Thomas Erl is an independent consultant and Chief Architect at XMLTC Consulting Inc. in Vancouver, BC, Canada