Simplifying EAI - PowerPoint PPT Presentation

About This Presentation
Title:

Simplifying EAI

Description:

Fort Software Inc. paul_at_forte.com. HPTS 99. 2. HPTS 99 ... The best bet for interoperability. Component Assembly for faster integration and development ... – PowerPoint PPT presentation

Number of Views:54
Avg rating:3.0/5.0
Slides: 14
Provided by: SoftWi
Category:
Tags: eai | simplifying

less

Transcript and Presenter's Notes

Title: Simplifying EAI


1
Simplifying EAI
HPTS 99
  • Paul Butterworth
  • Forté Software Inc.
  • paul_at_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
Whats Hard in EAI?
  • Hooking up the applications - they dont 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
Forté Fusion Architecture
Forté Fusion Backbone
8
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
  • Lots of applications
  • Lots of infrastructure
  • Lots of machines
  • Lots of communications
  • What doesnt go wrong?

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

13
Summary
  • Its more than just messaging
  • Tools for
  • Development
  • Mapping
  • Assembly
  • Deployment
  • Operations
Write a Comment
User Comments (0)
About PowerShow.com