© 2005 Enterprise Architecture Solutions Ltd The Role of SOA in Enterprise Data Integration Jonathan Carter Enterprise Architecture Solutions

© 2005 Enterprise Architecture Solutions Ltd

The Role of SOA in Enterprise Data Integration

Jonathan Carter

Enterprise Architecture Solutions


Introduction

• The Role of SOA• Case Study• Lessons learned• Future


The Role of SOA

• Allows you to evolve the data integration and information architectures

• Improves speed-of-delivery of solutions• Ubiquity of Web Services means the technology

barriers have been brought down• Abstracted view of the data• SOA, not SOT

– Technology constraints – Currently, not the answer for everything

• Strength lies in providing access to common data


Case Study - Global FMCG

– Globally-deployed EAI solution– New IT Strategy


Scenario

• Exchange Rates data• Distributed to many systems

– across the world – including several SAP systems

• Updated daily• Straight-forward data set


Existing architecture

Financial data siteFinancial data site

Message Message BrokerBroker

FTP pullFTP pull loadload

Data WarehouseData Warehouse

extractextract

<xml <do<o <e

<xml <do<o <e

<xml <do<o <e

<xml <do<o <e

ExratAB,1DE,F

<xml <do<o <e


• Multiple integration technologies• Multiple access points, no “single truth” for data• Difficult to manage load on data sources • Multiple security models and mechanisms• Unclear who owns the integration solution• Inconsistent mechanism for meta data sharing• Data usage tracking • Inconsistent data quality

Data Integration issues


Strategic drivers

• New IT Strategy• Convergence and consolidation of technology• Cost reduction• Simplification and clarity

– Infrastructure – Organisation

All of these had implications for the integration architecture


Delivering the strategic architecture

• Strategy definition– Defined a vision based on SOA– Select strategic technologies

• Roadmap– Plan controlled introduction of SOA approach and

technology

• Phase 1 Pilot– Candidate services– Scoped to internal integration only

• Phase 1 Rollout– Support organisation– Governance

Vision&

Strategy

Vision&

Strategy Roadmap Roadmap Pilot Pilot Rollout Rollout


Service Oriented Architecture

• What is a Service?– Useful– Discrete– Designed to be shared and client independent– Have ubiquitous access– Self describing

• Purpose of SOA is to separate the ‘what’ from the ‘how’– What do I need to access the service?– Where do I go to request the service?– I know what I need to give the service– I know what to expect to get back from the service

• Abstraction layer– Evolve architecture in a controlled way

Vision&

Strategy

Vision&

Strategy Roadmap

Roadmap

Pilot

Pilot

Rollout

Rollout


What is a Service?

ExchangeRatesServiceExchangeRatesService•listExchangeRatesForCurrencyOnDatelistExchangeRatesForCurrencyOnDate •getExchangeRateForCurrencyOnDategetExchangeRateForCurrencyOnDate

DeveloperDeveloper

ProcurementProcurementsystemsystem

FinanceFinancesystemsystem

DataDataWarehouseWarehouse

ServiceServiceregistryregistry

InterfaceExchanglistExchgetEx

CRM CRM applicationapplication

Vision&

Strategy

Vision&

Strategy Roadmap

Roadmap

Pilot

Pilot

Rollout

Rollout


Vision&

Strategy

Vision&

Strategy Roadmap

Roadmap

Pilot

Pilot

Rollout

Rollout

Service Infrastructure

DeveloperDeveloperProcurementProcurement

systemsystemFinanceFinancesystemsystem





Service InfrastructureService Infrastructure

Enterprise Class

MonitoringLoadBalancing Failover

Security

Logging Alerts

PolicyFinan

PolicyFinanPolicyFinan

PolicyFinan

PolicyProcurPolicyProcur


Vision&

Strategy

Vision&

Strategy Roadmap

Roadmap

Pilot

Pilot

Rollout

Rollout

Service Network


Vision&

Strategy

Vision&

Strategy Roadmap

Roadmap

Pilot

Pilot

Rollout

Rollout

Strategic Technologies

DeveloperDeveloperProcurementProcurement

systemsystemFinanceFinancesystemsystem






WSDLWSDLSOAP SOAP SOAP

WS-SecurityWS-Security WS-ReliableMessagingWS-ReliableMessaging

WS-MetaDataExchangeWS-MetaDataExchange

WS-PolicyWS-Policy


SOA strategy addresses the issues

• Multiple integration technologies– Common and robust technology infrastructure with ubiquitous

access• Multiple access points, no “single truth” for data

– Provides abstraction layer for evolving your integration architecture in a controlled manner

• Difficult to manage load on data sources – Abstraction protects data source

• Multiple security models and mechanisms – Manageability through policy and role-based approach

• Unclear who owns the integration solution– Devolves organisation integration responsibilities

• Inconsistent mechanism for meta data sharing – Inherently centralises meta-data

• Data usage tracking– All access provided through service interface

• Inconsistent data quality– Single interface to common data


Vision&

Strategy

Vision&

Strategy Roadmap Roadmap Pilot

Pilot

Rollout

Rollout

Roadmap

2004 2005 2006 2007 2008

Evolve B2B Integration ArchitectureConsuming External Services

Publishing Services for External Consumption

B2B Collaborations

Phase 2

Evolve Process Integration ArchitectureCreating and Managing Shared Business Services

Business Process Automation

Business Activity Monitoring

Phase 3

Evolve Data & Application Integration Architectures

Simple Services

Enterprise Class

Phase 1



Phase1 Pilot architecture



PolicyFinan

PolicyFinanPolicyFinan

PolicyFinan

ExchangeRatesServiceExchangeRatesService•listExchangeRatesForCurrencyOnDatelistExchangeRatesForCurrencyOnDate •getExchangeRateForCurrencyOnDategetExchangeRateForCurrencyOnDate

•etc.etc.

FinancialFinancialDataData

ContentContentProviderProvider

FTP pullFTP pull loadload DataDataWarehouseWarehouse

Vision&

Strategy

Vision&

Strategy

Roadmap

Roadmap

Pilot Pilot Rollout

Rollout


Rollout - technology


Vision&

Strategy

Vision&

Strategy

Roadmap

Roadmap

Pilot

Pilot

Rollout Rollout


Rollout – service network


Support OrganisationSupport Organisation• OperationalOperational• GovernanceGovernance

Vision&

Strategy

Vision&

Strategy

Roadmap

Roadmap

Pilot

Pilot

Rollout Rollout


Lessons Learned

• Enterprise initiative • Organisation buy-in• Enterprise class infrastructure• Ownership• Useful service• Service definition• Schema management• Don’t be afraid to grow slowly• Control your scope


Benefits realised

• Increased speed of delivery• Improved quality• Higher level of development• Usage controlled through configuration rather

than coding• Enterprise-wide monitoring, alerting and usage

tracking• ‘Point-to-point’ development, ‘brokered’

management and runtime


Future

Extended capabilities• Publish / subscribe• Enhancements to security• Meta data management• Write-backs• Transformation as a service?

Further SOA usage• B2B data integrations• Event-based data distribution


The Role of SOA

• Allows you to evolve the data integration and information architectures

• Improves speed-of-delivery of solutions• Ubiquity of Web Services means the technology

barriers have been brought down• Abstracted view of the data• SOA, not SOT

– Technology constraints – Currently, not the answer for everything

• Strength lies in providing access to common data


[email protected]

www.enterprise-architecture.com

Questions?


Documents

© 2005 Enterprise Architecture Solutions Ltd The Role of SOA in Enterprise Data Integration Jonathan Carter Enterprise Architecture Solutions