1 / 13

Simplifying EAI

Simplifying EAI. HPTS 99. Paul Butterworth Forté Software Inc. paul@forte.com. Integrate and Develop. “Extended” and “Composite” Applications Generally involve pulling together many of the functional systems within your environment -- Integrate

temima
Download Presentation

Simplifying EAI

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Simplifying EAI HPTS 99 Paul Butterworth Forté Software Inc. paul@forte.com

  2. Integrate and Develop • “Extended” and “Composite” Applications • Generally involve pulling together many of the functional systems within your environment --Integrate • Combine existing functional systems with new functions -- Develop • Deploy these to new audiences (customers and partners) -- Develop

  3. What’s Hard in EAI? • Hooking up the applications - they don’t want to be integrated. • No interfaces • Batch systems • getting confirmation • screen scraping • Settling on or converting data representations • Recovering from errors • Managing performance

  4. Too Many Moving Parts • Applications • Transformations • Interfaces • Messaging • Web • App Servers • DBMSs

  5. Two Types of Integration • Tightly-coupled Components • CORBA, COM, Java models • Generally Synchronous • Loosely-coupled Components • Applications and Packages • Generally Asynchronous • Both Required in Most Systems

  6. How do we simplify EAI? • Process-based Integration • The business value is in automating the process (particularly in web applications) not in the plumbing. • XML Data Interchange • The best bet for interoperability • Component Assembly for faster integration and development • TOOL • Java • COM and CORBA • “One Button Run”

  7. Integration Logic Process Automation Process Logic LegacyApp CustomApp Packaged App Component Develop & Deploy Functional Logic Technology Integration Forté Fusion Architecture Forté Fusion Backbone

  8. Forté Fusion Fusion Manager Process manager Application Proxy Application Proxy Application Proxy Rule Base (XSL) Connector Connector XML messages Native XML API (e.g C++) API (e.g Java) Application e.g. Credit Check Application e.g. Inventory Application e.g. Shipping Forté Fusion Components

  9. Who Owns the Business Data? • EAI framework holds a bunch of business data. • Business wants access to it. • EAI framework is now in the database business. • Some of the state (state of the process/message) must be there.

  10. Performance • A bunch of disparate applications • Many layers of software • Implications: • Too many requests • Too many translations • Too many failures (see next issue)

  11. Keeping This Mess Running • Lot’s of applications • Lot’s of infrastructure • Lot’s of machines • Lot’s of communications • What doesn’t go wrong?

  12. Who Worries About the Boring Stuff? • Installing new versions of software • Compatibility • System management • Footprint

  13. Summary • It’s more than just messaging • Tools for • Development • Mapping • Assembly • Deployment • Operations

More Related