1 / 126

Enterprise Application Integration

Enterprise Application Integration. Ruh, Maginnis, Brown (2001) text Vendors Internet Resources Web Services EAI Journal online and print. Enterprise Application Integration. Packaged applications Legacy applications Data from variety of sources Stovepipe apps.

pravat
Download Presentation

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. Enterprise Application Integration • Ruh, Maginnis, Brown (2001) text • Vendors • Internet Resources • Web Services • EAI Journal online and print

  2. Enterprise Application Integration • Packaged applications • Legacy applications • Data from variety of sources • Stovepipe apps

  3. Enterprise Application Integration • C 1 Business Drivers • C 2 Types of Integration • C 3 Building Blocks • C 4 MOM • C 5 Object arch • C 6 Transaction arch

  4. Enterprise Application Integration • Stats • 30-60 % IT resources on integration • 35 % of budgets • 85 % IT projects not completed • 58 % large projects over budget • 63 % projects off schedule • 58 % report success below 50%

  5. Enterprise Application Integration • Select • Architect • Apply • Common Building Blocks

  6. Enterprise Application Integration • Messaging Architecture • IBM MQ Series • Object Architectures • EJB • Transaction Architecture • BEA Tuxedo

  7. Enterprise Application Integration • Introductory text • Look at concepts • Then vendor applications • Web Services later

  8. Enterprise Application Integration • Technology is always changing • Concepts • Frameworks • Application in an organization

  9. Enterprise Application Integration • Key Facts p.1 • Definition p.2 • Enterprise Application Integration is the creation of business solutions by combining applications using common middleware.

  10. Enterprise Application Integration • Middleware is application-independent software that provides services that mediate between applications. • Multiple types

  11. Enterprise Application Integration • Goals • Quick, easy, cheap • Improved relationships • Supply chains • Mergers and acquisitions • BPI • Speed

  12. Enterprise Application Integration • 360 view of relationships p.4 • Stovepipe applications definition p.5 • Examples and issues • Supply-chain • Examples and issues

  13. Enterprise Application Integration • XML p.6 • BPI • Speed p.7 • Legacy applications • Packaged solutions COTS

  14. Enterprise Application Integration • Internet p. 8-11 • Dot-bomb • B2B, B2C • Intranets • Extranets

  15. Enterprise Application Integration • Barriers to EAI • Custom API, application programming interfaces • Vendors • Skills – EAI • Security

  16. Enterprise Application Integration • Types of integration • Chapter 2 • Key facts • Integration model defines how applications will be integrated by defining the nature of and mechanisms for integration

  17. Enterprise Application Integration • Presentation • Data • Functional • Pages 19-21

  18. Enterprise Application Integration • Presentation integration model allows the integration of new software through the existing presentations of the legacy software. This is typically used to create a new user interface but may be used to integrate with other applications.

  19. Enterprise Application Integration • Data integration model allows the integration of software through access to the data that is created, managed and stored by the software typically for the purposes of reusing or synchronizing data across applications.

  20. Enterprise Application Integration • Functional integration model allows the integration of software for the purpose of invoking existing functionality from other new or existing applications. The integration is done through interfaces to the software.

  21. Enterprise Application Integration • Coupling • White box integration • Black box integration

  22. Enterprise Application Integration • Presentation integration model p.22 • When to use it • Green screen • One look • Only choice • Examples

  23. Enterprise Application Integration • Pros and Cons • Skill level • Speed • Less complex • Performance low • Most limiting

  24. Enterprise Application Integration • Data integration p. 24 • Batch file transfer • Open database connectivity • Data access middleware • Data transformation

  25. Enterprise Application Integration • When to use it • Analysis of data • Data warehouse • Different vendors • Synchronize • EIS

  26. Enterprise Application Integration • Pros and cons • Flexible • Reused • Lack of functionality • Simple access to data • No logic access

  27. Enterprise Application Integration • Functional integration model p.29 • Business logic • RPC’s • Distributed processing middleware

  28. Enterprise Application Integration • Distributed processing middleware • MOM • DOT • TPM

  29. Enterprise Application Integration • MOM • Passing messages • IBM MQ series • Talarian Smart Sockets

  30. Enterprise Application Integration • Distributed object technology • OMG CORBA • Microsoft COM+ • Sun’s J2EE

  31. Enterprise Application Integration • TPM • Transactions • BEA Tuxedo

  32. Enterprise Application Integration • Breadth of functional integration • Data consistency • Multistep process • Plug and play components

  33. Enterprise Application Integration • Data consistency integration is integration through the code of an application where the purpose is to access or update data. The integration facilitates the communication of data and actions.

  34. Enterprise Application Integration • Multistep process integration, also known as straight-through processing, is the integration of applications where there is not only communications of requests but also the coordination and management of these requests across applications. The integration facilitates communication of the request and manages the flow and sequencing.

  35. Enterprise Application Integration • Plug and play component integration is the integration of applications where a well-defined interface exists that allows a component to be easily connected with other components without modification. The integration facilitates the communication of requests and handles all of the interface definition and management.

  36. Enterprise Application Integration • Table 2.1

  37. Enterprise Application Integration • When to use it • Difficulty • Performance • Future reuse • Examples

  38. Enterprise Application Integration • Pros and cons • Robust • Flexible • Reuse • Complex • Difficult software • May not be possible

  39. Enterprise Application Integration • Chapter 3 p.39 • Key facts

  40. Enterprise Application Integration • For EAI solutions need • Methodology • Technology

  41. Enterprise Application Integration • Communication model • 2 choices • Synchronous – wait until reply is received • Asynchronous – continue processing

  42. Enterprise Application Integration • Receiver is software that receives a request from a sender. • Request is a formatted set of actions and data sent from a sending piece of software to a receiving set of software

  43. Enterprise Application Integration • Reply is a formatted set of data and possibly associated actions that are sent as a result of a request • Sender is software that sends a request to another software component

  44. Enterprise Application Integration • Synchronous communication occurs when the communication between a sender and receiver is accomplished in a coordinated manner. This requires the sender and receiver to operate dependent on the processing of request.

  45. Enterprise Application Integration • Interactive systems require synchronous communication. • Examples

  46. Enterprise Application Integration • Three types of synchronous communication • Request/Reply • One-Way • Synchronous polling

  47. Enterprise Application Integration • Request/reply communication is a form of synchronous communication where a sender makes a request of a receiver and waits for a reply before continuing to process. • Page 42

  48. Enterprise Application Integration • One-way communication is a form of synchronous communication where a sender makes a request from a receiver and waits for a reply that acknowledges receipt of the request. • Page 43

  49. Enterprise Application Integration • Synchronous polling communication is a form of synchronous communication where a sender communicates a request to a receiver but instead of blocking continues processing. At intervals defined by the developer, the sender checks to see if a reply has been sent. When it detects a reply it processes it and stops any further polling for a reply.

  50. Enterprise Application Integration • Asynchronous communication occurs when the communication between a sender and receiver is accomplished in a manner that allows each of them to operate independently of the other. The receiver of the request is under no obligation to handle the communications or respond to the sender. The sender continues to operate once the request is sent without regard to how the receiver handles the communication.

More Related