Enterprise Application Integration Styles

1
Enterprise Application Integration Styles

• Phong Nguyen Thanh
• Muhammad Usman Khokhar

2
Agenda

• Introduction
• Overview of current EAI technologies
• Evolutions in EAI Styles

3
Background

• Large amount of software resources and there
  integration is a fundamental part in todays
  rapidly changing environment.
• Early systems were designed to run independently
  as individual components with no interaction
  between them.
• Forester Research estimate that 30 of the
  fortune 1000 companys IT budget (over 100
  billion) is being spent linking the systems
  together.

4
Earlier Solution (ERP)

• Introduced as Integrated suites that automated
  core corporate activities such as finance, human
  resources, manufacturing, supply and
  distribution.
• They were designed to solve the fragmentation of
  information in large business organizations and
  integrate all the information flowing within a
  company.

5
Benefits of ERP

• Solutions to problems of legacy systems
• Reduced development risk
• Increased global competitiveness
• Business efficiency

6
Drawbacks of ERP

• Implementation complexity
• Integration problems
• Conflict with the business strategy
• Rigid solutions which were hard to change
• Led organizations to bankruptcy or failure

7
A Better Solution - EAI

• What is EAI?
• Making separate applications work together to
  produce a unified set of functionality.
• Why EAI is so important?

8
Levels Of Integration

• Data-level EAI
• The process and techniques and technology of
  moving data between data stores.
• Application interface-level EAI
• The leveraging of interfaces exposed by custom to
  access both business processes and simple
  information.
• Method-level EAI
• The sharing of the business logic that may exist
  within the enterprise, eliminating the need to
  rewrite each method within several applications.
• User interface-level EAI
• To bundle applications by using their user
  interfaces as a common point of integration

9
Enterprise Integration Models
10
Workflow for EAI

• Divide a task into a flow (business process) and
  task logic (components) before designing and
  developing the system.
• It defines the business process of the target
  tasks and maps the packages to be executed.
• The existing system and the new systems are also
  mapped to the business process.
• The packages are connected using adaptors and
  wrappers.

11
Workflow for EAI
12
Integration Styles

• As there are different levels of integration,
  similarly there are different styles for
  integration. The various ((approaches are
• File Transfer
• Shared Database
• Remote Procedure Invocation
• Messaging

13
File Transfer
14
Shared Database

• Sharing the database ensures that the data is
  always consistent.
• Simultaneous updates can be handled by the
  transaction management system very gracefully.

15
Data Synchronization
16
Data Federation
17
Remote Procedure Invocation

• If an application needs information which is
  owned by another application, it asks that
  application directly.
• Each application can maintain the integrity of
  the data it owns.

18
Brokers
19
Messaging

• Each application connect to a common messaging
  system and exchange data and invoke behavior
  using messages.
• Sending a message does not require both systems
  to be up and running

20
Message Brokers
21
Application Servers
22
Process Orchestration
23
Technology Evolution
24
Architectural Styles for EAI

• Foster loosely couple among components and
  connectors
• Layers
• Model-View-Controller
• Brokers
• Event
• Micro-kernel

25
Technology Evolution

• Proprietary
• Binary data format
• SPX, NetBIOS
• RPC, IIOP, RMI, COM/DCOM
• Closed source

• Open standards
• Text format EDI, XML
• TCP
• SOAP, WSDL
• Open source

26
SOA and EAI
27
SOA and EAI (2)
28
References

• D. S. Linthicum, ed., Enterprise Application
  Integration. Addison Wesley, 1999.
• G. Hohpe and B. Woolf, Enterprise Integration
  Patterns. Addison-Wesley, 2003.
• United Nations Centre for Trade Facilitation and
  Electronic Business, United Nations Standard
  Messages Directory for Electronic Data
  Interchange for Administration, Commerce and
  Transport (EDIFACT)., http//www.unece.org/cefact
  /
• R. Zahavi, Enterprise Application Integration
  with CORBA. John Wiley Sons, Inc., 1999.
• G. Hohpe, Web services Pathway to a
  service-oriented architecture?.,
  http//www.thoughtworks.com, 2002.
• Object Management Group, The Common Object
  Request Broker Architecture and Specification.
  Object Management Group, 2.5 ed., September 2001.
• F. Buschmann, R. Meunier, H. Rohnert, P.
  Sommerlad, and M. Stal, Pattern-Oriented
  Software Architecture. Willey, 1996.

29
Thank you!
30
Electronic Data Interchange(EDI)

• ASC X12 UN/EDIFACT standard
• compressed form
• predefined field identifiers in a predefined
  sequence
• retail, health-care, financial and automotive
• inflexible, expensive
• EDI vs. XML