1 / 37

Section 10 Enterprise Application Integration

Section 10 Enterprise Application Integration. LEARNING OUTCOMES. Describe necessity and characteristics of Enterprise Application Integration(EAI) Define EAI and its aim, benefit and challenges List principles for Enterprise Integration

camilla-doyle
Download Presentation

Section 10 Enterprise 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. Section 10 Enterprise Application Integration

  2. LEARNING OUTCOMES • Describe necessity and characteristics of Enterprise Application Integration(EAI) • Define EAI and its aim, benefit and challenges • List principles for Enterprise Integration • Describe the advantages of E-Collaboration scenarios,IS Integration and E-Collaboration platforms

  3. Agenda A. Introduction B. E-Collaboration scenarios C. IS Integration D. E-Collaboration platforms

  4. Web-based services for business customers Motives • Cost strategy: equal/increased service level for business customers at lower cost • Transferring administrative/functional services on a medium/channel with a lower cost level • Improving customer relations by providing web services

  5. Clients Suppliers Partners Partners CORBA Clients MOM COM FTP RPC Solaris HTTP …... SAP C++ EDI HL7 Oracle XML SOAP ….. A Sample of Complicated Application View The Enterprise OS 390 EDI Trns Windows NT Cobol Apps Natural Apps SQL Server HTML MQ Series Java Apps IIS DB2 Adabas CICS VSAM Windows 2000 VB Apps Pivotal SQL Server Is web the only way to integrated?

  6. Web-based services for business customers But • Impact of e-business solutions on customer satisfaction? • Costs of implementing and maintaining an e-business solution? • Customer needs, demands and requirements?

  7. Agenda A. Introduction B. E-Collaboration scenarios C. IS Integration D. E-Collaboration Platforms

  8. FAQ (Asus)

  9. Manual Download (Asus)

  10. Agenda A. Introduction B. E-Collaboration scenarios C. IS Integration D. E-Collaboration Platforms

  11. Enterprise Application Integration • Enterprise Application Integration • Definition: The process of integrating multiple applications that were independently developed, may use incompatible technology, and remain independently managed. • By this definition, EAI would include: • Business Process Integration • Enterprise Information Integration

  12. Guiding Principles for Enterprise Integration • Clear IT Strategy mapped to Business Strategy • Mapping of corporate process and data models • Plan ahead for EI - investment vs. cost justification • Formulate an EI architecture based on integration characteristics • Establish clear lines of ownership and accountability • Evaluate vendors on commercials, stability, references, strategy • Evaluate technologies - scalability, flexibility, customization, standards • Invest in the right skills - Solution & Integration Architects • Pilot the desired solution, but in a real environment • Ensure tools and processes in place for end-to-end service mgmt.

  13. Enterprise Integration Taxonomy

  14. Common Layers of EAI Solutions Business Intelligence Provides real-time and historical data on performance of processes and assists in making decisions. Business Process Management Manages and tracks business transactions that might span multiple systems and last minutes to days. Messaging Ensures the reliability of data delivery across the Enterprise or between systems. Adapters Provides “open” connectivity into data sources while allowing filtering and transformations of data.

  15. A sample of Integration Methodology

  16. Difficulty of EAI In 2003, 70% of EAI projects turned out to fail Trotta, Gian(2003) -Failure reason 1.Constant change 2.Shortage of EAI experts 3.Competing standards 4.EAI is a tool paradigm 5.Building interfaces is an art 6.Loss of detail 7.Accountability 8.Lack of centralized co-ordination of EAI work. Toivanen, Antti (2013)

  17. IS Integration Approaches Motivation • Technical considerations for web services • Service scenarios (services, business processes) • Process model (heuristic) • Extending EAI concept into an inter-organizational direction • EAI provides different levels of integration (from loose coupling to very tight integration) • EAI is a concept, I.e. independent of programming languages, technical infrastructures etc.

  18. Enterprise Application Integration Aim Integrate existing - both intra- and inter-organizational - applicationsusing a common middleware rather than recreate the same business processes and data repositories over and over again. (Averagely, The Fortune 1000 firms are managing around 15-100 major software applications.)

  19. Enterprise Application Integration Reasons • Saving development costs • Retaining existing value of legacy applications (but “ancient” technology) • Increasing need for integration by popularity of packaged applications such as SAP R/3 • Need for a comprehensive integration system rather than creating interfaces and integration points between every application and data source

  20. Enterprise Application Integration Benefit • Reuse of integration objects • Modeling business information corresponds directly to business model • End-user / SME driven changes • Multiple presentations for single piece of information • Lower cost of integration • Initial • Maintenance

  21. Spaghetti integration Source: [Linthicum 1999, 9]

  22. The way to EAI Source: [Pinkston 2001, 49]

  23. Levels of EAI Source: [Linthicum 1999, 19]

  24. EAI vision Source: [Linthicum 1999, 10]

  25. Typical Architecture of EAI Business Application Transformer Business Application Function Database Database Function Data Integration Broker Adapter Adapter Adapter Adapter XML SOAP Web Services Broker UDDI

  26. Implementation of Inter-EAI • User Interface Level • HTML Frames • Content syndication • Method Level • Web Services • Application Interface Level • Middleware (e.g. CORBA) • Jave RMI • SAP R/3 business objects • Data Level • EDI standards (e.g. EDIFACT) • XML standards (e.g. BMEcat, openTrans)

  27. Web Services Source: [Linthicum 1999, 19]

  28. XML Web Services Source: www.microsoft.com

  29. Web Services Benefits • Loose application coupling • Independent application evolution • All vendors are pushing for web services • (Some) interoperability • Standardization of integration technologies • Convenience APIs and tools • Enable ASP (Application Service Providing)

  30. The Web Service Architecture Web services Application services Application service Application service Application service Application service Service grid Shared utilities Security, auditing and assessment of third-party performance, billing and payment Service management utilities Provisioning, monitoring, ensuring quality ofservice, synchronization, conflict resolution Resource knowledge management utilities Directories, brokers, registries, repositories,data transformation Transport management utilities Message, queuing, filtering, metering, monitoring, routing, resource orchestration Standards and protocols Software standards • WSDL • UDDI • XML Communication protocols • SOAP • HTTP • TCP/IP Source: [Hagel/Brown 2001]

  31. Agenda A. Introduction B. E-Collaboration scenarios C. IS Integration D. E-Collaboration Platforms

  32. E-Collaboration Platforms • Platform (technical infrastructure) for offering web services • Possible platform concepts • Corporate portal • Co-operation platform • Electronic marketplace • Application Service Providing • Selection decision is affected by • Standardization issues • “Richness” of service portfolio • Customer acceptance

  33. Corporate portal • Internet portal • Relationship: One-to-some/one-to-many • Low/moderate investments on customer side (Web browser) • Offering tailored (proprietary) services • Low standardization demands • One front-end for whole service portfolio • Requirements analysis/implementation according to Process Portal Methodology • Most firms (Dell, Cisco, etc.) providing their web services on a corporate portal

  34. Co-operation platform • Co-operation platform • (Open) platform hosted by Siemens ICN, a third-party or a consortium • Relationship: Some-to-some/some-to-many • Low/moderate investments on customer side (Web browser) • Offering (more) generic web services • Standardization is more important • Various business models possible • Negotiations between platform providers neccessary • Examples: Covisint, … • Conflict resolution (e.g. negotiation of standards)? • Reduced service portfolio • Customer acceptance should be higher

  35. Future and Trend of EAI • Evolving from data-level integration into business process automation. • Changing from focusing on integrating enterprise applications to integration of heterogeneous platforms. • Providing Infrastructure, allows for futuristic conversion for total integration. • Shorten the time lag between the introduction of new products and services through integration of various platforms with business applications. • Going to cloud

  36. References • Special thanks to 1)Lehrstuhl für Wirtschaftinformatik und Interorganisationssysteme (IOS) Prof. Dr. Stefan Klein Universität Münster Institut für Wirtschaftsinformatik 2) http://www.integrationconsortium.org

More Related