0% found this document useful (0 votes)
348 views

Enterprise Application Architecture (EAI)

This document discusses enterprise application integration (EAI). EAI allows data to be shared between different applications without custom interfaces. A typical EAI system uses middleware like a message broker to route messages between applications like inventory management, payment processing, and shipping systems. The benefits of EAI include cost effectiveness, faster time to market, scalability, and ability to integrate complex environments. Key components of an EAI system include business rules, data acquisition interfaces, transformation tools, and a system control component to manage the system.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
348 views

Enterprise Application Architecture (EAI)

This document discusses enterprise application integration (EAI). EAI allows data to be shared between different applications without custom interfaces. A typical EAI system uses middleware like a message broker to route messages between applications like inventory management, payment processing, and shipping systems. The benefits of EAI include cost effectiveness, faster time to market, scalability, and ability to integrate complex environments. Key components of an EAI system include business rules, data acquisition interfaces, transformation tools, and a system control component to manage the system.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 18

Enterprise Application Architecture

(EAI)

Lecture 14
Content
•Architectures

•Middleware

•What is EAI

•A Typical EAI System

•EAI Benefits

•Conclusion
Enterprise Application Integration (EAI)
Provides the means to share data between different applications without
writing custom interfaces.
Example:
• Consider a company that wants to do build an eCommerce portal.
• Has a number of legacy applications (or even an ERP solution in place)
• Need build the web-based eCommerce infrastructure and link with systems
that do functions like process orders, manage inventory, ship products
• The company decides to use a major courier service for delivery of products
ordered from the web site.
• The company wants an ODS for analysis of transactions taking place on the site
Example
eCom
Site

Order
System

Inventory ODS

Shipping

Courier

One solution – custom Interfaces Issues?


Example
eCom
Site

Order
System

EAI ODS
Inventory

Shipping

Courier

Alternative – employ EAI solution


Advantages of EAI

•Cost effectiveness

•Time to market

•Scalability

•Ability to deal with complex environments


EAI Components

•Business Rule Component: to allow the applications to understand your


business processes.

•Business Logic Modules (i.e. supply planning, sales order processing. Methods
for business process management.)

•Transformation tools (to define how to map data from one system to another)
EAI Components …. Cont…
Data Acquisition Component: to allow access to the Data Source and Target
Interfaces (i.e. Siebel, SAP, PeopleSoft, ODBC, Oracle, CICS, IMS) - note that the
data acquisition component is crucial to EAI success. Most vendors refer to these
interfaces as "adapters“

Adapters understand the data structures associated with applications and the
means by which to access the data. (SAP/ABAP). map heterogenous data formats,
interfaces and protocols into a common model and format. Hide heterogeneity
and present uniform view of layers below.
EAI Components …… Cont….

System Development Component: to allow programmers


to design and test custom requirements - Design tools (for
business process design, debugging, and testing)
EAI - Components
•System Control Component: Should have the following features:
– Management tools (for application-specific monitoring)

– Directory tools (for locating other applications on different platforms),


particularly support for the Lightweight Directory Access Protocol (LDAP)

– Commitment control management mechanisms (for control of business-


level logical units of work)

– Strong support for metadata management


EAI - Components
– Message Brokers (to control transactions, control security, and perform event notification. The
product should also include the capability to "bridge" messages between different messaging
systems (facilitates the interaction among adapters)

– Scalability for high-volume transaction throughput. It is almost impossible to know at


implementation time what the data volumes will be in the future – therefore, EAI must be
scalable.

– Support for varying levels of fault tolerance, load balancing, and failover for mission-critical
systems. Workflow enablement is a key requirement to reduce latency between distributed
processes.
Typical EAI system
integrating application
(contains the composition logic)

message broker

SmartQuotation database SmartForecasting e-mail XYZ


adapter adapter adapter adapter adapter

SmartQuotation DBMS SmartForecasting XYZ


applications
Message Brokers

•Message oriented middleware

•Supporting integration of heterogenous systems

•Logic for routing messages

•Filtering and processing messages


Old message-based
interoperability

inventory payment- month-end


dispacher shipping
management system closing

new PO

message-oriented middleware
Message Brokers

inventory payment- month-end


dispacher shipping
management system closing

new PO

message broker
Difference
In basic MOM it is the sender who With message brokers, custom
specifies the identity of the receivers. message routing logic can be defined at
the messae broker level or at the
queue level.

sender receiver

message broker core


Routing logic
•sender‘s identity

•message type

•message content

Definition

• message broker level

• queue level
What is EA?
•Its not technical!

•Aligning IT to business.

•Answering all of the enterprise needs

•Transverse view.

• knowing and managing the current situation, paving the road for the wanted one.

•Implementation of information management

•Enforce homogeneous solutions and enable “One system” to the users.

You might also like