soa governance

SWG - Emerging Technologies

IBM internal use only © 2005 IBM Corporation

SOA governance

Creating a culture of service re-use

Tony Fricko, jStart Program [email protected]


© 2004 IBM CorporationIBM internal use only

AgendaGovernance & IT governance– skippedSOA – what is there to manage and why is this a new scenario compared to existing systems management practice– skipped

Standard Life, Edinburgh– Evolution from a hub centric architecture– Organization & tools to foster and measure re-use

Government organization– IT provider for multiple government agencies– Domain design, metadata repository, management



Who is jStart?jStart is IBM’s Software Group’s worldwide program for “jumpstarting”the implementation of emerging, on demand software technologies in customer environments

Customer and jStart team work in partnership to implement an on demand application utilizing specific standards-based technology themes

Objectives are to accelerate technology maturity and market adoption

Customer application promoted as reference implementation



Provider Projects

Consumer Projects

Component Based Development

Projects

Legacy Wrapping Projects

Composite Application

Projects

Solution Delivery Projects

ApplicationIntegration

Projects

Service Bus Projects

Service Supply Projects



Who is Standard Life ?Established over 170 years ago, Standard Life is now the largestmutual life assurance company in Europe. They have over 4 million customers, £100 billion under management and a string of awards to their credit. For the last four years they have been voted Personal Investment Marketing Show Life and Pensions Company of the Year by Independent Financial Advisers.

Standard Life are split into three divisions, or businesses. These are:– Life and Pensions (principally pensions)– Investments (They currently have in excess of £100Billion funds

under management)– Standard Life Bank (This is a telephone based savings bank which

also offers flexible mortgages. They currently have about 15% ofthe UK mortgage market.)



Current IT EnvironmentSites– Data Centre– Service Continuity Centre

Mainframe (3)– Z/OS– Transaction Monitors

• IMS• CICS

– Databases• IMS• DB2

Off-mainframe– P690’s

• AIX• WebSphere Application Server

(v4/v5)• WebSphere MQ• WebSphere MQ integrator (v2.1/v5)• WebSphere MQ Workflow

– Databases• DB2 UDB• Oracle

– AS/400• Workflow (AWD)

Approx 1000 headcount in Service Development and Delivery



Design Patterns

1995 1996 1997 1998 1999 2000 2001 2002 2003 2004

Folders

Redevelopment

IBM

Oracle

M/Soft

ADA1

eMutual Funds

ADA2

Hub Centric Design Pattern / SOA



HCDP – Hub Centric Design Pattern

Websphere MQWorkflow

'Intelligent Switch‘,“The Hub”,“The Integration Layer”

DeterministicRouting

Logging

Infrastructure Services

Post

Financial Business Services

Credit check

Life & Pensions Services

Maintain policyProvide customer infoChange name

EDIeMail

Extranet

Exchange

SWIFT

Client 'Channels'

Investment Services

Fund switchSell unitsBuy units

Internet

Telephone

ProtocolTranslation

Poison MessageHandling

Business Services



HUB and SPOKEMESSAGING

(MQSeries Integrator - 1999)

POINT TO POINTMESSAGING

(MQSeries - 1993)

Enterprise Service Bus(WebSphere MQ & WBI Message Broker V5 - 2003)

Multiple servers/transports work together to create the Bus

–Message Broker adds rich mediation and transport options to MQ

–Secure connectivity within an internet and across the Internet

Support for distributed message routing and mediation

A robust enterprise infrastructure for SOA and Web Services

IBM Business Integration: Enterprise Service Bus evolution



HCDP – Hub Centric Design Pattern

Rationale– Fully implement the hub architecture

vision

– Ensure designs across IS are consistent

– Ensure best use is made of current technology

– Put in place a framework within which new technologies can be utilised when appropriate



HCIHub Centric Infrastructure

ADA Framework GPP Framework

Folders CSOL ContractEnquiry eJoiners SDS Dundas

HCDPService Oriented Architecture ADA HCDP

Integration Hub

HCDPPatterns Framework

Applications delivered to the business

Frameworks executed at run-time

Infrastructure in support of business applications

Architecture, design & implementation patterns shaping the business applications

