1 / 23

Types of Application Integration

Types of Application Integration. IST 421 Fall 2006. Enterprise integration should enable organizations to become more agile and flexible. This means: Continuously monitor market demand Quickly respond by providing new products, services & information Quickly introduce new technologies

lkaren
Download Presentation

Types of Application Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Types of Application Integration IST 421 Fall 2006

  2. Enterprise integration should enable organizations to become more agile and flexible. This means: Continuously monitor market demand Quickly respond by providing new products, services & information Quickly introduce new technologies Quickly modify business methods Lee, Siau, & Hong, Enterprise Integration with ERP and EAI, Communications Of the ACM, Vol. 46, Number 2, February 2003, 54-60.

  3. Coupling • The act of bringing together • Binding logic with data; level of interdependency between the two components • Problems: • Creates one application and database out of many, each dependent on the other • Over time, a change to any system means a change to the coupled systems as well

  4. Cohesion • Act of “sticking” together • Applications and databases are independent • Changes to any source system should not affect the others

  5. Coupling vs. Cohesion • The goal is to have loosely coupled components so that there is little or no dependency • Integration solutions should be cohesive rather than coupled

  6. Integration Models • An approach and configuration used to integrate software • It emphasizes one or two of the following attributes: • Simplicity of performing the integration • Reusability of integration for different configurations • Breadth of possible approaches to integration • Expertise required to perform integration

  7. Integration Models • There are four general categories to consider for integration: • Information-oriented • Business process integration-oriented • Service-oriented • Portal-oriented

  8. Information-Oriented • Information-oriented approach suggests that integration should occur between databases • Data replication • Data federation • Interface processing

  9. Information-Oriented • Data Replication • Move data between two or more databases • Provide the infrastructure to exchange data • Advantages to this technique: • Simple • Low cost

  10. Data-Level Integration

  11. Data-Level Integration • A variety of tools and data access middleware have been used to access and integrate at the data level • Batch file transfer • Open Database Connectivity (ODBC) • Database access middleware – provide connectivity to distributed databases • Data transformation – convert data from source database format into target database format; EBCDIC to ASCII

  12. When to Use it • Combine data from multiple sources for analysis and decision making • Provide multiple applications with read access to a common source of information • Allow data to be extracted from one source and reformatted and updated in another

  13. Data-Level Integration • Advantages: • Tools and techniques currently exist • Relatively easy • Requires no changes to the application logic or database structure • Provides access to a wider range of data • Allows data to be reused across other applications

  14. Data-Level Integration • Disadvantages: • Need to rewrite business logic

  15. Data-Level Example • Customer data from Sybase, IBM DB2, and SAP R/3 databases combined into a call center application. • Middleware would be used to access the data and integrate it into the call center application • Call center application would send a request to the middleware

  16. Data-Level Example • Middleware would send the request to each of the databases in the correct format and wait for responses. Responses would be passed back to the call center application.

  17. Other Data Source to Consider • Relational databases • IDMS • IMS • VSAM • ISAM • Flat files

  18. Presentation Integration • One of the simplest models • Integration of multiple software components is accomplished through an application user interface • Application appears to be a single application although it may be accessing several legacy applications

  19. When to Use it • Put a PC-based user interface on an existing terminal-based application • Provide a single application that is in fact a composite of several applications

  20. Presentation Integration • Advantages: • Very easy and quick to do • Developer focuses on new presentation • Disadvantages: • Can have performance bottlenecks • Most limiting model

  21. Information Integration • Integration solution set that works: • Identify the data • Catalog the data into a data dictionary • Reason for the data • Ownership • Format • Security • Role in the data structure • Build the enterprise metadata model • Used as a master guide for integrating

  22. Information Integration • Maintain integrity issues • Data latency • Real time • Near time • One time

  23. Information Integration

More Related