Enterprise Application Integration - PowerPoint PPT Presentation

About This Presentation
Title:

Enterprise Application Integration

Description:

Lecture-03 Subject: System Integration & Architecture – PowerPoint PPT presentation

Number of Views:127
Updated: 20 March 2018
Slides: 17
Provided by: inam12
Tags:

less

Transcript and Presenter's Notes

Title: Enterprise Application Integration


1
Enterprise Application Integration
(EAI)
Lecture 3
  • System Integration Architecture
  • Inam Ul Haq
  • BSIT-6th
  • University of Education Okara

2
Contents
  • EAI?
  • Architectures
  • Middleware
  • What is EAI
  • A Typical EAI System
  • EAI Benefits
  • Conclusion

3
Defining EAI
  • Why EAI?
  • Wouldnt it be great if everyone used the same
    servers with the same operating system with the
    same clients.
  • Reality is very diverse. We can expect a mix of
    mainframes, Windows, UNIX, Linux, VMs, as well as
    many other systems
  • Getting them to work/share data together is the
    issue!
  • EAI is defined as the unrestricted sharing of
    data and business processes among any connected
    applications and data sources in the enterprise.
  • Using EAI effectively will allow us to integrate
    without making major changes to our current
    infrastructure.
  • EAI How we bridge gap between different
    software programs

4
Architectures
  • 1 layer architecture (1 tier)
  • 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

5
(No Transcript)
6
Multi-tier Architectures
  • In software engineering, multitier
    architecture (often referred to as n-tier
    architecture) is a clientserver architecture in
    which presentation, application processing, and
    data management functions are physically
    separated. 
  • The most widespread use of multitier architecture
    is the three-tier architecture. (Wikipedia)

7
Multi-tier Architectures
  • Where to put the business-logic?
  • Middle tier -gt YES!
  • Business logic has its own tier
  • A data-tier application (DAC) is a logical
    database management entity that defines all of
    the SQL Server objects - like tables, views, and
    instance objects

Client tier user interfaces
Middle tier business logic
Data tier data sources
Web browsers HTML, Java
Middleware Server e.g. Web server
Databases
GUI clients C, VB, Java
Legacy Systems
8
Middleware
  • Allows communication
  • through a standard language e.g. JSP
  • across different platforms
  • between legacy and moderm applications
  • Takes care of
  • transactions between servers
  • authentication
  • communications between computers
  • E.g. Web servers, application servers, CMS, and
    releted tools
  • Note search ERP Systems below for broader idea
  • https//en.wikipedia.org/wiki/List_of_ERP_software
    _packages

9
Middleware (Contt.)
  • Main use today covering thin client
    architectures (heavily server dependent)
  • CORBA enables communication between different
    platforms.
  • EJB (Enterprise JavaBeans) is a subset of the
    Java EE specification.

User interfaces
Client-tier (GUI applications, browsers)
Business logic
Middle-tier (CORBA/EJB)
Data sources
Data-tier (databases, mainframes)
10
Middleware
Middleware
EAI
Middleware
Middleware
Middleware
Middleware
11
ERP System
CRM System
Internal Applications (Java,C,C)
EAI
Databases
Enterprise Portal Application
Legacy System
Financial System
Suppy Chain Mgt System
12
EAI benefits
  • Lower development costs
  • Integration is simpler because systems are more
    loosely coupled
  • Lower opportunity costs
  • Integration is done more quickly
  • Corresponding cost savings reachieved sooner
  • Lower maintenance effort
  • Adapters extract the interaction with external
    systems
  • Significant advantage from the software
    engineering point of view

13
Real World Example
  • 1875 Alexander Graham Bell invented the telephone
    in the 19th century and ATT became parent
    company of the Bell System,
  • The system broke up into eight companies in 1984.

14
Conclusion
  • Enterprises integrate their applications
  • less expensive than replacement
  • more efficient than information islands
  • Enterprises must establish web-presence and make
    business services available to web-clients

15
Exercise
  • Explore CORBA, EJB

16
References
  • http//www.ibm.com
  • http//www.att.com
  • http//www.eaipatterns.com/
  • http//www.iwaysoftware.com/
  • http//www.capterra.com/enterprise-application-int
    egration-software
  • http//www.infoworld.com/techindex/enterprise_appl
    ication_integration_-_eai.html
Write a Comment
User Comments (0)
About PowerShow.com