book

Enterprise Service Bus

Name: Enterprise Service Bus
Author: David A Chappell
ISBN: 9781449391096

by David A Chappell

June 2004

Intermediate to advanced

276 pages

15h 17m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Enterprise Service Bus
A Note Regarding Supplemental Files
Foreword
Preface
About This BookOverview of the ChaptersNotational Conventions for ESB Integration PatternsDiagramming NotationsConventions Used in This BookWe’d Like to Hear from YouAcknowledgments
1. Introduction to the Enterprise Service Bus
1.1. SOA in an Event-Driven Enterprise1.2. A New Approach to Pervasive Integration1.3. SOA for Web Services, Available Today1.4. Conventional Integration Approaches1.5. Requirements Driven by IT Needs1.6. Industry Traction1.6.1. Vendors Adopting the ESB1.7. Characteristics of an ESB1.7.1. Pervasiveness1.7.2. Standards-Based Integration1.7.3. Highly Distributed Integration and Selective Deployment1.7.4. Distributed Data Transformation1.7.5. Extensibility Through Layered Services1.7.6. Event-Driven SOA1.7.7. Process Flow1.7.8. Security and Reliability1.7.9. Autonomous but Federated Environment1.7.10. Remote Configuration and Management1.7.11. XML as the “Native” Datatype of the ESB1.7.12. Real-Time Throughput of Business Data1.7.13. Operational Awareness1.7.14. Incremental Adoption1.8. Adoption of ESB by Industry1.8.1. Financial Services1.8.2. Insurance1.8.3. Manufacturing1.8.4. Retail1.8.5. Telecom1.8.6. Energy/Utility1.8.7. Food Distribution Network1.8.8. Government1.9. Summary
2. The State of Integration
2.1. Business Drivers Motivating Integration2.1.1. IT Spending Trends2.1.2. Integration as a High-Ranking Priority2.1.3. Regulatory Compliance2.1.3.1. Telecom2.1.3.2. Sarbanes-Oxley2.1.3.3. Government2.1.4. Straight-Through Processing (STP)2.1.5. Radio Frequency Identification (RFID)2.2. The Current State of Enterprise Integration2.2.1. The Enterprise Is Not Well Connected2.2.2. The Accidental Architecture2.2.2.1. Departmental and organizational issues2.2.2.2. Moving forward with an accidental architecture2.2.3. ETL, Batch Transfers, and FTP2.2.4. Integration Brokers2.3. Leveraging Best Practices from EAI and SOA2.3.1. Adopt XML2.3.2. Adopt Web Services and Implement SOA2.4. Refactoring to an ESB2.4.1. Introduce the ESB at an Individual Project Level2.4.2. Propagate the ESB Across a Widely Distributed Enterprise2.4.3. Leave and Layer: Connecting into the Existing EAI Broker2.4.4. Partner Integration2.5. Summary
3. Necessity Is the Mother of Invention
3.1. The Evolution of the ESB3.2. The ESB in Global Manufacturing3.2.1. Putting It to the Test3.3. Finding the Edge of the Extended Enterprise3.3.1. e-Commerce Trading Hubs3.3.2. The Extended Enterprise: The Ever-Changing Edge3.3.3. Corralling the Ever-Changing Edge of the Network3.4. Standards-Based Integration3.4.1. The New Economics of Integration3.4.2. Driving Down the Cost of Technology3.5. Case Study: Manufacturing3.5.1. Building a Real-Time Business3.5.1.1. Inventory management3.5.1.2. Technical challenges3.5.1.3. Availability To Promise (ATP)3.5.2. Flexible Partner Integration3.6. Summary
4. XML: The Foundation for Business Data Integration
4.1. The Language of Integration4.1.1. XML Is Human-Readable4.2. Applications Bend, but Don’t Break4.3. Content-Based Routing and Transformation4.4. A Generic Data Exchange Architecture4.4.1. Data Translation to and from a Canonical Format4.4.2. Adopting a Canonical Data Exchange4.4.3. Alternate Approaches4.5. Summary
5. Message Oriented Middleware (MOM)
5.1. Tightly Coupled Versus Loosely Coupled Interfaces5.1.1. Remote Procedure Call (RPC)-Style Programming5.1.2. Tightly Coupled Interfaces5.1.3. Loosely Coupled Interactions5.1.4. Loosely Coupled Interfaces5.1.5. N-Squared Data Formats: It’s Really About the Data Transformations5.1.6. Get on the Bus5.1.7. Loosely Coupled Web Services Standards5.2. MOM Concepts5.2.1. Abstract Decoupling5.2.2. Messaging Models: Publish-and-Subscribe and Point-to-Point5.2.3. Topic Hierarchies5.2.4. Access Control Lists (ACLs)5.2.5. What’s in a Message?5.3. Asynchronous Reliability5.3.1. Message Autonomy5.3.2. Store and Forward5.3.3. Message Persistence5.3.4. Message Acknowledgments5.4. Reliable Messaging Models5.4.1. Reliable Publish-and-Subscribe5.4.2. Reliable Point-to-Point Queues5.4.3. Store-and-Forward Across Multiple Message Servers5.5. Transacted Messages5.5.1. Local Transactions5.5.2. Transactions with Multiple Resources5.5.3. An ESB Removes the Low-Level Complexities5.6. The Request/Reply Messaging Pattern5.6.1. The Reply-Forward Pattern5.7. Messaging Standards5.7.1. The Java Message Service (JMS)5.7.1.1. What about the “J” in JMS?5.7.2. Reliable Messaging with SOAP5.7.3. Web Services Events and Notifications5.8. Summary
6. Service Containers and Abstract Endpoints
6.1. SOA Through Abstract Endpoints6.2. Messaging and Connectivity at the Core6.3. Diverse Connection Choices6.4. Diagramming Notations6.5. Independently Deployable Integration Services6.6. The ESB Service Container6.6.1. The Management Interface of the Service Container6.6.2. The ESB Service Interface6.6.3. Auditing, Logging, and Error Handling6.6.4. ESB Service Container Facilities6.6.4.1. QoP and QoS6.6.4.2. Administration of ESB facilities6.6.5. Standardizing ESB Container Connectivity6.7. Service Containers, Application Servers, and Integration Brokers6.7.1. Adherence to Standards6.7.2. Centralized Hub-and-Spoke Processing6.7.3. What’s Hosted in the Container6.7.4. Management Substrate6.7.5. Compiled Class Files Versus Declarative Rules6.7.6. Abandon Application Servers?6.8. Summary

7. ESB Service Invocations, Routing, and SOA
7.1. Find, Bind, and Invoke7.2. ESB Service Invocation7.3. Itinerary-Based Routing: Highly Distributed SOA7.4. Content-Based Routing (CBR)7.4.1. Conditional Routing Using BPEL4WS7.5. Service Reusability7.5.1. Parameterization and Configuration7.5.2. Reuse via Composition7.6. Specialized Services of the ESB7.6.1. Routing Patterns Using Itineraries and Services7.6.2. Sophisticated Process Flow Using an Orchestration Service (BPEL4WS)7.6.2.1. Recovery of process state7.6.2.2. Correlation of asynchronous conversations7.6.2.3. BPEL4WS for scripting of orchestration services7.6.3. XML Storage and Caching Services7.6.3.1. Data caching7.6.3.2. Aggregation and reporting7.6.3.3. Implementation choices7.6.4. Convergence in Process Modeling7.7. Summary
8. Protocols, Messaging, Custom Adapters, and Services
8.1. The ESB MOM Core8.1.1. MOM Interoperability8.1.2. The 80/20 Rule of MOM Backbone Versus External Protocols8.2. A Generic Message Invocation Framework8.2.1. Protocol Bridging8.2.2. MOM Bridging8.2.3. Direct Protocol Handlers8.2.3.1. Synchronous request/reply: invoking an ESB service via HTTP8.2.3.2. Asynchronous request/reply8.2.4. SOAP Protocol Handler8.2.5. Where Do Asynchronous Errors Go?8.3. Case Study: Partner Integration8.3.1. Secure DMZ Deployment8.3.2. Availability To Promise (ATP)8.3.3. The SAP Adapter: A Custom ESB Service8.3.4. EDI Transportation and Transformation8.3.5. Removing the Dependency on the EDI VAN8.3.6. Looking Ahead8.4. Summary
9. Batch Transfer Latency
9.1. Drawbacks of ETL9.1.1. ETL Reliability and Data Validity9.1.2. Undesired Downtime and the Logistics of Data Synchronization9.1.3. Overall Latency of Data Gathering9.2. The Typical Solution: Overbloat the Inventory9.3. Case Study: Migrating Toward Real-Time Integration9.3.1. Inserting the ESB9.3.2. Transforming and Routing the Data9.3.2.1. Structured message channels9.3.2.2. Assigning process definitions9.3.3. Considerations9.3.3.1. Streamlined data flow9.3.3.2. Migrating to XML9.3.3.3. Message-based atomicity9.3.3.4. Think asynch9.3.3.5. Removing the file interface9.4. Summary
10. Java Components in an ESB
10.1. Java Business Integration (JBI)10.1.1. JBI as an ESB Container10.1.2. JBI and Other Java Specifications10.2. The J2EE Connector Architecture (JCA)10.2.1. Domain Expertise10.2.2. ESB to Application Server Connectivity10.3. Java Management eXtensions (JMX)10.3.1. A JMX Primer10.3.1.1. JMX server environment10.3.1.2. JMX client protocol adapters10.3.1.3. JMX connector interface10.3.1.4. JMX MBean interfaces10.3.2. JMX Management in an ESB Architecture10.3.3. JMX-Managed Components in an ESB10.3.4. Directory Cache10.3.5. Template-Based Remote Configuration Replication10.4. Summary
11. ESB Integration Patterns and Recurring Design Solutions
11.1. The VETO Pattern11.1.1. Variations: The VETRO Pattern11.2. The Two-Step XRef Pattern11.3. Portal Server Integration Patterns11.3.1. The Portal Server Deployment Architecture11.3.2. Portal Server Challenges11.3.2.1. Synchronous sequential aggregation11.3.2.2. Web services11.3.2.3. Concurrency via multithreaded request11.3.2.4. Long-duration conversation management11.3.2.5. Asynchrony and reliability using JMS11.3.2.6. Connectivity using application adapters11.3.3. Inserting an ESB as the Integration Backbone11.4. The Forward Cache Integration Pattern11.4.1. Data Forwarding Using Publish-and-Subscribe11.4.2. Data Forwarding Using Itinerary-Based Routing11.4.3. Other Considerations of the Forward Cache Pattern11.4.3.1. Integration first, portal second11.5. Federated Query Patterns11.5.1. Cache Push Versus Pull Patterns11.5.2. The Real-Time Request Pattern11.5.3. The Long-Duration Request Pattern11.5.4. Federated Query Pattern Variations11.5.4.1. Federated query using itinerary processes11.5.4.2. Federated query using BPEL4WS and an orchestration service11.6. Summary
12. ESB and the Evolution of Web Services
12.1. Composability Among Specifications12.2. Summary of WS-* Specifications12.3. Adopting the WS-* Specifications in an ESB12.3.1. WS-* Does Not Imply Enterprise Capabilities12.3.2. WS-* Does Not Imply ESB12.4. Conclusion
A. Appendix: List of ESB Vendors
13. Bibliography
Analyst ReportsBooksMiscellaneousWeb Services SpecificationsJava Specifications
Index
About the Author
Colophon
Copyright

