More

    OVERVIEW OF ENTERPRISE APPLICATION INTEGRATION (EAI)

    Enterprise application integration (EAI) is the use of software and computer systems’ architectural principles to integrate a set of enterprise computer applications like ERP systems, CRM systems, Databases and even legacy software systems.

    Enterprise application integration can be considered as an integration framework composed of a collection of technologies and services which form a middleware to enable integration of systems and applications across an enterprise.

    Why EAI?

    Many types of business software such as supply chain management applications, ERP systems, CRM applications for managing customers, business intelligence applications, payroll and human resources systems typically cannot communicate with one another in order to share data or business rules. For this reason, such applications are sometimes referred to as islands of automation or information silos. This lack of communication leads to inefficiencies, wherein identical data are stored in multiple locations, or straightforward processes are unable to be automated.

    Enterprise application integration is the process of linking such applications within a single organization together in order to simplify and automate business processes to the greatest extent possible, while at the same time avoiding having to make sweeping changes to the existing applications or data structures.

    The various systems that need to be linked together may reside on different operating systems, use different database solutions or computer languages, or different date and time formats, or may be legacy systems that are no longer supported by the vendor who originally created them. 

    Use cases for EAI

    EAI can be used for different purposes:

    • Data integration: Ensures that information in multiple systems is kept consistent. This is also known as enterprise information integration (EII).
    • Vendor independence: Extracts business policies or rules from applications and implements them in the EAI system, so that even if one of the business applications is replaced with a different vendor’s application, the business rules do not have to be re-implemented.
    • Common facade: An EAI system can front-end a cluster of applications, providing a single consistent access interface to these applications and shielding users from having to learn to use different software packages.

    Examples of EAI solutions

    Commercial products include:

    • IBM WebSphere Message Broker
    • Informatica Cloud Data Integration
    • Information Builders iWay ISM
    • Intersystems Ensemble
    • Jitterbit Integration Server
    • Magic Software xpi Integration Platform
    • Microsoft BizTalk Server
    • Mule Enterprise
    • Oracle SOA Suite
    • SAP NetWeaver Process Integration (PI)
    • SnapLogic
    • Software AG Suite
    • Tibco ActiveMatrix/Business Works
    • WebMethods

    Open-source projects include:

    • UltraESB
    • Apache ActiveMQ
    • Mule ESB
    • Apache Camel
    • GuaranĂ¡ DSL
    • Fuse ESB (based on Apache ServiceMix)
    • Fuse Mediation Router (based on Apache Camel)
    • Fuse Message Broker (based on Apache ActiveMQ)
    • MuleSoft
    • Niklas Integration Platform
    • Openadaptor
    • OpenESB
    • Petals ESB
    • Talend
    • Virtuoso Universal Server
    • RabbitMQ (based on AMQP protocol)

    References

    http://en.wikipedia.org/wiki/Enterprise_application_integration

    Recent Articles

    OAUTH – FREQUENTLY ASKED QUESTIONS FOR INTERVIEWS AND SELF EVALUATION

    Why is refresh token needed when you have access token? Access tokens are usually short-lived and refresh tokens are...

    SUMO LOGIC VIDEOS AND TUTORIALS

    Sumo Logic Basics - Part 1 of 2 (link is external) (Sep 29, 2016)Sumo Logic Basics - Part 2 of 2...

    GIT – USEFUL COMMANDS

    Discard all local changes, but save them for possible re-use later:  git stash Discarding local changes...

    DISTRIBUTED COMPUTING – RECORDED LECTURES (BITS)

    Module 1 - INTRODUCTION Recorded Lecture - 1.1 Introduction Part I – Definition

    BOOK REVIEW GUIDELINES FOR COOKBOOKS

    Whenever you add reviews for the book, please follow below rules. Write issues in an excel.Create an excel...

    Related Stories

    Leave A Reply

    Please enter your comment!
    Please enter your name here

    Stay on op - Ge the daily news in your inbox