Cover image for SOA Approach to Integration.
SOA Approach to Integration.
Title:
SOA Approach to Integration.
Author:
Juric, Matjaz B.
ISBN:
9781847190116
Personal Author:
Edition:
1st ed.
Physical Description:
1 online resource (398 pages)
Contents:
SOA Approach to Integration -- Table of Contents -- SOA Approach to Integration -- Credits -- About the Authors -- About the Reviewers -- Preface -- What This Book Covers -- Who is This Book for -- Conventions -- Reader Feedback -- Customer Support -- Errata -- Questions -- 1. Integration Architecture, Principles, and Patterns -- Integration Challenges -- Current Situation -- Effective Information Systems -- Replacing Existing Applications -- Requirements and Strategies -- Single Data Input -- Information Access with Low Latency -- Importance of a Centrally Managed Integration Project -- Responsibility to Define Integration Architecture -- Responsibility to Select Integration Infrastructure and Technologies -- Development and Maintenance of Integration Documentation -- Integration Architecture Steps and Approaches -- Bottom-Up Approach -- Top-Down Approach -- Sound Integration Architecture Benefits -- Types of Integration -- Data-Level Integration -- Application Integration -- Business Process Integration -- Presentation Integration -- Business-to-Business Integration -- Integration Infrastructure -- Communication -- Brokering and Routing -- Transformation -- Business Intelligence -- Transactions -- Security -- Lifecycle -- Naming -- Scalability -- Management -- Rules -- Integration Technologies -- Database Access Technologies -- Message-Oriented Middleware -- Remote Procedure Calls -- Transaction Processing Monitors -- Object Request Brokers -- Application Servers -- Web Services -- Enterprise Service Buses -- The Integration Process -- Choosing the Steps and Defining the Milestones -- Sound Practices -- Iterative Development -- Incremental Development -- Prototyping -- Reuse -- Integration Process Activities and Phases -- Integration Patterns -- Summary -- 2. Service- and Process-Oriented Architectures for Integration.

Defining Service-Oriented Architectures -- Why SOA in the Integration Space? -- Islands in the Enterprise IT Landscape -- The Integration Problem -- Custom Integration Application and Its Issues -- Inverted View: Reusable Services, Simple Integration Processes -- Enter SOA: A Services-Based Integration Architecture -- Concepts and Principles of SOA -- Paradigm Shift - from Self-Contained Applications towards "Services" -- Service Orientation -- Component-Based Services -- The Internet Simplifies Remote Services -- Consuming Services -- Introducing SOA Architecture -- Service Abstractions -- Service Invocation and Service Implementation -- Process Engines -- Messaging Abstractions -- Synchronous and Asynchronous Messages -- Service Registries -- Quality of Service -- Communication Infrastructure -- What is a "Bus"? -- XML and Web Services: SOA Foundation -- Using XML in Middleware -- Middleware Mechanics for Services -- XML-Based Mechanism to "Invoke" Services -- Services over the Web via SOAP -- Web Services - Protocols for SOA -- Technology Agnostic System-to-System Interaction -- Service Description - Using WSDL -- Discovering the Services - UDDI -- Containers to Host Web Services -- Standards Foundation -- Application Platforms (JAVA EE) Hosting Web Services -- Using Services to Compose Business Processes -- Simple Integration Applications -- Simple Business Processes - Orchestrating the Services -- Advantages of Business Processes -- Choreography - Multi-Party Business Process -- Collaboration between Enterprises (B2B) -- SOA Security and Transactions -- Security Challenges in a Services Environment -- Simple Middleware Systems Security -- Security in Java Infrastructure -- Microsoft.NET Security -- Web Services Security for Loosely Coupled Services -- Emerging Web Services Security Standards -- Transactions in SOA.

Web Services Transaction - A Standard -- Infrastructure Needed for SOA -- Service Execution and Communications -- Types of Component Services -- Service Containers (Execution Engines) -- Communication Infrastructure - Under the Covers -- Communication "Bus" - At the Core -- MOM -- XML Backbone (XML, Transformations, and Persistence) -- Reliability and Scalability -- Managing a Distributed SOA Environment -- Options for SOA Infrastructure -- Web Services -- Application Platforms (JAVA EE / .NET) -- Simple Messaging-Based Custom Infrastructure -- Integration Platforms (EAI) -- ESB - Enterprise Service Bus -- Designing Services and Processes for Portability -- Adoption Considerations -- Think Services -- Model the Business Data as XML -- Processes in BPEL -- New Applications - Prepare for SOA/POA -- Design for Infrastructure (Vendor) Independence -- Transition to Process-Oriented Architectures -- Services and Processes Coexist - But Services First -- Process - Orchestration of Services -- POA - Shifting the Focus to "Processes First" -- Concepts and Principles of Process-Oriented Architectures -- POA - Processes First. Services... Maybe! -- POA Enables Top-down Design - Using just Processes -- Analysts Become Programmers -- POA Changing Software Development Roles -- Process Standards -- Infrastructure for Process-Oriented Architectures -- Summary -- 3. Best Practices for Using XML for Integration -- Introduction -- Domain-Specific XML Schemas -- Sending and Receiving XML Documents -- Validating XML Documents -- Mapping Schemas -- Choosing Processing Models -- Fragmenting Incoming XML Documents -- Design Recommendations -- Tips for Designing XML Schemas -- Default Namespace - targetNamespace or XMLSchema? -- Localize Namespace vs. Expose Namespaces -- Requirements for Localizing the Schema.

