Large IT organizations increasingly face the challenge of integrating various web services, applications, and other technologies into a single network. The solution to finding a meaningful large-scale architecture that is capable of spanning a global enterprise appears to have been met in ESB, or Enterprise Service Bus. Rather than conform to the hub-and-spoke architecture of traditional enterprise application integration products, ESB provides a highly distributed approach to integration, with unique capabilities that allow individual departments or business units to build out their integration projects in incremental, digestible chunks, maintaining their own local control and autonomy, while still being able to connect together each integration project into a larger, more global integration fabric, or grid.Enterprise Service Bus offers a thorough introduction and overview for systems architects, system integrators, technical project leads, and CTO/CIO level managers who need to understand, assess, and evaluate this new approach. Written by Dave Chappell, one of the best known and authoritative voices in the field of enterprise middleware and standards-based integration, the book drills down into the technical details of the major components of ESB, showing how it can utilize an event-driven SOA to bring a variety of enterprise applications and services built on J2EE, .NET, C/C++, and other legacy environments into the reach of the everyday IT professional.With Enterprise Service Bus, readers become well versed in the problems faced by IT organizations today, gaining an understanding of how current technology deficiencies impact business issues. Through the study of real-world use cases and integration patterns drawn from several industries using ESB--including Telcos, financial services, retail, B2B exchanges, energy, manufacturing, and more--the book clearly and coherently outlines the benefits of moving toward this integration strategy. The book also compares ESB to other integration architectures, contrasting their inherent strengths and limitations.If you are charged with understanding, assessing, or implementing an integration architecture, Enterprise Service Bus will provide the straightforward information you need to draw your conclusions about this important disruptive technology.

Osoby które kupowały "Enterprise Service Bus. Theory in Practice", wybierały także:

• Zen Steve'a Jobsa 29,67 zÅ‚, (8,90 zÅ‚ -70%)
• ASP.NET MVC. Kompletny przewodnik dla programistów interaktywnych aplikacji internetowych w Visual Studio 86,77 zÅ‚, (26,90 zÅ‚ -69%)
• jQuery, jQuery UI oraz jQuery Mobile. Receptury 57,74 zÅ‚, (17,90 zÅ‚ -69%)
• Scratch. Komiksowa przygoda z programowaniem 36,06 zÅ‚, (11,90 zÅ‚ -67%)
• Baltie. Kurs video. Poziom pierwszy. Elementarz programowania w jÄ™zyku wizualnym 59,00 zÅ‚, (26,55 zÅ‚ -55%)

Spis treści

Enterprise Service Bus. Theory in Practice eBook -- spis treści

• Enterprise Service Bus
• A Note Regarding Supplemental Files
• Foreword
• Preface
  • About This Book
    • Overview of the Chapters
  • Notational Conventions for ESB Integration Patterns
    • Diagramming Notations
  • Conventions Used in This Book
  • Wed Like to Hear from You
  • Acknowledgments
• 1. Introduction to the Enterprise Service Bus
  • 1.1. SOA in an Event-Driven Enterprise
  • 1.2. A New Approach to Pervasive Integration
  • 1.3. SOA for Web Services, Available Today
  • 1.4. Conventional Integration Approaches
  • 1.5. Requirements Driven by IT Needs
  • 1.6. Industry Traction
    • 1.6.1. Vendors Adopting the ESB
  • 1.7. Characteristics of an ESB
    • 1.7.1. Pervasiveness
    • 1.7.2. Standards-Based Integration
    • 1.7.3. Highly Distributed Integration and Selective Deployment
    • 1.7.4. Distributed Data Transformation
    • 1.7.5. Extensibility Through Layered Services
    • 1.7.6. Event-Driven SOA
    • 1.7.7. Process Flow
    • 1.7.8. Security and Reliability
    • 1.7.9. Autonomous but Federated Environment
    • 1.7.10. Remote Configuration and Management
    • 1.7.11. XML as the Native Datatype of the ESB
    • 1.7.12. Real-Time Throughput of Business Data
    • 1.7.13. Operational Awareness
    • 1.7.14. Incremental Adoption
  • 1.8. Adoption of ESB by Industry
    • 1.8.1. Financial Services
    • 1.8.2. Insurance
    • 1.8.3. Manufacturing
    • 1.8.4. Retail
    • 1.8.5. Telecom
    • 1.8.6. Energy/Utility
    • 1.8.7. Food Distribution Network
    • 1.8.8. Government
  • 1.9. Summary
• 2. The State of Integration
  • 2.1. Business Drivers Motivating Integration
    • 2.1.1. IT Spending Trends
    • 2.1.2. Integration as a High-Ranking Priority
    • 2.1.3. Regulatory Compliance
      • 2.1.3.1. Telecom
      • 2.1.3.2. Sarbanes-Oxley
      • 2.1.3.3. Government
    • 2.1.4. Straight-Through Processing (STP)
    • 2.1.5. Radio Frequency Identification (RFID)
  • 2.2. The Current State of Enterprise Integration
    • 2.2.1. The Enterprise Is Not Well Connected
    • 2.2.2. The Accidental Architecture
      • 2.2.2.1. Departmental and organizational issues
      • 2.2.2.2. Moving forward with an accidental architecture
    • 2.2.3. ETL, Batch Transfers, and FTP
    • 2.2.4. Integration Brokers
  • 2.3. Leveraging Best Practices from EAI and SOA
    • 2.3.1. Adopt XML
    • 2.3.2. Adopt Web Services and Implement SOA
  • 2.4. Refactoring to an ESB
    • 2.4.1. Introduce the ESB at an Individual Project Level
    • 2.4.2. Propagate the ESB Across a Widely Distributed Enterprise
    • 2.4.3. Leave and Layer: Connecting into the Existing EAI Broker
    • 2.4.4. Partner Integration
  • 2.5. Summary
• 3. Necessity Is the Mother of Invention
  • 3.1. The Evolution of the ESB
  • 3.2. The ESB in Global Manufacturing
    • 3.2.1. Putting It to the Test
  • 3.3. Finding the Edge of the Extended Enterprise
    • 3.3.1. e-Commerce Trading Hubs
    • 3.3.2. The Extended Enterprise: The Ever-Changing Edge
    • 3.3.3. Corralling the Ever-Changing Edge of the Network
  • 3.4. Standards-Based Integration
    • 3.4.1. The New Economics of Integration
    • 3.4.2. Driving Down the Cost of Technology
  • 3.5. Case Study: Manufacturing
    • 3.5.1. Building a Real-Time Business
      • 3.5.1.1. Inventory management
      • 3.5.1.2. Technical challenges
      • 3.5.1.3. Availability To Promise (ATP)
    • 3.5.2. Flexible Partner Integration
  • 3.6. Summary
• 4. XML: The Foundation for Business Data Integration
  • 4.1. The Language of Integration
    • 4.1.1. XML Is Human-Readable
  • 4.2. Applications Bend, but Dont Break
  • 4.3. Content-Based Routing and Transformation
  • 4.4. A Generic Data Exchange Architecture
    • 4.4.1. Data Translation to and from a Canonical Format
    • 4.4.2. Adopting a Canonical Data Exchange
    • 4.4.3. Alternate Approaches
  • 4.5. Summary
• 5. Message Oriented Middleware (MOM)
  • 5.1. Tightly Coupled Versus Loosely Coupled Interfaces
    • 5.1.1. Remote Procedure Call (RPC)-Style Programming
    • 5.1.2. Tightly Coupled Interfaces
    • 5.1.3. Loosely Coupled Interactions
    • 5.1.4. Loosely Coupled Interfaces
    • 5.1.5. N-Squared Data Formats: Its Really About the Data Transformations
    • 5.1.6. Get on the Bus
    • 5.1.7. Loosely Coupled Web Services Standards
  • 5.2. MOM Concepts
    • 5.2.1. Abstract Decoupling
    • 5.2.2. Messaging Models: Publish-and-Subscribe and Point-to-Point
    • 5.2.3. Topic Hierarchies
    • 5.2.4. Access Control Lists (ACLs)
    • 5.2.5. Whats in a Message?
  • 5.3. Asynchronous Reliability
    • 5.3.1. Message Autonomy
    • 5.3.2. Store and Forward
    • 5.3.3. Message Persistence
    • 5.3.4. Message Acknowledgments
  • 5.4. Reliable Messaging Models
    • 5.4.1. Reliable Publish-and-Subscribe
    • 5.4.2. Reliable Point-to-Point Queues
    • 5.4.3. Store-and-Forward Across Multiple Message Servers
  • 5.5. Transacted Messages
    • 5.5.1. Local Transactions
    • 5.5.2. Transactions with Multiple Resources
    • 5.5.3. An ESB Removes the Low-Level Complexities
  • 5.6. The Request/Reply Messaging Pattern
    • 5.6.1. The Reply-Forward Pattern
  • 5.7. Messaging Standards
    • 5.7.1. The Java Message Service (JMS)
      • 5.7.1.1. What about the J in JMS?
    • 5.7.2. Reliable Messaging with SOAP
    • 5.7.3. Web Services Events and Notifications
  • 5.8. Summary
• 6. Service Containers and Abstract Endpoints
  • 6.1. SOA Through Abstract Endpoints
  • 6.2. Messaging and Connectivity at the Core
  • 6.3. Diverse Connection Choices
  • 6.4. Diagramming Notations
  • 6.5. Independently Deployable Integration Services
  • 6.6. The ESB Service Container
    • 6.6.1. The Management Interface of the Service Container
    • 6.6.2. The ESB Service Interface
    • 6.6.3. Auditing, Logging, and Error Handling
    • 6.6.4. ESB Service Container Facilities
      • 6.6.4.1. QoP and QoS
      • 6.6.4.2. Administration of ESB facilities
    • 6.6.5. Standardizing ESB Container Connectivity
  • 6.7. Service Containers, Application Servers, and Integration Brokers
    • 6.7.1. Adherence to Standards
    • 6.7.2. Centralized Hub-and-Spoke Processing
    • 6.7.3. Whats Hosted in the Container
    • 6.7.4. Management Substrate
    • 6.7.5. Compiled Class Files Versus Declarative Rules
    • 6.7.6. Abandon Application Servers?
  • 6.8. Summary
• 7. ESB Service Invocations, Routing, and SOA
  • 7.1. Find, Bind, and Invoke
  • 7.2. ESB Service Invocation
  • 7.3. Itinerary-Based Routing: Highly Distributed SOA
  • 7.4. Content-Based Routing (CBR)
    • 7.4.1. Conditional Routing Using BPEL4WS
  • 7.5. Service Reusability
    • 7.5.1. Parameterization and Configuration
    • 7.5.2. Reuse via Composition
  • 7.6. Specialized Services of the ESB
    • 7.6.1. Routing Patterns Using Itineraries and Services
    • 7.6.2. Sophisticated Process Flow Using an Orchestration Service (BPEL4WS)
      • 7.6.2.1. Recovery of process state
      • 7.6.2.2. Correlation of asynchronous conversations
      • 7.6.2.3. BPEL4WS for scripting of orchestration services
    • 7.6.3. XML Storage and Caching Services
      • 7.6.3.1. Data caching
      • 7.6.3.2. Aggregation and reporting
      • 7.6.3.3. Implementation choices
    • 7.6.4. Convergence in Process Modeling
  • 7.7. Summary
• 8. Protocols, Messaging, Custom Adapters, and Services
  • 8.1. The ESB MOM Core
    • 8.1.1. MOM Interoperability
    • 8.1.2. The 80/20 Rule of MOM Backbone Versus External Protocols
  • 8.2. A Generic Message Invocation Framework
    • 8.2.1. Protocol Bridging
    • 8.2.2. MOM Bridging
    • 8.2.3. Direct Protocol Handlers
      • 8.2.3.1. Synchronous request/reply: invoking an ESB service via HTTP
      • 8.2.3.2. Asynchronous request/reply
    • 8.2.4. SOAP Protocol Handler
    • 8.2.5. Where Do Asynchronous Errors Go?
  • 8.3. Case Study: Partner Integration
    • 8.3.1. Secure DMZ Deployment
    • 8.3.2. Availability To Promise (ATP)
    • 8.3.3. The SAP Adapter: A Custom ESB Service
    • 8.3.4. EDI Transportation and Transformation
    • 8.3.5. Removing the Dependency on the EDI VAN
    • 8.3.6. Looking Ahead
  • 8.4. Summary
• 9. Batch Transfer Latency
  • 9.1. Drawbacks of ETL
    • 9.1.1. ETL Reliability and Data Validity
    • 9.1.2. Undesired Downtime and the Logistics of Data Synchronization
    • 9.1.3. Overall Latency of Data Gathering
  • 9.2. The Typical Solution: Overbloat the Inventory
  • 9.3. Case Study: Migrating Toward Real-Time Integration
    • 9.3.1. Inserting the ESB
    • 9.3.2. Transforming and Routing the Data
      • 9.3.2.1. Structured message channels
      • 9.3.2.2. Assigning process definitions
    • 9.3.3. Considerations
      • 9.3.3.1. Streamlined data flow
      • 9.3.3.2. Migrating to XML
      • 9.3.3.3. Message-based atomicity
      • 9.3.3.4. Think asynch
      • 9.3.3.5. Removing the file interface
  • 9.4. Summary
• 10. Java Components in an ESB
  • 10.1. Java Business Integration (JBI)
    • 10.1.1. JBI as an ESB Container
    • 10.1.2. JBI and Other Java Specifications
  • 10.2. The J2EE Connector Architecture (JCA)
    • 10.2.1. Domain Expertise
    • 10.2.2. ESB to Application Server Connectivity
  • 10.3. Java Management eXtensions (JMX)
    • 10.3.1. A JMX Primer
      • 10.3.1.1. JMX server environment
      • 10.3.1.2. JMX client protocol adapters
      • 10.3.1.3. JMX connector interface
      • 10.3.1.4. JMX MBean interfaces
    • 10.3.2. JMX Management in an ESB Architecture
    • 10.3.3. JMX-Managed Components in an ESB
    • 10.3.4. Directory Cache
    • 10.3.5. Template-Based Remote Configuration Replication
  • 10.4. Summary
• 11. ESB Integration Patterns and Recurring Design Solutions
  • 11.1. The VETO Pattern
    • 11.1.1. Variations: The VETRO Pattern
  • 11.2. The Two-Step XRef Pattern
  • 11.3. Portal Server Integration Patterns
    • 11.3.1. The Portal Server Deployment Architecture
    • 11.3.2. Portal Server Challenges
      • 11.3.2.1. Synchronous sequential aggregation
      • 11.3.2.2. Web services
      • 11.3.2.3. Concurrency via multithreaded request
      • 11.3.2.4. Long-duration conversation management
      • 11.3.2.5. Asynchrony and reliability using JMS
      • 11.3.2.6. Connectivity using application adapters
    • 11.3.3. Inserting an ESB as the Integration Backbone
  • 11.4. The Forward Cache Integration Pattern
    • 11.4.1. Data Forwarding Using Publish-and-Subscribe
    • 11.4.2. Data Forwarding Using Itinerary-Based Routing
    • 11.4.3. Other Considerations of the Forward Cache Pattern
      • 11.4.3.1. Integration first, portal second
  • 11.5. Federated Query Patterns
    • 11.5.1. Cache Push Versus Pull Patterns
    • 11.5.2. The Real-Time Request Pattern
    • 11.5.3. The Long-Duration Request Pattern
    • 11.5.4. Federated Query Pattern Variations
      • 11.5.4.1. Federated query using itinerary processes
      • 11.5.4.2. Federated query using BPEL4WS and an orchestration service
  • 11.6. Summary
• 12. ESB and the Evolution of Web Services
  • 12.1. Composability Among Specifications
  • 12.2. Summary of WS-* Specifications
  • 12.3. Adopting the WS-* Specifications in an ESB
    • 12.3.1. WS-* Does Not Imply Enterprise Capabilities
    • 12.3.2. WS-* Does Not Imply ESB
  • 12.4. Conclusion
• A. Appendix: List of ESB Vendors
• 13. Bibliography
  • Analyst Reports
  • Books
  • Miscellaneous
  • Web Services Specifications
  • Java Specifications
• Index
• About the Author
• Colophon
• Copyright