Enterprise Architecture Consulting Group ?· Enterprise Service Bus Access Services Partner ... This…

Embed Size (px)

Text of Enterprise Architecture Consulting Group ?· Enterprise Service Bus Access Services Partner ......

  • Enterprise ArchitectureConsulting Group

    How to Deliver Complex SOA Projects Successfully: A look at Dos and Donts from Real Projects

    Impact 2009Session #1532

    Thomas Bohn, Jan Thielscher

    Las Vegas, May 5th, 2009

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 2

    Agenda

    Story of the Project

    Ingedients of Success

    Some more Secrets to Success

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 3

    The Customer and his Business

    One of the three long-established, very well known german mailorder giants

    ~3500 employees, HQ in Frankfurt

    Traditional catalog business dropped to 50%

    Web-based business gains importance, but systems are more and more limited

    Project Goals

    Establish new eCommerce platform

    approx. 700 000 000 EUR turnover per year

    20.000 tx (Customer Orders) per day

    Timeframe: 6 months

    Environment:

    several backend systems based on IMS v8.1

    Current shop hosted on 128 servers

    Replaced with Demand Ware

    New product data management based on SAP MDM

    rolled out

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 4

    System Environment and Goals

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 5

    The first thing to think about:

    Have a SOA vision and keep talking about it

    Google knows about 261k SOA visions

    How about yours?

    SOA means change.

    The way a business works.

    The way people work.

    Your SOA vision should be as unique as your business.

    Your vision should cover your needs not

    the latest trends

    Think about what you need to bring

    forward your business and what you

    already have in plcae

    No Bullshit Bingo use your companies /

    peoples terminology

    Talk Business in a way

    your management will

    understand.

    Talk Tech in a way your

    techies will identify.

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 6

    In the project first a Clear SOA Vision has been

    identified

    as the main Governing Thought

    Identify the Golden Guiding Principles you will never overrule again

    Understand domains required and their

    differences

    Define how business objects will

    interact / be maintained concerning

    application in services

    Define a tailoring principle for service to

    prevent monster size services

    Accept SOA is not healing your existing applications

    SOA will grow slowly from a single seed

    SOA lives from its design principles it

    does not heal badly designed

    applications!

    Use SOA principles to force clear

    design decisions and assign

    responsibilities

    Never ever accept bad behaviour in your new SOA design

    Encapsulate all bad behaviour

    Use processes or covering services

    while connecting to badly behaving

    applications

    Build compensations where

    necessary

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 7

    Project with dedicated Senior Sponsorship has

    been chosen

    Search the impacting projects

    Implementing SOA successfully, you will need power and influence

    Only projects impacting the business will have the right senior sponsorship

    Dont base your SOA strategy on a small, unimportant project. Rather look for real business impact.

    Set the vision with line-of-business and talk about the big picture

    Escalation never talks Tech

    Deciding for a power project, you automatically have senior attention

    You will escalate due to business reasons not for Tech reasons Understanding assured

    But remember: You are measured delivering the business benefit not the SOA

    Manage your Sponsor throughout the Project

    Be aware that your Sponsor knows how to escalate

    Align with the Sponsors other needs and goals

    Keep continuous track of your reporting, alert early!

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 8

    A Hands-On-Approach has been selected

    Why a hands on approach? Integration of new eShop with existing backend was very attractive candidate

    project due to high business impact

    Timeframe (6 months) challenging short

    CIO sponsorship has been assured

    Strong team with excellent resources available

    Artificial Approach

    Convince first, deliver later

    Spend much time on collecting and

    designing Principles

    Argue why SOA is better than

    standard integration way

    Write papers, saying how optimal it

    would be if

    Hands on Approach

    Deliver first, convince later

    Start with a small but strong set of

    principles, grow if necessary

    Dont argue, escalate due to

    business reasons!

    Implement a solution that serves the

    organisations requirements and sell it

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 9

    SOA Reference Architecture

    applied completely as Basic Stack

    Business Application

    Services

    Strategy and Planning Services

    Enterprise Service Bus

    Access Services

    Partner Services

    Process Services

    Information Services

    Interaction Services

    Business Events and Services

    Lifecycle Services

    Asset and Registry Services

    Development Services

    Management Services

    Infrastructure Services

    WebSphere Process Server

    WebSphere ESB

    WebSphere Service

    Registry & Repository

    WebSphere MQ

    WebSphere

    Partner Gateway

    WebSphere Business Modeler

    WBM Publish Server

    WebSphere

    Integration Developer

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 10

    Make sure your team covers the essential roles

    Business Analyst/Service Designer

    Deep business understanding

    Identifying real requirements

    Serving to deliver business

    benfits by suitable service

    deifnitions

    Service Developer Highly skilled Java developers

    deep understanding of

    WID, WAS, XML, JAXP, JMS

    knowledge of required

    back end technologies

    Chief Architect Being involved with overall architecture of project(s)

    Responsible for architecture conformity

    Enabling & supporting Service Designers & Developers

    Project Manager Capability to drive & escalate

    complex multi-project structures

    Understand and communicate

    SOA Vision

    Power to sell on Senior

    Management

    Test Manager Planning, implements & executing

    function and performance tests

    Coordinate with system context

    Supplying systems

    Identifying Service Metrics and

    organize Measurement

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 11

    Mediation Module

    How we prepared to launch the rocket

    Mass Data Transformation Mailorder Company But no unified

    catalog availbale Its an eShop 24x7 Unreliable Backends We dont wanna loose any order You can not touch the Host

    You have to guarantee a response time of 5

    sec. Because the customer is waiting in front of

    the Browser However the backend is not

    reliable and might even be gone completly.

    Ah, and by the way We are talking about

    orders So they can not get lost by any

    chance!

    My friend, the business consultant WebSphere JDBC Adapteroutbound

    WebSphere JDBC Adapter

    inbound

    Mediation Module

    eShopeShop

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 12

    dmc4Control

    Architecture Overview ESBSystems View

    SAP KAA

    ETL

    Demandware

    VpGate

    WSGW

    AVS RKMDM

    NES NBFhNBFu

    Internet

    E1

    E2

    E3

    Mass Data Transformation

    Complex Business Rules

    Integration

    Service Provision

    Process Management

    ESB

    Integration external

    Services

    Provide Services to external

    Users

    Monitoring & Reporting of

    Partner Communication

    CrossGate

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 13

    Enterprise Service Bus & Sub-SystemsHW Allocation

    E1

    E2

    E3

    Development

    Loadbalancer

    nxesb01

    ESBCell1

    nxesb02

    nxesb03

    nxesb04

    nxesb09

    nxesb10

    TSM HA Cluster (DB2/MQ)

    nxdb201 nxdb202 nxdb203

    dev

    ETL QS

    nxsfa05 nxsfa02

    ETLCell1

    nxsfa01

    nxsfa03

    nxsfa04

    ESB QS

    nxesb07 nxesb08WaWiCell1

    nxesb11

    nxesb12

    dev

    SAN(File Shares)

    ESBCell2

    nxesb05

    nxesb06

    WSGW

    nxpgw01 nxpgw02

    Status: 1.4.2009

    NAS(File Shares)

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 14

    Make your architecture visible and consumable

    Design a Solution Architecture and document it well

    but brief

    Outline the architectural layers, principles and

    approaches chosen

    Stay pragmatic, let feasibillity guide you

    If you are successfull, many people will want to know

    what you do and how

    this will save you a lot of time later ;-)

    Write down architectural decision

    you will need them again!

  • Impact 2009 DeliverComplexSOA.ppt EACG GmbH 15

    ASBO GBO ASBO

    or the importance of your (cannonical)

    datamodel

    ExportASBO GBO

    Mediation[Routing] ESB Service

    GBO - ASBOMediation

    [Routing] Import Backend

    Inbound Interface Provider Outbound Interface ProviderESB ServiceGBOASBO GBO ASBO

    ESB Service BackendService

    Requestor

    ESB

    Service

    X

    [GBO GBOVersion

    Mapping]

    [GBO GB