Advantages of Localizing Component Namespaces within the Schema -- Advantages of Exposing Namespaces in Instance Documents -- Global vs. Local Declaration -- Russian Doll and Salami Slice Designs -- Element vs. Type -- Zero, One, or Many Namespaces -- Use the Heterogeneous Namespace Design -- Use the Homogeneous Namespace Design -- Use the Chameleon Design -- Using XSL for Transformation -- xsl:import and xsl:include -- Securing XML Documents -- XML Security Threats -- XML Encryption -- Encrypting an XML File -- Encrypting a Single Element -- SSL versus XML Encryption -- XML Signatures -- Guidelines for Securing Your Services -- XML Streaming and DOM -- Pull Parsing versus Push Parsing -- What is StAX? -- StAX and Other JAXP APIs -- Performance Considerations -- Limit Parsing of Incoming Documents -- Use the Appropriate API -- Choosing Parser -- Reduce Validation Cost -- Referencing External Entities -- Dynamically Generated Documents -- Using XML Judiciously -- Summary -- 4. SOA and Web Services Approach for Integration -- Designing Service-Oriented Architectures -- SOA Evolution -- IT Evolution -- Patterns -- Business Patterns -- Integration Patterns -- Composite Patterns -- Application Patterns -- Runtime Patterns -- Product Mappings -- Guidelines -- Designing Sound Web Services for Integration -- Web Services Architecture -- Web Services Benefits -- Self-Contained -- Self-Describing -- Modular -- Accessible Over the Web -- Language, Platform, Protocol Neutral -- Open and Standards-Based -- Dynamic -- Composable -- Patterns -- Self-Service Business Pattern -- Guidelines -- Extended Enterprise Business Pattern -- Guidelines -- Application Integration Pattern -- Application Integration Patterns -- Direct Connection Application Pattern -- Guidelines -- Broker Application Pattern -- Guidelines -- Serial Process Application Pattern -- Guidelines.

Parallel Process Application Pattern -- Guidelines -- Runtime Patterns -- Nodes -- Application Server/Services -- Rules Repository -- Router -- Protocol Firewall Node -- Domain Firewall Node -- Connectors -- Adapter Connector -- Path Connector -- Direct Connection Runtime Pattern -- Direct Connection Pattern using Single Adapter -- Direct Connection using Coupling Adapter -- Direct Connection using Service Bus -- Runtime Patterns for Broker -- Differences between B2B and EAI Web Services -- Interface Design -- Use of a Service Registry -- Writing Interoperable WSDL Definitions -- Validating Interoperable WSDL -- Interoperability Challenges in Web Services -- WS-I Specifications -- WS-I Basic Profile 1.0 -- WS-I Basic Profile 1.1 -- SOAP Changes -- WSDL Changes -- WS-I Basic Profile 1.2 -- SOAP Changes -- WSDL Changes -- WS-I Basic Security Profile 1.0 -- Guidelines for Creating Interoperable Web Services -- Avoid using Vendor-Specific Extensions -- Use the Latest Interoperability Tests -- Understand Application Data Models -- Understand Interoperability of Data Types -- Java EE and .NET Integration using Web Services -- Sample Integration Scenario -- Developing the Java Web Service -- Deploying the Service -- WSDL for Java Web Service -- Developing the .NET Web Service -- Deploying the .NET Web Service -- Developing the Test Client -- Summary -- 5. BPEL and the Process-Oriented Approach to Integration -- Process-Oriented Integration Architectures -- Service Composition -- Orchestration and Choreography -- Complexity of Business Services -- Identifying Business Services -- Development Lifecycle -- SOA and Executable Business Processes -- Example Business Process -- BPEL for Service Composition -- What We Can Do with BPEL -- Executable and Abstract Processes -- BPEL and Other Process Languages -- Languages for Choreography -- Modeling Notations.

Writing BPEL Processes.
Abstract:
XML, Web services, ESB, and BPEL in real-world SOA projects.
Local Note:
Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2017. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.
Electronic Access:
Click to View
Holds: Copies: