Releasemanagement in Integrationsprojekten - doag.org · Releasemanagement in Integrationsprojekten...

© OPITZ CONSULTING Deutschland GmbH 2015 Seite 1 Releasemanagement in Integrationsprojekten

OPITZ CONSULTING Vorlage Powerpoint 2011; Version 1.3; 10.05.2011; TGA, KSH

Titelfolie: •  Damit beginnt ein Vortrag. •  Haupttitel: 1zeilig! •  Untertitel: max 2. Zeilen •  Referent: Name, Funktion,

OC Niederlassung •  Logo: Optional.

Entweder ein Kunden/ oder themenbezogenes Logo verwenden. Ideal quadratisch, 3 Raster breit.

•  Fußzeile mit Haupttitel füllen.

Sven Bernhardt, Solution Architect

OPITZ CONSULTING Deutschland GmbH

Nürnberg, 18.11.2015

Releasemanagement in Integrationsprojekten



Titel und Inhalt: •  Dies ist das Haupttemplate

für Inhaltsseiten. •  Titel: 1-2zeilig! •  Inhalt:

•  3-7 Punkte o 2-3 Hauptpunkte mit Unterpunkten

•  Max bis zur 3. Ebene •  Logo: optional. rechts des

Titels zwischen den letzten beiden Rastern


Sven Bernhardt

n  Solution architect @OPITZ CONSULTING Deutschland GmbH

n  Oracle ACE

n  Author of articles, blogs, books n  Frequent speaker on diverse conferences

n  About OPITZ CONSULTING Deutschland GmbH n  10 locations over Germany and Poland n  Oracle Platinum Partner n  2 Oracle ACE Directors and 2 Oracle ACEs n  Business IT Alignment, BPM, SOA and

system integration, Application development, IT Infrastructure Management

n  Specialized in SOA, BPM, ADF & Application and much more



Agenda •  Diese Folie dient zur

Darstellung der Agenda •  Haupttitel: 1zeilig! •  Die Agenda sollte

möglichst nur die Hauptteile erläutern.

•  Die 1. Ebene ist numeriert, •  Sofern Ebene 2 genutzt

wird, ist diese als Spiegelstrichaufzählung zu gestalten.

•  Wichtig: Die Agenda ist kein Inhaltsverzeichnis!!!

Agenda

1.  Motivation

2.  Challenges

3.  Testing in integration projects

4.  Customer Case

5.  Summary



Teiltrenner •  Layout für Trennseiten

zwischen Teilen in einer Präsentation

•  Titel: 1-2zeilen •  Bitte den Titel immer auf die

Agenda abstimmen. •  Bitte die Teile gemäß

Agenda nummerieren. •  Eine Grafik ist auf dieser

Seite nicht vorgesehen.

1 Motivation









Why integration?

On-‐Premise Lösungen









Why integration matters

On-‐Premise Lösungen

Integra2on Backbone









Why integration matters

n  Avoiding uncontrolled growth n  Resolve fragmented IT architectures n  Transition to flexible IT system landscape

n  Increased agility

Integration is the key enabler for new technologies / trends!









2 Challenges









Challenges in integration projects

n  Complexity n  Singularities of legacy systems n  Lack of know-how n  Different technologies n  Platform

n  Distribution of systems / services

n  Number of systems / services n  Consistent, automated Deployment / Roll-out

n  Services n  System resources (Provisioning)

n  Automated testing n  Consistent monitoring (E2E)









How integration projects are often handeled

n  Static, mostly cumbersome approaches n  Waterfall n  V-Modell

n  Big, monolithical deliverables

n  „Big-bang“ software introductions

Source: http://www.commonplaces.com/blog/agile-vs-waterfall-how-to-approach-your-web-development-project/

Source: http://blog.procademysoftware.com/agile-project-management/









„Modern“ software development approach

n  Agile approach n  Scrum n  Kanban

n  Small, incremental deliverables

n  In-time business value generation

Source: http://blog.procademysoftware.com/agile-project-management/

Source: http://www.commonplaces.com/blog/agile-vs-waterfall-how-to-approach-your-web-development-project/









Continuous integration / delivery Source: https://guidelines.axonivy.com/projects/guides/wiki/Continuous_integration_delivery

Source: http://softwareengineeringdaily.com/tag/continuous-delivery/









Questions

n  How to slice the services? n  How to manage the source code? n  How to manage provisioning?

n  How to manage build and deployment? n  How to setup the development environment?

n  How to do testing? n  ...









Development infrastructure

n  Development environment n  Local development environment n  VM („Golden Image“) n  Docker + Vagrant

n  Continous integration / delivery infrastructure n  Dedicated CI environment (On-Premise) n  Dedicated CI environment (Cloud) n  TEST environment for CI (On-Premise)









3 Testing in integration projects









Why testing?

n  Types of tests n  Unit tests (JUnit)

n  XQuery n  XSLT n  Composites n  Servicebus

n  Integration tests n  Integration of different SOA components n  Example: Interaction Servicebus and SOA

n  System tests (E2E) n  Integration with external systems n  Example: Interaction between SOA and SAP n  Third party

Find bugs!

Missing

Available

Missing









OC SOA testing framework

n  Uses provided Oracle API n  Supports SOA Suite 11g and 12c n  Supports Unit testing for SB

n  Supports integration testing for SB and Composites n  Features:

n  Execute XQuery, XSLT tests n  Call services n  Intercept service calls n  Mock services (WS, JCA adapters, Human tasks)









Example

