20120716 l2 soa for enterprise-og-wsh-conf

Evolving the Enterprise IT Legacy to SOA
Sundar Ramanathan
July 16, 2012

Presenter Profile

 Sundararajan Ramanathan – Enterprise Architect @ Capgemini since June 2006
 TOGAF 9 & Capgemini IAF Certified Architect -
http://www.opengroup.org/togaf9/cert/protected/certuploads/30487.pdf
 10 years at Compuware, Detroit, Michigan
 5 years at Informix Software, California
 Education
 B.Sc (Physics), B.E (Indian Institute of Science), MBA (Wayne State University,
Michigan)
 Open Group
 Co-Author: Legacy Evolution to SOA Guide
 Chair: SOA for Business Technology Project
 NIST
 Contributor – Cloud Computing Forum – Taxonomy, Reference Architecture and
Roadmap

In collaboration with Legacy Evolution to SOA 2
© Copyright Capgemini 2011 All Rights Reserved

Agenda

Drivers for Legacy Key SOA Principles
L2SOA Modernization Organization and Process
Project Overview Approach to Enable Metrics for L2SOA
Project Team L2SOA Engagement

Modernization Strategies
EIP Pattern-Based SI
Approach SOA Governance Case Study A
EIP Patterns: Cost & Reference Model Summary
Complexity Analysis Legacy & Security Q&A


L2SOA Project Overview

Leverage the collective experiences of L2SOA practitioners to develop legacy
evolution best practices and lessons learned to improve the success of
L2SOA implementations. The content is therefore based on real projects.

 Current state problems and issues
 Key concepts, principles, and considerations related to L2SOA
 A high-level (general) approach to enable L2SOA
 Consolidated best practices, including metrics, architecture styles,
technologies, governance, etc.
 Historical case studies providing insight into how some of the concepts
described in the document are currently being applied

L2SOA
Project Overview
Project Team

L2SOA Project Team
Authors
 Xinfeng Chen, Hewlett-Packard
 Sundararajan Ramanathan, Capgemini
 Mukund Srinivasan, Capgemini
 Joost Van Der Vlies, Hewlett-Packard (Project Chair)
 Tejpal (TJ) Virdi, The Boeing Company (Project Chair)

Reviewers
 Ramagopal Allampalli, Cognizant Technology Solutions
 Jim Basler, Oracle
 Carleen Christner, Hewlett-Packard
 Pascal Dussart, LoQutus
 Ed Harrington, Architecting-the-Enterprise
 Venkata Kona, Wipro
 Martin Neuhard, Hewlett-Packard
 Carol Wang, Hewlett-Packard L2SOA
Project Overview
Project Team

Drivers for Legacy Modernization

Silo Architecture, Complex or No
High Sustain Costs, Less Agility, Interoperability, redundant /duplicate
No Business Metrics Information storage/processing, Less
scope for Automation

BUSINESS FUNCTIONAL
Tightly Coupled Applications, Outdated
Poor User Experience, Lack of SSO and Technology , Protocols with no support,
Integration to new UI/ Presentation Embedded Logic and Complex Configuration
platforms/devices

USABILITY TECHNOLOGY

 Maintenance costs are getting higher and higher
 Control over the application landscape and its dependencies is difficult
 The business needs to change faster than IT can support. Drivers for Legacy
Modernization
Approach to Enable L2SOA

Approach to Enable L2SOA

•L2SOA Business case,
•SOA maturity ROI
 Combining TOGAF ADM and assessment •Principle decision on
TOGAF SOA Guide with •Legacy expertise extend or re*
important L2SOA aspects

•Current state legacy
•Application Portfolio
Rationalization

•Legacy Organization
Management of change

•SOA Infrastructure versus Apps
•SOA maturity as input in legacy
modernization planning

Drivers for Legacy
•Legacy transformation phases Modernization
•Solution Building Blocks - SBBs
•Vendor/tool selection Approach to Enable
L2SOA

Key SOA Principles
 Well-Defined Service Contract  Loosely-Coupled Services

 Define Services with Appropriate Granularity  Design Services for Stateless

 Ensure Services have Appropriate Security Enforcement Standards

 Adopt SOA Ontology/Vocabulary Standard

Key SOA Principles
Organization and Process
Metrics for L2SOA Engagement

Organization and Process
 Managed Transformation Program  Work across Business Boundaries
(Business, Technology ) and Service Ownership
ROI Analysis based on Metrics and
Impact of Current IT Operations and KPIs
Change Management & Legacy
Processes

 Skill Development and Training plan for Employees & Partners

Risk Analysis on lack of adoption and adaptability

Key SOA Principles
Organization and
Process


 Metrics provide a baseline measurement to justify
an L2SOA engagement.
 Metrics should be measured at appropriate
intervals and reported for continues improvement
and measure the overall performance.

Key Metrics
Application Usage
Cost Reduction
Functional Re-use
Quality of Service
Revenue-generated
Time-to-Market Key SOA Principles
Security KPIs (data protection-related KPIs) Organization and Process
Metrics for L2SOA
Engagement


 Modernization strategies to enable the process of
