Transcript Document 7198858

Enterprise Application
Integration Styles
Phong Nguyen Thanh
Muhammad Usman Khokhar
Agenda



Introduction
Overview of current EAI technologies
Evolutions in EAI Styles
20 May 2016
2
Background



Large amount of software resources and there
integration is a fundamental part in today’s 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 company’s IT budget (over $100
billion) is being spent linking the systems together.
20 May 2016
3
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.
20 May 2016
4
Benefits of ERP




Solutions to problems of legacy systems
Reduced development risk
Increased global competitiveness
Business efficiency
20 May 2016
5
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
20 May 2016
6
A Better Solution - EAI

What is EAI?


Making separate
applications work
together to produce a
unified set of
functionality.
Why EAI is so
important?
20 May 2016
7
Levels Of Integration

Data-level EAI


Application interface-level EAI


The leveraging of interfaces exposed by custom to access
both business processes and simple information.
Method-level EAI


The process and techniques and technology of moving data
between data stores.
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
20 May 2016
8
Enterprise Integration Models
20 May 2016
9
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.
20 May 2016
10
Workflow for EAI
20 May 2016
11
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
20 May 2016
12
File Transfer
20 May 2016
13
Shared Database


Sharing the database ensures that the data is
always consistent.
Simultaneous updates can be handled by the
transaction management system very
gracefully.
20 May 2016
14
Data Synchronization
20 May 2016
15
Data Federation
20 May 2016
16
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.
20 May 2016
17
Brokers
20 May 2016
18
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 May 2016
19
Message Brokers
20 May 2016
20
Application Servers
20 May 2016
21
Process Orchestration
20 May 2016
22
Technology Evolution
20 May 2016
23
Architectural Styles for EAI

Foster loosely couple among
components and connectors





Layers
Model-View-Controller
Brokers
Event
Micro-kernel
20 May 2016
24
Technology Evolution

Proprietary




Binary data format
SPX, NetBIOS
RPC, IIOP, RMI,
COM/DCOM
Closed source
20 May 2016

Open standards

Text format: EDI,
XML
TCP
SOAP, WSDL

Open source


25
SOA and EAI
20 May 2016
26
SOA and EAI (2)
20 May 2016
27
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, “PatternOriented Software Architecture”. Willey, 1996.
20 May 2016
28
Thank you!
20 May 2016
29