Encyclopedia of Database Systems

2018 Edition
| Editors: Ling Liu, M. Tamer Özsu

Enterprise Application Integration

  • Janette Wong
Reference work entry
DOI: https://doi.org/10.1007/978-1-4614-8265-9_1183

Synonyms

Application-centric interfacing; Application-to-application integration; EAI

Definition

Enterprise Application Integration (EAI) is concerned with making applications work together seamlessly, by sharing data and functions among data sources and applications across heterogeneous platforms, facilitated by the use of common middleware. The applications can be a mixture of in-house developed, commercially packaged, and open-source applications; some are contemporary applications, some are legacy systems. Some of the applications were not designed to work together originally. The majority of the definitions set the boundary of EAI for integration within an enterprise. Integration across enterprises involves additional and sometimes different considerations that are covered by solutions that fall under the category of business-to-business (B2B) integration [1]. Variations of the definition of EAI can be found in existing literature. Some of the definitions include the idea that...

This is a preview of subscription content, log in to check access.

Recommended Reading

  1. 1.
    Gullege T. What is integration? Ind Manag Data Syst. 2006;106(1):5–20.CrossRefGoogle Scholar
  2. 2.
    Hohpe G, Woolf B. Enterprise integration patterns – designing, building, and deploying messaging solutions. Reading: Addison Wesley; 2004.Google Scholar
  3. 3.
    Adams J. IBM Patterns for e-business: application Integration pattern. IBM developerWorks. http://www-128.ibm.com/developerworks/patterns/application/index.html
  4. 4.
    Trowbridge D, Roxburgh U, Hohpe G, Manolescu D, Nadhan EG. Integration patterns. Redmond: Microsoft Corporation; 2004.Google Scholar
  5. 5.
    Ruh W, Maginnis F, Brown W. Enterprise application integration – a Wiley tech brief. New York: Wiley; 2001.Google Scholar
  6. 6.
    Sauter G, Mathews B, Selvage M, Lane E. Information service patterns, part 1: data federation pattern. IBM developerWorks, 28 July 2006. http://www.ibm.com/developerworks/webservices/library/ws-soa-infoserv1/
  7. 7.
    Sauter G, Mathews B, Selvage M, Ostic E. Information service patterns, part 2: data consolidation pattern. IBM developerWorks, 5 Dec 2006. http://www.ibm.com/developerworks/webservices/library/ws-soa-infoserv2/
  8. 8.
    Sauter G, Mathews B, Ostic E Information service patterns part 3: data cleansing pattern. IBM developerWorks, 6 Apr 2007. http://www.ibm.com/developerworks/webservices/library/ws-soa-infoserv3/
  9. 9.
    Dreibelbis A, Hechler E, Mathews B, Oberhofer M, Sauter G Information service patterns, Part 4: master data management architecture patterns. IBM developerWorks, 29 Mar 2007. http://www.ibm.com/developerworks/db2/library/techarticle/dm-0703sauter/
  10. 10.
    Chari K, Seshadri S. Demystifying integration. Commun ACM. 2004;47(7):59–63.CrossRefGoogle Scholar

Copyright information

© Springer Science+Business Media, LLC, part of Springer Nature 2018

Authors and Affiliations

  1. 1.IBM Canada LtdMarkhamCanada

Section editors and affiliations

  • H.-Arno Jacobsen
    • 1
  1. 1.Dept. of Elec. and Comp.Eng.Univ. of TorontoTorontoCanada