Enterprise integration allows organizations to integrate applications, databases, and legacy systems involved in critical business processes. Two scenarios were presented - with little integration where systems function independently, and complete integration where systems are interoperable through common formats and granular standards. The document discusses an integration vision, value of integration through improved speed, costs and sustainability. It presents different integration types including point-to-point, messaging and enterprise service bus, outlining their pros and cons. Finally, it questions how ACME can approach integration through styles, available systems, binding, message construction, routing, transformation and management.

1. Enterprise Integration
 CWade80292@gmail.com

2. Discussion Points
 What is Enterprise Integration?
 How the business models works (2 Scenarios)
 An Integration Vision
 Value of Enterprise Integration
 Setting the Integration Context
 Types of Integration
 What We Have at ACME
 How Patterns Work
 Questions to be Asking

3. What is Enterprise Integration?
integrate the application programs, databases, and legacy
systems involved in an organization's critical business
processes.
Node A Node B
Purchasing
Process
Receiving
Process
Data/
Functionality
Data/
Functionality
XML XML
Organization

4. How the business model works ( Scenario 1, Little Integration)
App
System
Business
Process
Users
App
System
Business
Process
Users
App
System
Business
Process
Users
- It Works To Define
and Solve Specific
Problems
- Companies and
Government are good
at this!

5. How the business model works (Scenario 2, Complete
Integration)
LOB 2
Suppliers/
Partners
Customers
VALUE
LOB 1 LOB 3
Corporate
Enterprise
Business Strategy
Stressed interoperability
Stressed integration
Included the process
Common Formats
Invoked granular
standards
Reduced Redundancy

6. An Integration Vision
Building a Foundation For Execution
6
Assembled-to-order application
During the requirements phase, it
is determined that re-usable
business services 1, 3 and 4 can
be reused by coupling them in the
order of the business process as
Service 4, 2 , and Service 1.
Service X will be the only service
that will have to be developed.
Four re-usable business
services that are ready for use
and loosely coupled. Note that
there is no connection between
them. They are also catalogued
and accessible.
Making the assumption that each service is the same amount of work to deploy, we
reduced our development effort by 75% through re-use of business services.
Services are platform independent
Service 1 Service 2 Service 3 Service 4Service 1 Service 2
Service X
Service 4

7. Enterprise Integration Value
Benefit Value Achieved
Speed to production 25% Improvement
Development Costs 33% Improvement
Efficiency 25% Improvement
Sustain Costs 60% Improvement*
ROI Crossover 22 months projected
19 months actual
A Real Example From A Very Large Company.
*Projected, not yet calculated

8. Setting the Integration Context
We have 5 systems that must be integrated. For our purpose, they
will each be referred to as a node.
We will use these 5 nodes to discover and evaluate various types of
enterprise integration
NOTE: WE HAVE ALL TYPES OF INTEGRATION, AS MOST
LARGE ORGANIZATION DO. THE RIGHT ONE TO USE IS
SITUATIONAL. NO SINGLE ANSWER WORKS ALL THE TIME.

9. Point to Point Integration

10. P2P Summary
PRO CON
Easy to Implement Becomes difficult to manage
Years of legacy Deployment Requires large upgrades
Fast Inflexible
Cheap (at first) Usually not fault tolerant

11. Messaging Integration

12. How Messaging Works

13. Messaging Summary
PRO CON
Starts to hide Complexity Still hidden P2P
Message transformation Not very flexible
Basic Manageability May Be Difficult to absorb change
Platform Agnostic Not typically event driven

14. Thinking Different with a Service Bus
Business Services were specific business process
services
Audience: Business
Effect Category: Revenue/Cost/Time
Presented as Business Processes
Common Business Service are things everybody used
and just needed configuration
Audience: CFO/CIO
Effect Category: Expense/Time
Presented as a normalized set of services
IT Service was background IT processes that just
happened
Audience: CIO/CFO
Effect Category: Expense/Time
Presented as a time saver for IT

15. Enterprise Service Bus Integration

16. How an ESB Works

17. Application Patterns & Transformation Illustrated
17
Simple Object Access Protocol
(SOAP) - a protocol specification for exchanging
structured information in the implementation of
Web Services
Representational State Transfer (REST) – a
style of software architecture for distributed
hypermedia systems such as the World Wide Web
Java Native Interface (JNI) - Java programming
interface, or API, that allows developers to access
the languages of a host system and determine the
way Java integrates with native code.
Raw native Interface (RNI) - programming
interface in Microsoft's Java Virtual Machine used
for calling native Windows elements such as GUI
routines

18. Service Bus Summary
PRO CON
Very Flexible Disruptive to Deploy
Scalable Requires Specific Skills
Assured Delivery Investment Required
Potentially HUGE ROI Difficult Start Up

19. What We Have At ACME
ESB In Development
*Other GM Areas are
using this in semi-
production

20. How Patterns Work & Fit

21. Questions To Be Asking
What to think about:
1. How can I do Integration? (Styles) (Last)
2. What kind of systems are available to me? (Systems)
3. How do we bind? (Channels)
4. How do we make a message? (Construction)
5. Where do we send the message? (Routing)
6. How do we translate the message? (Transformation)
7. Where do messages start and stop? (End Points)
8. How do we mange this? (System Management)