Framework providing pattern development resource & governance

GTXFramework

CIT

HCA – Hub Centric Architecture



Hub Centric ArchitectureSOA

How Is It Made Available?



Pattern Documentation

Problem

Context

Selection criteria

Solution

Consequences

Examples

Next Steps

Related Patterns



Implementation Specific Information

User Guides–Detailed “how to” guides–Published for all frameworksInfrastructure releases– Infrastructure design & implementation

documentsSample Application–Java based

• Various clients• Exercises the different layers• Used as a tutorial and a regression test tool



Hub Centric ArchitectureSOA

How to enable reuse …and measure it



Business Services Management TeamStaff with dedicated responsibilities for (business) services– They are typically part of the development teams

Represent indeed a Centre of Excellence on SOA– Define best practices and proactively promotes them– Manage the ‘business services catalogue’

• Documentation and publicizing– Define new services and interfaces– Manage change– Measure services – ‘impact analysis’– Define the cost for a service– Constant evaluation of the model



Business Service Directory - BSD

Runtime BSD– IBM DB2 UDB implementation

– Accessed only by application framework

– Contains• End points (WMQ Queues)• Quality of service attributes, e.g.

– Service criticality (determines error processing)

– Maximum response time



Business Service Catalogue

Analysis & Design Time Catalogue– Business Service Definitions

• Interfaces (WSDLs)• Functional & non-functional

requirements– Enhanced by impact analysis

information

– Supported by the Business Service Management team



Business Service Catalogue

Business

Service

Catalogue

Business

Service

Directory

HCDP

Extracts

Catalogue

Statistics

1

2

3

4Lotus Notes

DB2

Logs and

Live feeds

Development use to assess the list of existing services for potential reuse

Development and Deliveryto review service details for impact analysis purposes



HCA Application Statistics

73 Applications running on HCI

69 in-house built

34 ADA Applications

35 HCDP Applications

240 Business Services



Service Reuse Measurement

Catalogue

Statistics



Volumes

400,000 Servlet invocations per day

800,000 EJB invocations per day

1,600,000 IMS Transactions per day– (40% of total IMS Workload)

5 p690 CPUs in production

1.3 CPU p.a. expected growth



Systems Management

Standardised Logging Mechanism–Events correlated end-to-end across

heterogeneous systems–Centralised aggregation and processing

of events (WMQ based)–Specific events can be configured to raise

systems mgt events (Tivoli/Solve). Opt-in.–Supports audit and management info

functions



Systems Management

Standardised Component Interaction Logging Mechanism–Run-time view of component interactions

–Aids impact analysis decisions

–Provides reuse statistics

–Data mining tool provided



Lifecycle management

There will always be more than one version available in production !

Versioning impact at all levels:–Business services (typical 3 versions available)–Framework– Infrastructure

Production staging – bau–Development / test / deploy



Benefits to operation

Same number of staff since introduction of SOA / business services

Despite 900% increase in operational load

Still room to grow !

Why ?–All ‘business services’ behave the same–Staff doesn’t have to worry anymore about the

functions– ‘Does the business service adhere to SOA

pattern ?’



Evolution - Webservices

Gentle evolution to Web Service Standards

– Small steps may offer significant benefit• HCDP based on industry standards• Improved development & operation tooling• Development productivity gains

Leverage investment in SOA by enabling process automation using published services.



Key to success at Standard Life1. People

– Business services management team

2. Processes & tools– Patterns

• Handbook, guidelines, framework descriptions, etc– e2e coordination from analysis / design / deployment– Business service catalogue

• Supporting tools for data mining

3. Infrastructure– HCI - Hub centric design infrastructure can comfortably

accommodate SOA



SOA design considerations

Austrian e-gov project



The customer environment

Central IT for government agencies

Privatized IT of Ministry of Finance

Offers IT services for all government intuitions–Ministries

–European Union projects

–Expansion into Central Europe

1.000 employees



Roadmap to SOA

Decided to model business and IT architecture on services / SOA

Executive initiative sponsored by CEO

Have some messaging technology today

Pilot project for 2005–10 persons dedicated

Rollout from 2006 onwards