modernizing legacy applications using SOA
 Enterprises need to select one or more strategies, after in-
depth evaluation.

 Key Modernization
Strategies • Approach
• Problem Solved/Value-Add
 Service Enablement • Risks and Mitigations
 Language Conversion • Architecture Building Blocks Involved
 Re-Architect
 Re-hosting of Applications
EIP Pattern-Based SI Approach
EIP Patterns: Cost & Complexity
Analysis

Modernization Strategies (Continued)

Strategy Approach Problem Solved/ Risks & Mitigations Architecture Building
Value Add Blocks Involved

Service Enablement Host Services with Re-use Assets, Improve Difficult to identify useful Information: New Information
Integration Platforms Core Value, Automated functionality, Poor Services
Business Process Documentation, System Technology: Legacy Integration
Disruption Platforms, Hosting Service
Containers

Language Conversion Convert to Modern Reduce Total Cost of Impossible to provide Information & Technology Platforms/
Languages Ownership(TCO), Time autonomous Services (Re- Frameworks
To Market (TTM), Adapt Architect), Unsupported functions
to SOA in new language/environment,
Skills
Re-Architect (New Environment) Restructure Functions and Potential to fix old Budget and Architecture New ABB’s and SBB’s
Code problems and introduce approach discussions
new functions

Re-Architect (Old Environment) Restructure mainframe Reuse Business Old Documentation, Code / Data Integration Solution patterns –
source to specific functions Functionality and changes, Need additional testing leverage SBB’s
and expose with Legacy SOA Intellectual Property (IP)
adaptors

Re-hosting of Applications Platform Change, Needs Business Logic Preserve existing investments, Virtualization – Architecture Building
combination of other preserved, Agile Legacy Integration Platform Blocks and reusable SBB’s
strategies Integration to Legacy, complexity
Reduce TTM, Improve
Xabilities

EIP Patterns: Cost &
Complexity Analysis


Enterprise Integration Patterns(EIP)
 Design Patterns
 Facilitate the system integration framework for Legacy to SOA evolution
 Complex enterprise systems
 Leverage a combination of EIP approaches
 Provide the capabilities to modernize their architecture.

Common Patterns

Enterprise Integration (Service Bus)
Queue-based Mediation
Service Enablement
Screen Scraping
Re-design
EIP Pattern-Based SI
Approach
Complexity Analysis

EIP Patterns: Cost & Complexity Analysis

The directly SOA related patterns have a high cost and
medium-to-high complexity.
High costs can be spread across many service-enabled
applications – both legacy and new, than web-service
based pattern as Screen-scraping EIP Pattern-Based SI Approach
Complexity Analysis

SOA Governance Reference Model
The Open Group SOA Governance Framework’s goal is to enable organizations to define and
deploy their own focused and customized SOA governance model.
.

(*) See also the patterns
SOA Governance
(**) This needs to be explicitly taken into account as an architectural deliverable.
Reference Model
Legacy & Security

Legacy and Security
Legacy System security Concerns for L2SOA transformation:
 Outdated technology and software
 Vulnerable to newer technologies
 Closed Encryption
 An ingenious manual administration of user names and passwords
 Session definition in the legacy system, especially in connect of SSO

Approach: Leverage Open Group Security Project framework
The Open Group Security for the Cloud and SOA project, describes
two sets of principles largely:
 A set of 20 generic security principles common to all designs
aiming to assure a secure IT architecture, ranging from
“security by design” to “data protection lifecycle”.
 A specific set of principles regarding assuring security in
architecting the cloud and the SOA environment, mainly
focused on policies, data protection and privacy, and cloud
specific principles.
SOA Governance
Reference Model
Legacy &
Security

Case Study A – Legacy Supply Chain Evolution to SOA

Case Study A
Summary
Q&A

Summary

 Business, Functional Usability and Technology are key drivers for Legacy to SOA
initiated modernization.
 The TOGAF (ADM) combined with TOGAF SOA Guide provides stepwise approach for
L2SOA transformation engagements.
 SOA initiative has to be measured for ROI and other performance concerns, using
industry standard metrics.
 Organization can adapt single or more modernization strategies based on the system
requirement.
 Meetings for the Legacy Evolution to SOA Working Group for next iteration.
 For more details, Please read: The Open Group Guide : Legacy Evolution to SOA
https://www2.opengroup.org/ogsys/publications/viewDocument.html?publicationid=12590&documentid=11481

 Refer to the L2S0A Working Group - https://collaboration.opengroup.org/projects/soa-legacy/protected/

 Download L2SOA Tutorial based on published L2SOA Guide
https://collaboration.opengroup.org/projects/ssdg/documents.php?action=show&dcat=14&gdid=26417

Case Study A
Summary
Q&A

Questions

?
Case Study A
Summary
Q&A

20120716 l2 soa for enterprise-og-wsh-conf

More Related Content

What's hot

Viewers also liked

Similar to 20120716 l2 soa for enterprise-og-wsh-conf

More from SUNDAR RAMANATHAN

Recently uploaded

20120716 l2 soa for enterprise-og-wsh-conf

Editor's Notes