Content preview from Enterprise Service Bus

Chapter 13. Bibliography

Analyst Reports

Gartner Predicts: 2003 (DF-18-7304). http://www.gartner.com. (Quote from Roy Schulte in Chapter 1)

Gartner Predicts: 2004 (118991). “Enterprise Service Buses are Taking Off.” http://www.gartner.com.

IDC. The Enterprise Service Bus: Disruptive Technology for Software Infrastructure Solutions (Document #29132). http://www.idc.com/getdoc.jsp?containerId=29132.

IDC. Integration Standards Trends in Program Development: It All Depends on What the Meaning of “Open” Is (Document #30365). November 2003. http://www.idc.com/.

Books

Alexander, Christopher et al. A Pattern Language: Towns, Buildings, Construction. Oxford University Press, 1977.

Fowler, Martin. Patterns of Enterprise Application Architecture. Addison Wesley, 2002.

Hohpe, Gregor and Bobby Woolf. Enterprise Integration Patterns. 2004. Pearson Education, Inc. Figures: Aggregator, p.268; Content-Based Router, p.230; Control Bus, p.540; Message Broker, p.322; Message Channel, p.60; Publish-Subscribe Channel, p.106; Routing Slip, p.301; Splitter, p.259. © Reprinted by permission of Pearson Education, Inc. Publishing as Pearson Addison Wesley.

Kaye, Doug. Loosely Coupled: The Missing Pieces of Web Services. RDS Press, 2003.

Kreger, Heather, Ward K. Harold, and Leigh Williamson. Java and JMX: Building Manageable Systems. Addison Wesley, 2002.

Monson-Haefel, Richard and David A. Chappell. Java Message Service. O’Reilly, 2000.

Miscellaneous

The CIO Council’s XML Web Services Working Group “Kickoff Presentation” ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Hybrid Cloud Event Integration: Integrate Your Enterprise and Cloud with Bluemix Integration Services

Publisher Resources

ISBN: 0596006756Errata Page

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business