Integration blueprint-short-en
12 likes3,866 views
This document outlines the Trivadis Integration Architecture Blueprint, which provides an approach for structuring, designing, and understanding integration in application landscapes. It defines four layers - process, mediation, collection/distribution, and communication - to model integration at the architecture level. The blueprint has evolved over several years based on experience with many integration projects. It aims to provide a vendor-neutral methodology for integration modeling. The document also provides examples of how common integration scenarios can be depicted using the blueprint layers and discusses how various integration platforms map to the blueprint.
![Service Oriented Architecture: An Integration Blueprint Guido Schmutz Oracle ACE Director Principal Consultant / Partner [email_address]](https://image.slidesharecdn.com/integration-blueprint-short-en-100729164617-phpapp01/85/Integration-blueprint-short-en-1-320.jpg)
Integration blueprint-short-en
- 1. Service Oriented Architecture: An Integration Blueprint Guido Schmutz Oracle ACE Director Principal Consultant / Partner [email_address]
- 2. Agenda Integration Architecture Blueprint Road to the Integration Blueprint Scenarios Integration Platforms 29.07.2010 Data are always part of the game.
- 3. Structure of the book – what‘s in it? Basic Principles Base Technologies Integration Architecture Blueprint Implementation Scenarios Vendor Products for Implementing the Trivadis Blueprint 29.07.2010
- 4. Why do we need Integration? Why is integration necessary If everything would be build in a green field approach, we theoretically have no integration concerns at all Goal of SOA: Increased Intrinsic interoperability => Thomas Erl systems that are not interoperable need to be integrated Integration can be seen as the process that enables interoperability Integration on different levels Transport Protocol Message Protocol Different Vendor products/stacks/frameworks 29.07.2010
- 5. History of the Integration Architecture Blueprint 2 1/2 years ago the Architecture Board started to document the „Integration Architecture Blueprint“ based On our knowledge and experience with lots of traddional as well as more modern integration projects Database based solutions ETL Solutions Enterprise Application Integration (EAI) Service-Oriented Integration We wanted to define and document an easy to use approach and methodology to structure, design and understand existing as well as new application landscapes from the perspective of integration Vendor neutral Product neutral Approach neutral (SOA, EAI, ETL), applicable to mixed use cases 29.07.2010
- 6. History of the Integration Architecture Blueprint Lot‘s of discussions lead to the german version of the book, published almost 2 years ago Together with my co-authors Peter Welkenbach and Daniel Liebhard Good feedback from our colleagues, partners and customers lead us to the idea of publishing it in English Updated and actualized version of the german book Actual, up-to-date mapping of vendor platforms to the blueprint 29.07.2010
- 7. What is the Integration Architecture Blueprint ? Integration Architecture Blueprint shows how to structure, describe and understand existing application landscapes from the perspective of integration Easy to use approach, with no or minimal tooling support (whiteboard or graphical tool like Visio are enough) Ideally show a given integration solution on one single page Architecture (an design) level, NOT implementation level Deviding the integration architecture into 4 layers Process Mediation Collection and Distribution Communication (graphical) Domain Specific Language (DSL) for describing integration concerns 29.07.2010
- 8. Trivadis Integration Architecture Blueprint 29.07.2010
- 9. Agenda Integration Architecture Blueprint Road to the Integration Blueprint Scenarios Integration Platforms 29.07.2010 Data are always part of the game.
- 10. Simple Integration Solution – the beginning 29.07.2010
- 11. Layering, Goals, Roles and Information Flow 29.07.2010
- 12. Building Blocks and Roles 29.07.2010
- 13. Combine Collection and Distribution Layer 29.07.2010
- 14. Process Layer added for Orchestration 29.07.2010
- 15. Adding Levels to the Blueprint 29.07.2010
- 16. Trivadis Integration Architecture Blueprint 29.07.2010
- 17. Canonical Data Model: why ? 29.07.2010
- 18. Agenda Integration Architecture Blueprint Road to the Integration Blueprint Scenarios Integration Platforms 29.07.2010 Data are always part of the game.
- 19. Scenario Population – Implemented tradionally 29.07.2010
- 20. Scenario Process – Implemented by SOA 29.07.2010
- 21. Scenario Population – Change Data Capture (CDC) 29.07.2010
- 22. Scenario Population – Orchestrated by SOA 29.07.2010
- 23. Scenario Direct Connection – Implemented by SOA 29.07.2010
- 24. Scenario Data Grid 29.07.2010
- 25. Modernization of an Integration Solution – Before 29.07.2010
- 26. Modernization of an Integration Solution – After 29.07.2010
- 27. Agenda Integration Architecture Blueprint Road to the Integration Blueprint Scenarios Integration Platforms 29.07.2010 Data are always part of the game.
- 28. Oracle Fusion Middleware 29.07.2010
- 29. Oracle Data Integrator 29.07.2010
- 30. Oracle AIA and the Integration Architecture Blueprint 29.07.2010
- 33. Open Source and Spring 29.07.2010
- 34. Thank you! ? www.trivadis.com