Evolving the Enterprise IT Legacy to SOA

Sundar Ramanathan

July 16, 2012

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

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 3Legacy Evolution to SOA© Copyright Capgemini 2011 All Rights Reserved

Agenda

L2SOA Project OverviewProject Team

Drivers for Legacy ModernizationApproach to Enable L2SOA

Key SOA PrinciplesOrganization and Process Metrics for L2SOA Engagement

Modernization StrategiesEIP Pattern-Based SI ApproachEIP Patterns: Cost & Complexity Analysis

SOA Governance Reference Model Legacy & Security

Case Study ASummary Q & A

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

L2SOA Project Overview

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

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.

L2SOA

Project OverviewProject Team

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

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)

L2SOA Project Overview

Project Team

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

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

Drivers for Legacy Modernization

Drivers for Legacy ModernizationApproach to Enable L2SOA

FUNCTIONAL

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.

BUSINESS

USABILITY

High Sustain Costs, Less Agility, No Business Metrics

Silo Architecture, Complex or No Interoperability, redundant /duplicate Information storage/processing, Less scope for Automation

Poor User Experience, Lack of SSO and Integration to new UI/ Presentation platforms/devices

Tightly Coupled Applications, Outdated Technology , Protocols with no support, Embedded Logic and Complex Configuration

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

Approach to Enable L2SOA

Combining TOGAF ADM and TOGAF SOA Guide with important L2SOA aspects

•SOA maturity assessment•Legacy expertise

•L2SOA Business case, ROI•Principle decision on extend or re*

•Current state legacy•Application Portfolio Rationalization

•Legacy transformation phases•Solution Building Blocks - SBBs•Vendor/tool selection

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

•Legacy Organization Management of change

Drivers for Legacy Modernization

Approach to Enable L2SOA

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

Key SOA Principles

Well-Defined Service Contract

Define Services with Appropriate Granularity

Key SOA PrinciplesOrganization and Process Metrics for L2SOA Engagement

Loosely-Coupled Services

Design Services for Stateless

Ensure Services have Appropriate Security Enforcement Standards

Adopt SOA Ontology/Vocabulary Standard

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

Organization and Process

Key SOA Principles

Organization and Process Metrics for L2SOA Engagement

Managed Transformation Program (Business, Technology )

Impact of Current IT Operations and Change Management & Legacy Processes

Skill Development and Training plan for Employees & Partners

Risk Analysis on lack of adoption and adaptability

Work across Business Boundaries and Service OwnershipROI Analysis based on Metrics and KPIs

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

Metrics for L2SOA Engagement

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 SOA PrinciplesOrganization and Process

Metrics for L2SOA Engagement

Key MetricsApplication UsageCost ReductionFunctional Re-useQuality of ServiceRevenue-generatedTime-to-MarketSecurity KPIs (data protection-related KPIs)

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

Modernization Strategies

Modernization StrategiesEIP Pattern-Based SI ApproachEIP Patterns: Cost & Complexity Analysis

Modernization strategies to enable the process of modernizing legacy applications using SOA

Enterprises need to select one or more strategies, after in-depth evaluation.

• Approach• Problem Solved/Value-Add• Risks and Mitigations• Architecture Building Blocks Involved

Key Modernization Strategies

Service Enablement Language Conversion Re-Architect Re-hosting of Applications

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

Modernization Strategies (Continued)

Modernization StrategiesEIP Pattern-Based SI ApproachEIP Patterns: Cost & Complexity Analysis

Strategy Approach Problem Solved/ Value Add

Risks & Mitigations Architecture Building Blocks Involved

Service Enablement Host Services with Integration Platforms

Re-use Assets, Improve Core Value, Automated Business Process

Difficult to identify useful functionality, Poor Documentation, System Disruption

Information: New Information ServicesTechnology: Legacy Integration Platforms, Hosting Service Containers

Language Conversion Convert to Modern Languages

Reduce Total Cost of Ownership(TCO), Time To Market (TTM), Adapt to SOA

Impossible to provide autonomous Services (Re-Architect), Unsupported functions in new language/environment, Skills

Information & Technology Platforms/ Frameworks

Re-Architect (New Environment) Restructure Functions and Code

Potential to fix old problems and introduce new functions

Budget and Architecture approach discussions

New ABB’s and SBB’s

Re-Architect (Old Environment) Restructure mainframe source to specific functions and expose with Legacy SOA adaptors

Reuse Business Functionality and Intellectual Property (IP)

Old Documentation, Code / Data changes, Need additional testing

Integration Solution patterns – leverage SBB’s

Re-hosting of Applications Platform Change, Needs combination of other strategies

Business Logic preserved, Agile Integration to Legacy, Reduce TTM, Improve Xabilities

Preserve existing investments, Legacy Integration Platform complexity

Virtualization – Architecture Building Blocks and reusable SBB’s

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

EIP Pattern-Based SI Approach

Modernization Strategies

EIP Pattern-Based SI ApproachEIP 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 MediationService EnablementScreen ScrapingRe-design

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

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 Modernization Strategies

EIP Pattern-Based SI Approach

EIP Patterns: Cost & Complexity Analysis

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

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.

.

SOA Governance Reference Model Legacy & Security

(*) See also the patterns (**) This needs to be explicitly taken into account as an architectural deliverable.

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

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 frameworkThe 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

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

Case Study A – Legacy Supply Chain Evolution to SOA

Case Study ASummary Q & A

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

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 Guidehttps://collaboration.opengroup.org/projects/ssdg/documents.php?action=show&dcat=14&gdid=26417

Case Study A

Summary Q & A

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

Questions

?Case Study ASummary

Q & A