Jess Thompson

1
Enterprise Nervous System Lifeblood of
Integration

• Jess Thompson

2
Archipelagos of Integration or One Enterprise
Nervous System?
Microsoft Archipelago
Custom Legacy
.Net App 1
.Net
New Package
.Net App 2
Packaged Legacy
.Net App 3
3
Key Issues
1. What will be the benefits and limitations of
the three major migration strategies
rip-and-replace, wrap-and-re-engineer and
leave-and-layer? 2. How will the spread of
integration technology to application servers,
application platform suites, packaged
applications and enterprise service buses affect
the adoption and management of integration
suites? 3. Which integration approaches will have
a durable impact on enterprise business
strategies and which will be discarded as dead
ends?
4
Key Issues
1. What will be the benefits and limitations of
the three major migration strategies
rip-and-replace, wrap-and-re-engineer and
leave-and-layer?
5
Conventional Application Integration Spaghetti
6
Three Possible 'Antidotes' to the Problems of IS
Heterogeneity

• Rip-and-replace
• Wrap-and-re-engineer
• Leave-and-layer

7
Rip-and-Replace Theory
Network
8
Rip-and-Replace Reality
Legacy
Purchased Package
Outside Virtual Enterprise
Outsourced
Independent Subsidiary
Ad Hoc
Has Not Heard of Architecture
9
Wrap-and-Re-engineer Theory
New SOA Application Set
Product
Wrapped Legacy Application
Customer
Network
Portal
Call Center
Employee
Wrapped Packaged Application
10
Wrap-and-Re-engineer Reality
New SOA Application Set
Product
Customer
Wrapped Legacy Application
Customer
Network
Portal
Call Center
Employee
Customer
Wrapped Packaged Application
11
Leave-and-Layer Integration
Enterprise Nervous System
12
Key Issues
1. What will be the benefits and limitations of
the three major migration strategies
rip-and-replace, wrap-and-re-engineer and
leave-and-layer? 2. How will the spread of
integration technology to application servers,
application platform suites, packaged
applications and enterprise service buses affect
the adoption and management of integration suites?
13
Traditional Networks Move Data but Do No
Application Logic
Pub-Sub Message
File Transfer
COM, CORBA, RMI, RPC, SOAP
Enterprise Network FTP, HTTP, MOM, SMTP, TCP/IP
E-mail
Sockets Dialog
14
Enterprise Nervous System Enables Leave and
Layer Design
Enterprise Nervous System
Enterprise Network FTP, HTTP, MOM, SOAP, TCP/IP
Integration Metadata
Message Warehouse
Operational Data Store
Data Warehouse
15
Integration Technology Proliferates
16
Integration Technology Aligned With One
Application Server or Neutral
17
Integration Broker Adoption Rate
No Integration Broker
100
80
60
Percent of Projects
40
20
0
2002
2003
2006
2005
2004
18
Key Issues
1. What will be the benefits and limitations of
the three major migration strategies
rip-and-replace, wrap-and-re-engineer and
leave-and-layer? 2. How will the spread of
integration technology to application servers,
application platform suites, packaged
applications and enterprise service buses affect
the adoption and management of integration
suites? 3. Which integration approaches will have
a durable impact on enterprise business
strategies and which will be discarded as dead
ends?
19
Application Integration Technology Hype Cycle
20
Integration Competency Center
21
Recommendations

• An integration strategy should be a mix of
  rip-and-replace, wrap-and-re-engineer and
  leave-and-layer.
• Where new application platforms will be
  heterogeneous, integration technology should be
  application-server-neutral.
• Where one packaged application or application
  server will dominate an enterprise,
  one-stop-shopping integration tools will be
  appropriate.
• Enterprises should design and manage their ENSs
  through a central integration competency center
  not by multiple application-centric teams.
• Enterprises should prepare to gradually migrate
  from an application-out integration approach to a
  bus-in integration approach.

22
Enterprise Nervous System Lifeblood of
Integration

• Jess Thompson

23
Enterprise Nervous System Lifeblood of
Integration

• Jess Thompson