Chapter 1 - EAI Intoduction
Chapter 1 - EAI Intoduction
Chapter 1 - EAI Intoduction
Integration
Content
Architectures
Middleware
What is EAI
A Typical EAI System
EAI Benefits
Conclusion
2/31
Architectures
1 layer architecture
monolithic Information Systems
presentation, application logic, and resource
management were merged into a single tier
2 layer architecture
separation of presentation layer from other 2 layers
(app + resource)
became popular as 'server/client' systems
3 layer architecture
can be achieved by separating RM (resource
management) from application logic layer
3/31
Multi-tier Architectures
Where to put the business-logic?
Client tier -> NO!
Fat clients
Reimplementing it for each different type of client
Redistributing clients after each software update
Multi-tier Architectures
Where to put the business-logic?
Middle tier -> YES!
Business logic has its own tier
Client tier
user interfaces
Web browsers
HTML, Java
GUI clients
C++, VB, Java
Middle tier
business logic
Web
Server
Data tier
data sources
Databases
Middleware
Server
Legacy Systems
5/31
Middleware I
Allows communication
through a standard language
across different platforms
between legacy and moderm applications
Takes care of
transactions between servers
data conversion
authentication
communications between computers
6/31
Middleware II
Provides runtime environment for
components in the middle-tier
Component lifecyle and management
Transaction, event and security services
Provides connections to databases,
mainframes and legacy systems
Middleware III
Main use today: legacy wrapping for thin
client architectures
User interfaces
Business logic
Data sources
What is EAI
A step forard in the evolution of
middleware
Integrates applications and enterprise data
sources so that they can easily share
business processes and data
Integration is done without significant
changes of applications and data sources
9/31
Middleware
Middleware
EAI
Middleware
Middleware
Middleware
Middleware
10/31
ERP System
Internal Applications
(Java,C,C++)
Enterprise Portal
Application
CRM System
EAI
Financial System
Databases
Legacy System
SCM System
11/31
purchase
order
CRM System
document
customer-contact
Warehouse
Controlsystem
check
availability
Business Process
Management
not
available
available
ERP System
order atricle
Financial System
write invoice
Manufacturing
System
deliver goods
12/31
Components of EAI
Adapters
map heterogenous data formats, interfaces
and protocols into a common model and
format
hide heterogeneity
present uniform view of layers below
Message brokers
facilitates the interaction among adapters
13/31
message broker
SmartQuotation
adapter
database
adapter
SmartForecasting
adapter
SmartQuotation
DBMS
applications
SmartForecasting
e-mail
adapter
XYZ
adapter
XYZ
14/31
Message Brokers
Message oriented middleware
Supporting integration of heterogenous
systems
Logic for routing messages
Filtering and processing messages
15/31
Old message-based
interoperability
inventory
management
paymentsystem
dispacher
shipping
month-end
closing
new PO
message-oriented middleware
16/31
Message Brokers
inventory
management
paymentsystem
dispacher
shipping
month-end
closing
new PO
message broker
17/31
Difference
With message brokers,
custom message routing
logic can be defined at the
messae broker level or at
the queue level.
sender
receiver
Routing logic
senders identity
message type
message content
Definition
message broker level
queue level
19/31
The Publish/Subscribe
Interaction Model
Applications communicate by exchanging
messages
Senders do not specify the the recipients
of the message, they just publish
Receivers have to subscribe with the
middleware
Middleware retrieves the list of subscrivers
of a messagetype and delivers copy
20/31
The Publish/Subscribe
Interaction Model
inventory
management
(subscriber)
paymentsystem
(subscriber)
dispacher
(pulisher)
shipping
(subscriber)
month-end
closing
(subscriber)
new PO
message broker
21/31
Parameter-based
type = new PO AND customer = ACME
Co. AND quantity > 1200
22/31
The Publish/Subscribe
Interaction Model
admin
client
client
admin
client
client
client
client
23/31
Quotation scenario
1. Receiving the quote from the customer
2. Accessing the quotation system to obtain a
quote
3. Inserting quote information into a forecasting
system (i.e., a system that predicts the order
volume)
4. Sending the quote back to the customer
24/31
publication of a quote
message
delivery of message
quoteRequest
RFQ processing
message broker
SmartQuotation
adapter
SmartForecasting
adapter
synchronous invocation
of the getQuote function
delivery of message
quote
publication of a
newQuote message
delivery of message
newQuote
invocation of the
createForecastEntry
procedure
SmartQuotation
SmartForecasting
25/31
EAI benefits:
Lower development costs
Integration is simpler because systems are more
loosely coupled than in object brokers
Conclusion
Enterprises integrate their applications
less expensive than replacement
more efficient than information islands