Trivadis Integration Architecture Blueprint

1. Trivadis Integration ArchitectureBlueprint Guido Schmutz Oracle ACE DirectorPrincipal Consultant / Partner DOAG SIG SOAKöln, 20.10.2010

2. Introduction • Guido Schmutz • Working for Trivadis for more than 13 years • leading and independent IT service company operating in Germany, Austria and Switzerland • Oracle ACE Director for Fusion Middleware and SOA • Co-Author of different books • Consultant, Trainer Software Architect for Java, Oracle, SOA and EDA • More than 20 years of software development experience • Contact: guido.schmutz@trivadis.com • Blog: http://guidoschmutz.wordpress.com/ Best Practices for Testing SOA Suite 11g based systems

3. Trivadis facts & figures • 11 Trivadis locations with more than 550 employees • Financially independent and sustainably profitable • Key figures 2009 • Revenue CHF 100 / EUR 66 mio. • Services for more than 650 clients in over 1‘600 projects • Over 160 Service Level Agreements • More than 5'000 training participants • Research and development budget: CHF 5.0 / EUR 3.3 mio. Hamburg ~170 employees Düsseldorf Frankfurt Stuttgart Vienna Munich Freiburg Basel ~20 employees Zurich Bern ~370 employees Lausanne Trivadis – the company

4. Data are always part of the game. Agenda • Introduction • Road to the Integration Blueprint • Scenarios • Integration Platforms

5. Why do we need Integration? • Why is integration necessary? • If everything would be build in a green field approach, we would 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

6. History of the Integration Architecture Blueprint • 2 years ago the Trivadis 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 • Goal was 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

7. History of the Integration Architecture Blueprint • Lot‘s of discussions lead to the german version of the book • 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

8. What is the Integration Architecture Blueprint ? • Integration Architecture Blueprint shows how to structure, describe and understand existing and new 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

9. Trivadis Integration Architecture Blueprint

10. Data are always part of the game. Agenda • Introduction • Road to the Integration Blueprint • Scenarios • Integration Platforms

11. Simple Integration Solution – the beginning

12. Layering, Goals, Roles and Information Flow

13. Building Blocks and Roles

14. Combine Collection and Distribution Layer

15. Changed Information Flow (top right to lower right)

16. Process Layer added for Orchestration

17. Role Orchestrator in Information Flow

18. Concrete Building Block for Orchestrator

19. Adding Levels to the Blueprint

20. Trivadis Integration Architecture Blueprint

21. Canonical Data Model: why ?

22. Canonical Data Model: why ?

23. Data are always part of the game. Agenda • Introduction • Road to the Integration Blueprint • Scenarios • Integration Platforms

24. Scenario Direct Connection – Implemented by SOA

25. Synchronous to Asynchronous Messaging Synchronous asynchronous

26. Scenario Router

27. Scenario Process – Implemented by SOA

28. Scenario Population – Implemented tradionally

29. Scenario Population – Change Data Capture (CDC)

30. Scenario Population – Orchestrated by SOA

31. Scenario CEP – Event Processing Engine in Process Layer

32. Process-Oriented Integration with Oracle SOA Suite

33. Modernization of an Integration Solution – Before

34. Modernization of an Integration Solution – After

35. Data are always part of the game. Agenda • Introduction • Road to the Integration Blueprint • Scenarios • Integration Platforms

36. Oracle Fusion Middleware

37. Oracle Data Integrator

38. Oracle AIA and the Integration Architecture Blueprint • Concepts and ideas of AIA can easily be mapped to the Integration Architecture Blueprint

39. IBM WebSphere

40. Microsoft BizTalk

41. Open Source and Spring

42. Thank you! ? www.trivadis.com