1 @Test 2 public void testService1() { 3 mockOsbBizService("Osb2/Abt2Service", new Delegate() { 4 public String serviceCallReceived( 5 String serviceName, String req) throws Exception { 6 recvReq = req; 7 return "<testresp>hallo</testresp>"; 8 } 9 }); 10 String recvResp = invokeOsbProxyService( 11 “Osb1/Abt1Service1",null, 12 "<testreq>hallo</testrq>"); 13 assertEquals("<testreq>hallo</testreq>",recvReq); 14 assertEquals("<testresp>hallo</testresp>",recvResp); 15 }









4 Customer Case









Numbers, data, facts...

Customer

Information technology

Project

Goal

•  42 locations world wide

•  ca. 9.000 employees

•  € 2,5 Billion turnover

•  Duration: 04/2014 – 03/2016

•  Replacement of existing integration platform

•  Modernization of existing IT system landscape

•  Flexible, easy-to-extend solution









System and Application Architecture - Requirements

n  High Availability n  Active – Active Clustering Topology n  Distributed across two data centers for redundancy reasons

n  Scalability n  Platform has to be scalable on physical, virtual and application layer

n  High Throughput n  About 70 mio. messages per year and steadily increasing

n  Low Latency n  Introduction of well-designed network architecture









System and Application Architecture - Requirements

n  Operatability and Maintainability n  Mechanisms to support application changes, fault analysis, etc.

n  Standardization n  Heterogenous integration landscape -> standardized platform

n  Future-proof n  Usage of future-proof and OOTB technologie









System context

n  Source platform: Oracle Interconnect (OAI) n  Target platform: Oracle Service Bus 11g n  Systems to integrate with:

n  Oracle E-Business Suite (CRM) n  SAP n  MSSQL n  Oracle DB

n  Technologies: n  XQuery n  Java EE n  WLST n  Ant, Maven









Topology









System architecture - Inbound External Domain Internal Domain

Extract and

TransformMeta

Message

JMS Queue

Delegate Enqueue

Customer HFp Post

Email Client J2EE

Enqueue

Insert or Update Incident

Extract and

TransformMeta

Message

Extract and

TransformMeta

Message

Customer Soap

Customer FTP

Customer HFp Post

Extract and

TransformMeta

Message

Customer Soap

Extract and

TransformMeta

Message

Dequeue Transform Modify & Enrich

Mail

EBS









System architecture External Domain Internal Domain

SMTP Gateway

JMS Queue

Customer A

Customer B

Customer C

Send Data

Get Data

Send Email

Post Message HTTP

Send Data

Enqueue

Dequeue

Customer A

Customer B

Customer C

Customer A

Customer B

Customer C

Customer A

Customer B

Customer C

EBS

Post Message SOAP

Modify & Enrich

Transform

Post Message HTTP

Post Message SOAP

Transfer Message

FTP

Customer A

Customer B

Customer C









Build and Deployment Architecture – Requirements

n  Physical separation of Build and Deployment environment n  Build and Deployment mechanisms should not be hosted on one server

n  Separation of Responsibilities n  Rights and privileges need to be separated in different roles

n  Light weighted Process n  Affordable for all involved roles

n  Continuous Integration and Automatic Tests n  Build and Deployment Scope

n  Smallest Build and Deployment Unit Project or Resource? n  Project based Deployment vs. Resource based Deployment

Resource based Deployment









Testing approach

n  Wanted: Consistent approach to allow n  Changeability n  Robustness

n  Usage of OC SOA Testing framework and SOAP UI for n  XQuery tests n  Component tests n  Integration tests (E2E)

n  Embedded JUnit and Integration Testing

n  Test Driven Development









Testing approach









Build and deployment procedure









5 Summary









„Magic Box“

n  Build and deployment n  Ant (SOA Suite 11g) n  Maven (SOA Suite 12c) n  Jenkins

n  Testing n  OC SOA Testing Framework n  SOAP UI









Lessons learned

n  Handle complexity in integration projects n  Avoid „Big Bang“ n  „Share and reign“ n  Adapt existing concepts and apply for integration scenarios

n  Testing is essential and has to be done immediately n  Test-driven development if possible n  Automating test to a certain grade within integration domain; mock external

systems

n  Define consistent build and deployment structure

Everything should be made as simple as possible, but not simpler (Albert Einstein)









Fragen und Antworten

Design: •  Das Farbschema ist im

Design als „OC 2009“ hinterlegt.

•  Ebenso sind die Schriftarten als „OC 2009“ hinterlegt.

•  Die Standardfarben sind:

Fragen?



Kontakt 1. fach: •  Diese Folie wird als vorletzte

Folie genutzt, um den individuellen Bezug zum Referenten herzustellen.

•  Als Foto muss ein quadratisches Foto des Referenten in qualitativ hochwertiger Form vorliegen.

•  Das Foto geht über 3 Rasterbreiten.

•  Die Daten der Adresse sollten vollst. eingegeben werden

Ansprechpartner bei OPITZ CONSULTING

Sven Bernhardt Solu%on Architect, Oracle ACE

OPITZ CONSULTING Deutschland GmbH Kirchstr. 6 -‐ 51647 Gummersbach eMail: sven.bernhardt@opitz-‐consul%ng.com Phone: 02261 -‐ 6001 0 Mobile: +49 172 2193529 Blog: hTp://thecaTlecrew.wordpress.com Design:

•  Das Farbschema ist im Design als „OC 2009“ hinterlegt.

•  Ebenso sind die Schriftarten als „OC 2009“ hinterlegt.

•  Die Standardfarben sind:

youtube.com/opitzconsulting @sbernhardt slideshare.net/opitzconsulting xing.com/profile/Sven_Bernhardt

Releasemanagement in Integrationsprojekten - doag.org · Releasemanagement in Integrationsprojekten...

Documents

Transcript of Releasemanagement in Integrationsprojekten - doag.org · Releasemanagement in Integrationsprojekten...