Employing Enterprise Application Integration (EAI)


Published on

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Employing Enterprise Application Integration (EAI)

  1. 1. Employing Enterprise Application Integration (EAI) to Achieve a Zero-Latency- Enterprise (ZLE) E I A ZLE The MITRE Corporation, Scott Hume eBusiness Lead
  2. 2. What is EAI? The MITRE Corporation, Scott Hume eBusiness Lead
  3. 3. What’s driving this momentum? • The explosion of the Internet • The demand for a COTS best-of-breed solution • Mergers & Acquisition consolidation • Supply and Demand Chain integration • Front and Back office integration,legacy systems can not be thrown away • Customer profitability, business agility The MITRE Corporation, Scott Hume eBusiness Lead
  4. 4. Current Problem(s) • Ad-Hoc Integration leads to an unmanageable tangle of “one-off” interfaces • Information is redundant, out-of-date, out-of-synch and/or inaccessible • Uneven Information Assurance implementation leaves gaps and holes in security • Redundant development with little re-use The MITRE Corporation, Scott Hume eBusiness Lead
  5. 5. Making the case for EAI • Information islands • Changing technology landscape • Information and process overlap • The ERP Puzzle The MITRE Corporation, Scott Hume eBusiness Lead
  6. 6. Types of Integration • Data Level • Message Level • Process Level The MITRE Corporation, Scott Hume eBusiness Lead
  7. 7. Legacy System Types of EAI Legacy System User Interface Level Business Processes Business Processes Method Level Package Application Package Application Application Interface Level Data Store Data Store Data Level The MITRE Corporation, Scott Hume eBusiness Lead
  8. 8. Implementation Architecture 1. Hub and Spoke 2. Bus A B Wrapper Broker C A B C D D 3. Multihub Integration Platform Message Bus B A A B Broker Broker C Integration Manager C D D B Broker C A D The MITRE Corporation, Scott Hume eBusiness Lead
  9. 9. EAI vs. Traditional Middleware • Traditional Middleware • EAI – Provides the “plumbing” – Integrating end-to-end for exchanging business processes in a information in a global, distributed, and distributed computing diverse computing environment environment The MITRE Corporation, Scott Hume eBusiness Lead
  10. 10. So, what is middleware today? • Specialized networked services that are shared by applications and users • A set of core software components that permit scaling of applications and networks • Tools that take the complexity out of application integration • A second layer of the IT infrastructure, sitting above the network • A land where technology meets policy The MITRE Corporation, Scott Hume eBusiness Lead
  11. 11. The New Direction: Integration Brokers ERP System Portal COTS CRM COTS Adaptors Application Integration Broker Servers Portal WorkFlow COTS Adapters Integration Broker Manager Adapters (ODBC, JDBC, LDAP) Custom Adapter Directory & Storage Area DB Servers Security (publishing) Legacy Servers Systems The MITRE Corporation, Scott Hume eBusiness Lead
  12. 12. EAI Model* *Source: Tibco © The MITRE Corporation, Scott Hume eBusiness Lead
  13. 13. The quest for standards The MITRE Corporation, Scott Hume eBusiness Lead
  14. 14. XML and EAI Foundation for A2A, B2B, or both? The MITRE Corporation, Scott Hume eBusiness Lead
  15. 15. SOAP • A protocol designed to be simple and to use internet standards such as HTTP and XML • Essentially the start of replacement for IIOP and DCOM when these are used over the Internet • A way to enable messages through firewalls • Basic low level, loosely coupled infrastructure “By 2003, the invocation methods of more than 70 percent 2000 2003 of Web Services will be: a loosely coupled SOAP Structure (0.7 probability); existing RPC/ORB structures (0.1 probability); or another XML/HTTP variant (0.2 probability).” Source: Gartner © The MITRE Corporation, Scott Hume eBusiness Lead
  16. 16. UDDI Organizations register information about their businesses and Web-based services in UDDI’s directory White Pages Yellow Pages Green Pages •Organization’s name •Services and •E-business rules •Contact Information •product index •Service descriptions •Identifiers •Industry Codes •Application invocation (e.g.. Tax Id) •Geographical index •Data binding The MITRE Corporation, Scott Hume eBusiness Lead
  17. 17. EAI Building Blocks Systems monitoring & management E-Business Services B2B Integration Business Process Management Enterprise Application Integration Application Servers & Web Servers Application Messaging The MITRE Corporation, Scott Hume eBusiness Lead
  18. 18. In the search for a Holy Grail solution, what are some key ingredients? Things to consider before purchasing: • Scalability and redundancy- the infrastructure has to be designed to support the current message volume and future growth • Application integration tools- select an EAI solution that supplies an adapter to t he packaged applications you intend to integrate and allows your developers to easily build your own adapters for custom- built application • Extensibility- you should be able to add to and change business processes without affecting the underlying application, and IT department should be able to change applications without affecting business processes The MITRE Corporation, Scott Hume eBusiness Lead
  19. 19. The Current EAI Marketplace The MITRE Corporation, Scott Hume eBusiness Lead
  20. 20. Benefits of Integration • Open new revenue generating distributions channels • Rapid Organizational response • Streamlining supply chain business processes • Leverage IT investment • Reduce cost of doing business The MITRE Corporation, Scott Hume eBusiness Lead
  21. 21. The e-Business Architecture Customers Customers Human Financial CRM Enterprise Resources Resource Enterprise Planning Portals Application B2B Vendors & Partners Integration Vendors & Partners Employees Databases Mainframe Legacy Applications Marketplaces & The MITRE Corporation, Scott Hume eBusiness Lead Exchanges
  22. 22. ‘Zero Latency Enterprise’ Virtual Enterprise Enterprise Business Customers Data Center, & ASPs Subsidiary Dealers ERP, HR, Billing Sales Enterprise Nervous System Suppliers Purchasing Distribution Service Marketing Web-based Web-based Intermediaries Intermediaries Business Customers Suppliers The MITRE Corporation, Scott Hume eBusiness Lead Source: Gartner ©
  23. 23. The MITRE Corporation, Scott Hume eBusiness Lead
  24. 24. EAI Conclusions • EAI is a business issue and should add value to the bottom line • EAI infrastructure is a hard sell without a business imperative • EAI is critical to large corporate e-business strategies – .”Com” and “Bricks & Mortar” challenges • EAI is a distinct market identified by users as strategic • EAI enables Workflow/Process Management and facilitates BPR • Successful EAI requires business process, technical and product understanding The MITRE Corporation, Scott Hume eBusiness Lead
  25. 25. Backup slides The MITRE Corporation, Scott Hume eBusiness Lead
  26. 26. Web Service Standards STANDARD ORIGIN PURPOSE RECENT EXPECTED STATUS FUTURE SOAP- Created by An XML-based SOAP 1.1 The W3C XML (Simple Object Develop Mentor, protocol for specification Protocol (XP) Access Protocol) Microsoft, and messaging and simultaneously Working Group is Userland Software; RPC-style released and working on a Microsoft communication submitted to SOAP standard, solicited industry between two the W3C in May which will be feedback on the processes 2000; SOAP 1.1 called XP SOAP 0.9 specification in specification in use by developers September 1999 UDDI- Created by Ariba, A set of XML The UDDI Two more draft (Universal IBM, and protocols and specification specifications are Description, Microsoft; an hasn't yet been planned before Discovery, and Version 1.0 draft infrastructure submitted to UDDI is turned Integration) specification for the any standards over to a standards released in description and organizations; organization some September 2000 discovery of Draft version time during the business 1.0 in use by next 12 months. processes developers WSDL Created by IBM An XML language WSDL 1.0 The W3C has not (Web Services and Microsoft used to describe specification yet announced Description by merging how to connect to submitted to what action language) previous a Web Service. the W3C in they will take proposals: SCL, March, 2001; on the WSDL SDL, and WSDL 1.0 submission NASSL; Version specification in 1.0 specification use by released in developers September 2000 The MITRE Corporation, Scott Hume eBusiness Lead Source: Information Week 04/2001 ©
  27. 27. EAI The MITRE Corporation, Scott Hume eBusiness Lead
  28. 28. Appendices The MITRE Corporation, Scott Hume eBusiness Lead
  29. 29. Acronyms API (application program interface) is the specific method prescribed by a computer operating system or by an application program by which a programmer writing an application program can make requests of the operating system or another application. COM (Component Object Model) is Microsoft's framework for developing and supporting program component objects, an object encapsulation technology specifies interfaces between component objects within a single application or between applications CORBA (Common Object Request Broker Architecture) is an architecture and specification for creating, distributing, and managing distributed program objects in a network. DCOM (Distributed Component Object Model) is a set of Microsoft concepts and program interfaces in which client program objects can request services from server program objects on other computers in a network. IIOP (Internet Inter-ORB Protocol) is a protocol that makes it possible for distributed programs written in different programming languages to communicate over the Internet. JDBC (Java Database Connectivity) is an application program interface (API) specification for connecting programs written in Java to the data in popular database. LDAP (Lightweight Directory Access Protocol) is a software protocol for enabling anyone to locate organizations, individuals, and other resources such as files and devices in a network, whether on the public Internet or on a corporate Intranet. MOM (Message-oriented middleware) is used for connecting applications on different operating systems, most commonly through the use of message queuing The MITRE Corporation, Scott Hume eBusiness Lead
  30. 30. Acronyms ODBC (Open Database Connectivity) is an open standard application-programming interface (API) for accessing a database. ORB (Object Request Broker) is the programming that acts as a quot;brokerquot; between a client request for a service from a distributed object or component and the completion of that request. RPC (Remote Procedure Call) is a protocol that one program can use to request a service from a program located in another computer in a network without having to understand network details SOAP (Simple Object Access Protocol) is a way for a program running in one kind of operating system to communicate with a program in the same or another kind of an operating system by using the World Wide Web's Hypertext Transfer Protocol (HTTP) and its Extensible Markup Language (XML) as the mechanisms for information exchange. UDDI (Universal Description, Discovery, and Integration) is an XML-based registry for businesses worldwide to list themselves on the Internet WSDL (Web Services Description Language) is an XML-based language used to describe the services a business offers and to provide a way for individuals and other businesses to access those services electronically XML (Extensible Markup Language) is a flexible way to create common information formats and share both the format and the data on the World Wide Web, Intranets, and elsewhere. ZLE (Zero Latency Enterprise) is an enterprise in which all parts of the organization can respond to events as they occur elsewhere in the organization, using an integrated IT infrastructure that can immediately exchange information across technical and organization boundaries The MITRE Corporation, Scott Hume eBusiness Lead