Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Enterprise application integration

Please visit and for more information.

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

Enterprise application integration

  2. 2. OBJECTIVES ODS Overview EAI concepts EAI functional components 2
  3. 3. DEFINITIONS 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
  4. 4. ENTERPRISE APPLICATION INTEGRATION Enterprise Application Integration (EAI) is one of the hot- button issues in Information Technology in 2000. Information Week's research survey of 300 technology managers showed nearly 75% of respondents said EAI is a planned project for their IT departments in the coming year. According to a study by Bank Boston, the market for EAI is expected to be $50 Billion USD in 2001 4
  5. 5. ENTERPRISE APPLICATION INTEGRATION EAI began at Goldman Sachs in New York nearly 10 years ago, where they funded the Teknekron Information Bus (TIB) to pump stock market quotes into different systems. The programmers who wrote Teknekron then left and founded TIBCO. Many of those same developers are now with Vitria.                           5
  6. 6. ENTERPRISE APPLICATION INTEGRATION (EAI) Provides the means to share data between different applications without writing custom interfaces. Example:  Consider a company that wants to do build an eCommerce portal.  Has a number of legacy applications (or even an ERP solution in place)  Need build the web-based eCommerce infrastructure and link with systems that do functions like process orders, manage inventory, ship products  The company decides to use a major courier service for delivery of products ordered from the web site.  The company wants an ODS for analysis of transactions taking place on the site 6
  7. 7. EXAMPLE 7 eCom Site Courier Shipping Inventory Order System ODSEAI Alternative – employ EAI solution
  8. 8. ADVANTAGES OF EAI Cost effectiveness Time to market Scalability Ability to deal with complex environments 8
  9. 9. EAI COMPONENTS Business Rule Component: to allow the applications to understand your business processes Business Logic Modules (i.e. supply planning, sales order processing. Methods for business process management.) Transformation tools (to define how to map data from one system to another)                               9
  10. 10. EAI COMPONENTS Data Acquisition Component: to allow access to the data Data Source and Target Interfaces (i.e. Siebel, SAP, PeopleSoft, ODBC, Oracle, CICS, IMS) - note that the data acquisition component is crucial to EAI success. Most vendors refer to these interfaces as "adapters" Adapters understand the data structures associated with applications and the means by which to access the data. (SAP/ABAP) 10
  11. 11. EAI COMPONENTS System Development Component: to allow programmers to design and test custom requirements - Design tools (for business process design, debugging, and testing) 11
  12. 12. EAI - COMPONENTS System Control Component: Should have the following features:  Management tools (for application-specific monitoring)  Directory tools (for locating other applications on different platforms), particularly support for the Lightweight Directory Access Protocol (LDAP)  Commitment control management mechanisms (for control of business-level logical units of work)  Strong support for metadata management 12
  13. 13. EAI - COMPONENTS  Message Brokers (to control transactions, control security, and perform event notification. The product should also include the capability to "bridge" messages between different messaging systems  Scalability for high-volume transaction throughput. It is almost impossible to know at implementation time what the data volumes will be in the future – therefore, EAI must be scalable.  Support for varying levels of fault tolerance, load balancing, and failover for mission- critical systems  Workflow enablement is a key requirement to reduce latency between distributed processes. 13
  14. 14. EXAMPLE Save for Later (Computer Maker’s Web Store)  Potential client goes to the web site and registers  Client then browses through products, placing in ‘shopping cart’.  If client decides not to buy at a point in time, can ‘Save For Later’ – keep the order for a period and come back later to purchase. Once a SFL transaction takes place, the computer maker routes to an ODS, does some analysis. 14
  15. 15. EXAMPLE SFL data may be used in a variety of ways  Customer may be sent an email  Transactions may be routed to call center for follow up (with customer registration data – email, phone, etc) – offer discounts, product information, etc. – try to convince the customer to purchase. 15
  16. 16. EXAMPLE How it works:  Save for later transaction on the web causes INSERT or UPDATE in certain DB tables  Trigger fires after INSERT or UPDATE and routes data to EAI queue.  EAI software reads the data in the queue does some simple transformations (mapping of data in this case) and forwards to ODS based on a set of rules (some transactions are ignored, for example) 16