Trivadis Integration Architecture Blueprint

Guido Schmutz Oracle ACE Director Principal Consultant / Partner DOAG SIG SOA Köln, 20.10.2010

Basel

·

Baden

·

Bern

·

Lausanne

·

Zürich

·

Düsseldorf

·

Frankfurt/M.

·

Freiburg i. Br.

·

Hamburg

·

München

·

Stuttgart

·

Wien

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

© 2010

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.
Düsseldorf

Hamburg

~170 employees

Services for more than 650 clients in over 1µ600 projects Over 160 Service Level Agreements

Frankfurt

Stuttgart Vienna Freiburg Basel Bern Lausanne Munich

More than 5'000 training participants Research and development budget: CHF 5.0 / EUR 3.3 mio. ~20 employees

Zurich

~370 employees

Trivadis ± the company

3

© 2010

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

4

20.10.2010

© 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

5

20.10.2010

© 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
6 20.10.2010 © 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

7

20.10.2010

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

Trivadis Integration Architecture Blueprint

9

20.10.2010

© 2010

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

10

20.10.2010

© 2010

Simple Integration Solution ± the beginning

11

20.10.2010

© 2010

Layering, Goals, Roles and Information Flow

12

20.10.2010

© 2010

Building Blocks and Roles

13

20.10.2010

© 2010

Combine Collection and Distribution Layer

14

20.10.2010

© 2010

Changed Information Flow (top right to lower right)

© 2010

Process Layer added for Orchestration

16

20.10.2010

© 2010

Role Orchestrator in Information Flow

© 2010

Concrete Building Block for Orchestrator

© 2010

Adding Levels to the Blueprint

19

20.10.2010

© 2010

Trivadis Integration Architecture Blueprint

20

20.10.2010

© 2010

Canonical Data Model: why ?

21

20.10.2010

© 2010

Canonical Data Model: why ?

22

20.10.2010

© 2010

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

23

20.10.2010

© 2010

Scenario Direct Connection ± Implemented by SOA

24

20.10.2010

© 2010

Synchronous to Asynchronous Messaging

Synchronous

asynchronous

25

20.10.2010

© 2010

Scenario Router

© 2010

Scenario Process ± Implemented by SOA

27

20.10.2010

© 2010

Scenario Population ± Implemented tradionally

28

20.10.2010

© 2010

Scenario Population ± Change Data Capture (CDC)

29

20.10.2010

© 2010

Scenario Population ± Orchestrated by SOA

30

20.10.2010

© 2010

Scenario CEP ± Event Processing Engine in Process Layer

© 2010

Process-Oriented Integration with Oracle SOA Suite

32

20.10.2010

© 2010

Modernization of an Integration Solution ± Before

I ntegration View Application
Process 13
Job S cheduler

I ntegration Domain
Mediation Collection/ Distribution

I ntegration
Communication

1
Shell call

7
call
33 20.10.2010 © 2010

Modernization of an Integration Solution ± After

34

20.10.2010

© 2010

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

35

20.10.2010

© 2010

Oracle Fusion Middleware

36

20.10.2010

© 2010

Oracle Data Integrator

37

20.10.2010

© 2010

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

38

20.10.2010

© 2010

IBM WebSphere

39

20.10.2010

© 2010

Microsoft BizTalk

40

20.10.2010

© 2010

Open Source and Spring

41

20.10.2010

© 2010

Thank you!

?
www.trivadis.com

Basel

·

Baden

·

Bern

·

Lausanne

·

Zürich

·

Düsseldorf

·

Frankfurt/M.

·

Freiburg i. Br.

·

Hamburg

·

München

·

Stuttgart

·

Wien

Sign up to vote on this title
UsefulNot useful