Service-Oriented Architecture: A Field Guide To Integrating . - Arcitura
erl.book XXXXXXXXXXXXXXXXXXXXXXXXPage iii Thursday, March 25, 2004 1:05 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit eA Field Guide to Integrating XML andWeb ServicesThomas ErlPRENTICE HALLPROFESSIONAL TECHNICAL REFERENCEUPPER SADDLE RIVER, NJ 07458WWW.PHPTR.COM
erlTOC.fm Page v Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit www.serviceoriented.ws.C o n te n tsPrefaceXIXC h a p te r 1In tro d u ctio n1 .11 .21 .31 .41 .51W h y th is g u id e is im p o rtan t . 21 .1 .1T h e h am m er an d X M L . 21 .1 .2X M L an d W eb s erv ices . 31 .1 .3W eb s erv ices an d S erv ice-O rien ted A rch itectu re . 31 .1 .4S erv ice-O rien ted A rch itectu re an d th e h am m er. 31 .1 .5T h e h am m er an d y o u . 4T h e X M L & W eb S erv ices In teg ratio n F ram ew o rk (X W IF ). 4H o w th is g u id e is o rg an iz ed . 51 .3 .1Part I: T h e tech n ical lan d s cap e. 61 .3 .2Part II: In teg ratin g tech n o lo g y . 71 .3 .3Part III: In teg ratin g ap p licatio n s . 91 .3 .4Part IV : In teg ratin g th e en terp ris e . 121 .3 .5T h e ex ten d ed en terp ris e . 13w w w .s erv iceo rien ted .w s . 13C o n tact th e au th o r. 13v
erlTOC.fm Page vi Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit www.serviceoriented.ws.viContentsP art IThe technical landscape15Chapter 2Introduction to XML technologies2.1E xtensible Markup Language (XML). 182.1.12.1.22.1.32.1.42.22223Concepts. 25Syntax . 25Concepts. 28Syntax . 28Concepts. 34Syntax . 35XML Q uery Language (XQ uery) . 382.5.12.5.22.621E xtensible Stylesheet Language Transformations (XSLT) . 332.4.12.4.22.520XML Schema D efinition Language (XSD ). 282.3.12.3.22.4Concepts.Schemas .Programming models.Syntax .D ocument Type D efinitions (D TD ) . 242.2.12.2.22.317Concepts. 38Syntax . 41XML Path Language (XPath) . 432.6 .12.6 .2Concepts. 43Syntax . 44Chapter 3Introduction to Web services technologies3.147Web services and the service-oriented architecture (SOA) . 483.1.13.1.23.1.33.1.43.1.5U nderstanding services .XML Web services .Service-oriented architecture (SOA) .Common principles of service-orientation.Web service roles .4849505355
erlTOC.fm Page vii Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit .1.93.2Web Services Descritption Language (WSDL) . 673.2.13.2.23.2.33.3Abstract interface definition. 68Concrete (implementation) definition . 70Supplementary constructs . 71Simple Object Access Protocol (SOAP). 723.3.13.3.23.4Web service interaction. 57Service models . 61Web service description structure . 64Introduction to first-generation Web services. 66SOAP messaging framework. 74SOAP message structure . 77Universal Description, Discovery, and Integration (UDDI) . 81Chapter 4Introduction to second-generation (WS-*) Web servicestechnologies4.1Second-generation Web services and the service-orientedenterprise (SOE) . 904.1.14.1.24.2Concepts. 96Syntax . 99B usiness Process Execution Language for WebServices (B PEL4WS) . 1004.3.14.3.24.3.34.4Problems solved by second-generation specifications . 92The second-generation landscape. 94WS-Coordination and WS-Transaction . 964.2.14.2.24.389R ecent business process specifications . 100Concepts. 100Syntax . 106WS-Security and the Web services security specifications. 1094.4.14.4.24.4.34.4.44.4.5G eneral security concepts .Specifications.XML K ey Management (XK MS).Extensible Access Control Markup Language (XACML)and Extensible R ights Markup Language (XrML) .Security Assertion Markup Language (SAML)and .N ET Passport.110111112112112
erlTOC.fm Page viii Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit 4.4.94.5113115117WS-Addressing .Concepts.Acknowledgements.Syntax .119119121123WS-Policy. 1254.6.14.6.24.7113WS-ReliableMessaging. 1184.5.14.5.24.5.34.5.44.6XML-Encryption and XML-Digital Signature .Secure Sockets Layer (SSL) .The WS-Security framework .Concepts and syntax .Concepts . 126Syntax . 126WS-Attachments . 127Part IIIntegrating technology131Chapter 5Integrating XML into applications5.1Strategies for integrating XML data representation. 1.105.1.115.1.125.2133Positioning XML data representation in your architecture .Think “tree” (a new way of representing data) .Easy now (don’t rush the XML document model).Design with foresight.Focus on extensibility and reusability .Lose weight while modeling! (keeping your documents trim) .Naming element-types: performance vs. legibility .Applying XML consistently .Choosing the right API (DOM vs. SAX vs. Data Binding) .Securing XML documents.Pick the right tools.Don’t try this at home (fringe optimization rategies for integrating XML data validation . 1515.2.15.2.2XSD schemas or DTDs? . 151Positioning DTDs in your architecture. 155
erlTOC.fm Page ix Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit 2163165166167169XML schemas and the silent disparity pattern . 170A step-by-step process . 171Strategies for integrating XML transformation. 1745.4.15.4.25.4.35.4.45.4.55.4.65.5156Strategies for integrating XML schema administration. 1705.3.15.3.25.4Positioning XSD schemas in your architecture .Understand the syntactical limitations of XSD schemas.Understand the performance limitations of XSD schemas .Other fish in the sea (more schema definition languages).Supplementing XSD schema validation.Integrating XML validation into a distributed architecture .Avoiding over-validation.Consider targeted validation .Building modular and extensible XSD schemas .Understand the integration limitations of your database.Positioning XSLT in your architecture.Pre-transform for static caching .Create dynamic XSLT style sheets.Simplify aesthetic transformation with CSS .Understand the scalability limitations of XSLT.Strategic redundancy .174177178178178179Strategies for integrating XML data q uerying. 1795.5.15.5.25.5.35.5.4Positioning XQuery in your architecture.Multi-data source abstraction.Establishing a data policy management layer.Unifying documents and data .180180182183Chapter 6Integrating Web services into applications6.1Service models. 1886.1.16.1.26.1.36.2187Utility services . 189Business services . 191Controller services . 191Modeling service-oriented component classes andWeb service interfaces. 1946.2.1Designing service-oriented component classes(a step-by-step process) . 195
erlTOC.fm Page x Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit www.serviceoriented.ws.xContents6.2.26.3Strategies for integrating service-oriented encapsulation . 216217218219Everything in moderation, including service compositions. 221Modeling service compositions . 221Compound service compositions . 224Strategies for enhancing service functionality. 2256.5.16.5.26.5.36.6Define criteria for consistent logic encapsulationand interface granularity .Establish a standard naming convention .Parameter-driven vs. operation-oriented interfaces.Designing for diverse granularity .Utilize generic services consistently .Establish separate standards for internaland external services .Considering third-party Web services .Strategies for integrating service compositions . 2206.4.16.4.26.4.36.5Designing Web service interfaces(a step-by-step process) . 206Outputting user-interface information. 225Caching more than textual data . 226Streamlining the service design with usage patterns. 227Strategies for integrating SOAP messaging. 2286.6.16.6.26.6.36.6.4SOAP message performance management .SOAP message compression techniques.Security issues with SOAP messaging .Easing into SOAP .228228230231Chapter 7Integrating XML and databases7.1Comparing XML and relational databases . 2347.1.17.1.27.1.37.1.47.1.57.2233Data storage and security .Data representation .Data integrity and validation.Data querying and indexing .Additional features .235235236236236Integration architectures for XML and relational databases. 2377.2.17.2.2Storing XML documents as database records . 240Storing XML document constructs as database records . 242
erlTOC.fm Page xi Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit 3Strategies for integrating XML with relational databases . ing XML documents to relational data.The Bear Sightings application .Intrinsic one-to-one and one-to-many relationships with XML .Mapping XML to relational data with DTDs.Mapping XML to relational data with XSD schemas .255256256258265Database extensions. 2717.5.17.5.27.5.37.5.47.5.57.5.67.5.77.6Target only the data you need .Avoiding relationships by creating specialized data views.Create XML-friendly database models.Extending the schema model with annotations.Non-XML data models in XML schemas.Developing a caching strategy.Querying the XSD schema .Control XML output with XSLT.Integrate XML with query limitations in mind .Is a text file a legitimate repository?.Loose coupling and developer skill sets .Techniques for mapping XML to relational data. 2557.4.17.4.27.4.37.4.47.4.57.5Using XML to represent a view of database queries . 243Using XML to represent a view of a relational data model. 245Using XML to represent relational data withinan in-memory database (IMDB). 246Proprietary extensions to SQL .Proprietary versions of XML specifications .Proprietary XML-to-database mapping .XML output format .Stored procedures .Importing and exporting XML documents .Encapsulating proprietary database extensionswithin Web services .271272272272273273274Native XML databases . 2747.6.17.6.27.6.37.6.4Storage of document-centric data.Integrated XML schema models .Queries and data retrieval.Native XML databases for intermediary storage.274275275276
erlTOC.fm Page xii Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit www.serviceoriented.ws.xiiContentsPart IIIIntegrating applications278Chapter 8The mechanics of application integration8.1Understanding application integration. 2828.1.18.1.28.1.38.1.48.2282282283284Data-level integration .Application-level integration .Process-level integration.Service-oriented integration .287288289290A guide to middleware. 2918.3.18.3.28.3.38.3.48.4Types of integration projects.Typical integration requirements.Progress versus impact .Types of integration solutions .Integration levels . 2868.2.18.2.28.2.38.2.48.3281“EAI” versus “middleware” .Shredding the Oreo.Common middleware services and products .A checklist for buying middleware.291291292294Choosing an integration path . 2988.4.18.4.28.4.38.4.48.4.5Two paths, one destination .Moving to EAI.Common myths.The impact of an upgrade .Weighing your options .299299299300301Chapter 9Service-oriented architectures for legacy integration9.1303Service models for application integration . 3049.1.19.1.29.1.3Proxy services. 305Wrapper services . 307Coordination services (for atomic transactions). 308
erlTOC.fm Page xiii Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit www.serviceoriented.ws.xiiiContents9.2Fundamental integration components. 3109.2.19.2.29.2.39.3Web services and one-way integration architectures. 3149.3.19.3.29.49.4.29.4.39.4.4Tightly coupled integration between homogenouslegacy applications.Tightly coupled integration between heterogeneousapplications .Integration between homogenous component-basedapplications .Integration between heterogeneous component-basedapplications .324325332336Web services and centralized database architectures. 3409.5.19.5.29.6Batch export and import. 315Direct data access . 319Web services and point-to-point architectures . 3249.4.19.5Adapters. 310Intermediaries . 312Interceptors . 314Traditional architecture . 340Using a Web service as a data access controller . 341Service-oriented analysis for legacy architectures. 344Chapter 10Service-oriented architectures for enterprise integration10.1Service models for enterprise integration architectures . 35410.1.110.1.210.2Process services. 354Coordination services (for business activities). 356Fundamental enterprise integration architecture components . 35810.2.110.2.210.3353Broker . 360Orchestration . 363Web services and enterprise integration architectures . 36810.3.110.3.210.3.3Hub and spoke. 369Messaging bus. 372Enterprise Service Bus (ESB). 375
erlTOC.fm Page xiv Tuesday, February 8, 2005 9:17 PMSample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services"by Thomas Erl. For more information visit www.serviceoriented.ws.xivContentsChapter 11Service-oriented integration strategies11.1Strategies for streamlining integration endpoint interfaces . 1.3.311.3.411.3.511.3.611.3.7383385387387Minimize the use of service intermediaries .Consider using service interceptors.Data processing delegation .Caching the provider WSDL definition .389389391392Create a transition architecture by adding partialintegration layers.Data caching with an IMDB.Utilizing a queue to counter scalability demands .Adding a mini-hub .Abstract legacy adapter technology.Leveraging legacy integration architectures .Appending Web services to legacy integration architectures .394394395397398398400Strategies for enterprise solution integration. 40111.4.111.4.211.4.311.4.411.5381382Strategies for integrating legacy architectures . 39411.3.111.4Make interfaces more generic.Consolidate legacy interfaces .Consolidate proxy interfaces.Supplement legacy logic with external logic .Add support for multiple data output formats .Provide alternative interfaces for different SOAP clients .Strategies for optimizing integration endpoint services. 38911.2.111.2.211.2.311.2.411.3379Pragmatic service-oriented integration .Integrating disparate EAI products.Respect your elders (building EAI around your legacyenvironments) .Build a private service registry .402403404406Strategies for integrating Web services security . 40611.5.111.5.211.5.311.5.411.5.511.5.6Learn about the Web services security specifications .Build services with a standardized service-orientedsecurity (SOS) model.Creat
Service-Oriented Architecture A Field Guide to Integrating XML and Web Services Thomas Erl erl.book XPaXgXe iXiiX TXhXurXsdXayX,XMXarXcXh X25X, 2X0X04X X1:X05X PXMX Sample Chapter 1 from "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services" by Thomas Erl. For more information visit www.serviceoriented.ws.
"A service oriented architecture is an approach to design and integrate software in a modular method where each module is precisely a 'loosely coupled service' ,,,” “Service Oriented Architecture is nothing but business oriented architecture ” “SOA is a framework enabling
Service Oriented Architecture Training Session for STDDS November 2014 What is Service Oriented Architecture Service-Oriented Architecture (SOA) is a software and architecture design pattern based on a structured collection of discrete software modules known as services. SOA i
foundation for conducting business in the context of Service Oriented Architecture; the Realizing Services view which addresses the requirements for constructing a Service Oriented Architecture; and the Owning Service Oriented Architecture view which focuses on the governance and management of SOA-based systems. Status:
Web Services and Service Oriented Architecture Thomas Soddemann Delaman Workshop 2004 21 Service Oriented Architectures (SOA) Service Oriented Architecture Web Services CORBA Jini EJB An architecture of software which is composed of services. No Objects Objects Objects Objects Simple WS: No session, no state [ e.g. Shopping Cart realization?
What is Service-Oriented Architecture (SOA)? SOA is a software architecture style that focuses on service components (services) that are reusable across multiple applications and enterprises. While Service-Oriented Architecture (SOA) is an old concept, current standards and technologies have paved the way to add efficiency to IT and gain
Services view which addresses the requirements for constructing a Service Oriented Architecture; and the Owning Service Oriented Architecture view which focuses on the governance and management of SOA-based systems. Status: This document was last revised or
What is Computer Architecture? “Computer Architecture is the science and art of selecting and interconnecting hardware components to create computers that meet functional, performance and cost goals.” - WWW Computer Architecture Page An analogy to architecture of File Size: 1MBPage Count: 12Explore further(PDF) Lecture Notes on Computer Architecturewww.researchgate.netComputer Architecture - an overview ScienceDirect Topicswww.sciencedirect.comWhat is Computer Architecture? - Definition from Techopediawww.techopedia.com1. An Introduction to Computer Architecture - Designing .www.oreilly.comWhat is Computer Architecture? - University of Washingtoncourses.cs.washington.eduRecommended to you b
Scholarly accounts on non-alignment and neutralism in the Cold War in Asia are not very many, and these mainly focus on India. Indeed, even as late as the early 1990s, scholarly accounts on non-alignment and on regional developments in Asia during the Cold War in the 1950s tended to miss out Indonesia.2 The more
