Basel · Baden · Bern · Lausanne · Zürich · Düsseldorf · Frankfurt/M. · Freiburg i. Br. · Hamburg · München · Stuttgart · Wien Trivadis Integration Architecture Blueprint Guido Schmutz Oracle ACE Director Principal Consultant / Partner DOAG SIG SOA Köln,

© 2010 Best Practices for Testing SOA Suite 11g based systems 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:  Blog:

© 2010 Hamburg Düsseldorf Frankfurt Stuttgart Munich Freiburg Vienna Basel Bern Zurich Lausanne ~370 employees ~170 employees ~20 employees Trivadis facts & figures Trivadis – the company3  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.

© 2010 Agenda Data are always part of the game.  Introduction  Road to the Integration Blueprint  Scenarios  Integration Platforms

© 2010 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

© 2010 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

© 2010 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

© 2010 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

© 2010 Trivadis Integration Architecture Blueprint

© 2010 Agenda Data are always part of the game.  Introduction  Road to the Integration Blueprint  Scenarios  Integration Platforms

© 2010 Simple Integration Solution – the beginning

© 2010 Layering, Goals, Roles and Information Flow

© 2010 Building Blocks and Roles

© 2010 Combine Collection and Distribution Layer

© 2010 Changed Information Flow (top right to lower right)

© 2010 Process Layer added for Orchestration

© 2010 Role Orchestrator in Information Flow

© 2010 Concrete Building Block for Orchestrator

© 2010 Adding Levels to the Blueprint

© 2010 Trivadis Integration Architecture Blueprint

© 2010 Canonical Data Model: why ?

© 2010 Canonical Data Model: why ?

© 2010 Agenda Data are always part of the game.  Introduction  Road to the Integration Blueprint  Scenarios  Integration Platforms

© 2010 Scenario Direct Connection – Implemented by SOA

© 2010 Synchronous to Asynchronous Messaging asynchronous Synchronous

© 2010 Scenario Router

© 2010 Scenario Process – Implemented by SOA

© 2010 Scenario Population – Implemented tradionally

© 2010 Scenario Population – Change Data Capture (CDC)

© 2010 Scenario Population – Orchestrated by SOA

© 2010 Scenario CEP – Event Processing Engine in Process Layer

© 2010 Process-Oriented Integration with Oracle SOA Suite

© 2010 Modernization of an Integration Solution – Before

© 2010 Modernization of an Integration Solution – After

© 2010 Agenda Data are always part of the game.  Introduction  Road to the Integration Blueprint  Scenarios  Integration Platforms

© 2010 Oracle Fusion Middleware

© 2010 Oracle Data Integrator

© 2010  Concepts and ideas of AIA can easily be mapped to the Integration Architecture Blueprint Oracle AIA and the Integration Architecture Blueprint

© 2010 IBM WebSphere

© 2010 Microsoft BizTalk

© 2010 Open Source and Spring

Basel · Baden · Bern · Lausanne · Zürich · Düsseldorf · Frankfurt/M. · Freiburg i. Br. · Hamburg · München · Stuttgart · Wien Thank you! ?