Concept Five Technologies Inc.

1
Concept Five Technologies Inc.
Enterprise Application Integration
PresentationForEAIWG

• Jon Hanshew, Chief Technical Architect EAI
  Solutions
• Electronic Data Systems, Inc.
• 180 Montgomery St. Suite 600
• San Francisco, CA. 94104
• 415-228-6068 FAX [phone]
• jhanshew_at_shl.com

1
2
Agenda

• What We Do
• Middleware EAI Infrastructure Costs and Benefits
• Open Standards and EAI

3
Frameworks
4
Yet Another Framework
Increasing Business Value
Data Synchronization
5
Things Heard from Prospects

• Our IT environment is a mess. Nothing talks to
  anything else
• We have to fix our infrastructure, but we do not
  have time to do it with this project
• We have to cut costs. We hate to do it, but we
  cannot afford to build an EAI infrastructure for
  this project

6
Things Heard from Vendors

• Our product allows you to integrate applications
  with no programming at all.
• Our product will pay for itself in the first
  project.
• Its always cheaper to use middleware

7
What is the Reality?
8
App-to-App vs. Middleware Architectures
IT Reality Composite Applications
9
What is the General Casefor Pt-to-Pt?
Each Application has N-1 One Way Interfaces with
Other Applications
10
Order N2 is ReallyN(N-1)
N Applications with (N-1) One Way
Interfaces Yield N(N-1) Total
Possible Interfaces
11
Order N is Really2N
Each of the N Applications Has 2 One
Way Interfaces Making for a Total of 2N Total
Possible Interfaces
12
Break Even Point is 3 Appsor 6 Interfaces
13
Preliminary Conclusion

• The installation of an EAI infrastructure cannot
  be cost justified on a single project basis
  unless the project requires
• More Than Six Interapplication Interfaces

14
But Wait! the Vendors Say
What About Prebuilt Adapters?
15
If Prebuilt Adapters Take25 the Effort of a
Custom...
16
Penultimate Conclusions

• Assuming that building an interface using
  prebuilt adapters takes 25 (or less) of the
  effort of a custom interface
• Prebuilt adapters are a big win if they exist.
• EAI infrastructure costs may be cost justified
  for as few as two applications.
• Retrofitting an EAI infrastructure into an
  environment of custom legacy applications will
  continue to be expensive.
• Cost justifying EAI for a single project in a
  legacy environment will continue to be difficult

17
Other Additional Costs

• Learning Curve - The new vendor tools will have
  to be learned by all developers. This will cost
  time and money.
• Software Costs - They arent giving the stuff
  away yet.

18
Ultimate Conclusion

• The break even point for a pure legacy custom
  application environment is probably closer to
  five applications because of the additional costs

19
How to Justify the Additional Costs

• Reducing Opportunity Costs
• Inflexible Point-to-Point systems need to be
  replaced more frequently
• Inflexible systems tie up skilled staff
• Reducing Maintenance Costs - It is easier to add
  or change functionality in middleware environment

20
How Is Interface Simplification Achieved?
Adapters translate between external data
formats and the middlewares data format
To achieve maximum simplification, all
middleware should use same data format
Data in common format
EAI vendors provide platform integration and
messaging into the common environment
EDS believes an excellent choice for a common
data format is XML
Order (N) - Interfaces
21
What Happens With Two Brokers?
The first step is to add an interbroker adapter
If performance is not acceptable then more
adapters will be needed
The interface count is now 2n2
The interface count is now 2n4, 2n6, and we
are headed back to point-to-point
Broker B
Broker A
Order (N) - Interfaces
22
Conclusion
The Benefits of a Middleware BasedEAI
InfrastructureDerive FromHaving a Single
SuchEnvironment
23
Agenda

• Middleware EAI Infrastructure Costs and Benefits
• Open Standards and EAI

24
Question
Will Open StandardsTurn ProprietaryMessage
BrokersInto LegacyMiddleware Environments?
25
Middleware Tool Evolution
Autonomous Monolithic Applications Stovepipes
Multi-Step Processes Content Based Routing
Data Synchronization Data Replication, Publish
Subscribe

• Autonomous
• Distributed
• Applications
• EJB, CORBA

Composite Applications Processware
26
Feature Comparison
27
Yet Another Observation...
EAI Tools Based on Open Standards that Provide
Content Based Routing and Processware Services
Should Do Well
28
Candidate Technical Architecture
Co-ordination Infrastructure
Process Automation Engine
XML
IIOP
XML
Integration Infrastructure
CORBA Object
Message Broker
Request
Broker
HTTP/XML
MOM
IIOP
Adapter
Adapter
Adapter
BAAN
Vantive
Valex
?????
Provisioning
Billing
FrontOffice
Packaged Applications
Applications
Legacy

New

Custom Adapter
Prebuilt Adapter
Adapter
29


www.eds.com