Analysis of current stateDevelopment– Tools are project and customer specific– Disruption in technology and techniques from Design to

implementation to operation

Architecture– Heterogeneous systems, multiple, inconsistent frameworks

Infrastructure– EAI (some messaging), Output, Payment, Portal– Monolithic: SAP HV, PM– In development: BI/DWH, DMS/Archive



Implementation phasesPhase I Phase II Phase III

Study Domain concept

Conceptual SOA

Security concept

Framework- und Bus-Analysis

Developmentarchitecture

Detailedarchitecture

Service-BusDetailed specs

Implementation specifics for ESB

Pilot(Specification & Impl.)

Domain for pilot(Specification & Impl.)



Why develop a domain model ?Goals– Manageable complexity of interfaces– Reduction of redundant functions and data– High flexibility to external requestors– Stable services to external requestors– Clearly defined responsibilities and ownership of

processes, functions and data– Flexible exchange of elements within a domain,

without impact to other domains

Standardization



Criteria for domain aggregation

High coherence of function and data

Services and applications have high affinity in business logic

Flexibility within domains, but exposing stable interfaces

Domains are autonomous



Domains

Security

Access rightsmanagement

Justice

Payment

Penalsystem

SAP HV

SAP PM

Tax / Finance admin

SAP DL

Customs VSB

Companyregistry

OutputManagement

Archive

Gov processAutomation

Portal IntegrationServices

Knowledgemanagement

Documentmanagement

Input-management

completed

In process

Not yet defined



Example for Domain StructureB

ack

en

dFro

nte

nd

help.gv.at Finance-online

Signature-services

HV

BI/DWH …

ELAK PM Output Mgmt. …

Services Services Services Services Services

Services Services Services ServicesServices

DomainService Bus



Service Bus

Legend:

... Application

... Service

Application and service structure of domains

Domain A Domain B Domain C

Technical domain Cross-domain

A2

A8

A7

A4

A3A1A5

Ax



Service types within domain architecture

Intra-Domain Services–Core Services (e.g. security for portal)–Application Services (e.g. ‚child support‘)

Domain Services–Lightweight Domain Services –Domain Services (e.g. land registry enquiry, ...)–Cross Domains Services (e.g. ZIP code, bank

code, person register, ...)–Technical Services (e.g. MOA, Logging, ...)



Example for ‚school assistance‘

ArchivePayment

processprocess

Service Bus

Issue request

Issue request

Initiate payment EDIFACT

Archive request &decision

Validaterequest

Validaterequest

Evaluaterequest

Evaluaterequest

SecurityFinance / Tax admin

Output-Management

MOA-IDauthentication

Proof of income Deliver decision

parentsAssisting

Gov offices IT declinedecline

approveapprovearchivearchive

IT

IT



Service granularityBase Services (Service-Provider)– Fine granularity, simple function– E.g. Zip code, banking sort codes, currency conversion, etc

Business Services (Service-Provider)– Highly granular, specific business function– stateless or stateful

Workflow Services (Service-Bus)– Complex workflows– Describe business processes– Stateful, support ‘long transactions’– Standards: BPEL



Management concepts

LoggingRepository

SecurityRepository

Service &Config

Repository

Service-Bus and Execution environment

ServiceFramework

XML-DB LDAP RDB

Eclipse-cased Browser-based

Dashboard / Admin console

RSS-Feed

CBEStandard



AC – ISC – Integrated Solution ConsoleOne Stop Shopping for all

Administrative TasksOne consistent user

interface across product portfolio

Common runtime infrastructure and development tools based on industry standards, component reuse

Provides a presentation framework for other autonomic core technologies

Through a unified portal

Standards-based: J2EE, JSR168



Supporting an SOA culture – Take awayDomain concept– Necessity to take into account multiple customer / data / security

environments, multiple frameworks and development environments

Multiple service types– Responsibility being split between central / distributed

organizational entitiesService ‘managers’– Ensure consistent design, adoption and re-useMetadata repository– For development as well as deployment (runtime)– XML repository, XQUERY support– Essential for versioningVersioning needs to be a central design consideration throughout



ibm.com/services/soa

We’ve built the foundation. Let’s raise the roof.

Questions ?

soa governance

Documents