The Role of SOA in Enterprise Data Integration

Скачать презентацию The Role of SOA in Enterprise Data Integration

f62055baf7901a5b6ab3498869dfe603.ppt

Количество слайдов: 25

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 © 2005 Enterprise Architecture Solutions Ltd

Existing architecture Financial data site Data Warehouse

Data Integration issues • • 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 © 2005 Enterprise Architecture Solutions Ltd

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 © 2005 Enterprise Architecture Solutions Ltd

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 Roadmap Pilot Rollout © 2005 Enterprise Architecture Solutions Ltd

Service Oriented Architecture • What is a Service? – – – Vision & Strategy Roadmap Pilot Rollout 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 © 2005 Enterprise Architecture Solutions Ltd

What is a Service? Vision & Strategy Developer Service registry Procurement system Interface Exchang list. Exch get. Ex Finance system Roadmap Pilot Rollout CRM application Exchange. Rates. Service • list. Exchange. Rates. For. Currency. On. Date • get. Exchange. Rate. For. Currency. On. Date Data Warehouse © 2005 Enterprise Architecture Solutions Ltd

Service Infrastructure Vision & Strategy Developer Policy Procurement system Finance system Roadmap Pilot Rollout CRM application Procur Interface Exchang list. Exch get. Ex Policy Finan Service registry Enterprise Class Service Infrastructure Load Balancing Monitoring Security Failover Logging Alerts Data Warehouse © 2005 Enterprise Architecture Solutions Ltd

Strategic Technologies Vision & Strategy Developer WSDL Procurement system SOAP Finance system Roadmap Pilot Rollout CRM application SOAP Interface Exchang WS-Meta. Data. Exchange list. Exch get. Ex Service registry Service Infrastructure WS-Security WS-Reliable. Messaging WS-Policy Data Warehouse © 2005 Enterprise Architecture Solutions Ltd

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 © 2005 Enterprise Architecture Solutions Ltd

Roadmap Vision & Strategy 2004 2005 2006 2007 Roadmap Pilot Rollout 2008 Phase 1 Evolve Data & Application Integration Architectures Simple Services Enterprise Class Phase 2 Evolve B 2 B Integration Architecture Consuming External Services Publishing Services for External Consumption B 2 B Collaborations Phase 3 Evolve Process Integration Architecture Creating and Managing Shared Business Services Business Process Automation Business Activity Monitoring © 2005 Enterprise Architecture Solutions Ltd

Phase 1 Pilot architecture Vision & Strategy Financial Data Content Provider FTP pull load Roadmap Pilot Rollout Data Warehouse Exchange. Rates. Service Interface Exchang list. Exch get. Ex Policy Finan Service registry • list. Exchange. Rates. For. Currency. On. Date • get. Exchange. Rate. For. Currency. On. Date • etc. Service Infrastructure © 2005 Enterprise Architecture Solutions Ltd

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 © 2005 Enterprise Architecture Solutions Ltd

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 © 2005 Enterprise Architecture Solutions Ltd

Future Extended capabilities • Publish / subscribe • Enhancements to security • Meta data management • Write-backs • Transformation as a service? Further SOA usage • B 2 B data integrations • Event-based data distribution © 2005 Enterprise Architecture Solutions Ltd