iSeries Modernization: RPG/400 to Java Migration

eCube’s transforma/on process for legacy RPG applica/ons

iSeries Moderniza/on: RPG/400 to Java Migra/on

eCube Introduc-on

eCube Systems is: – A leader in Enterprise Evolu/on and Moderniza/on Services

– An IBM Advanced Business Partner •  IBM SOA Ready •  IBM Linux Ready

– An HP Business Partner – A member of the OMG Architecture-‐Driven Moderniza/on Task Force

– A member of the OMG SOA Consor/um

Typical Scenario Overview

•  Client is running numerous applica/ons across various business units – Hundreds of users across the company

•  Typical applica/on characteris/cs: –  Run in iSeries/ AS400 environment –  Primarily built in RPGIV with some COBOL or RPG III – Data primarily resides in IBM DB2 Universal Database –  Comprised of 2000+ logical files, 1500+ physical files and 5 million lines of codes

– Has undergone mul/ple itera/ons over the past 15-‐20 years

Typical Applica-on Moderniza-on Goals

•  Moderniza/on considera/ons under discussion include: – RPG migra/on to Java/J2EE or .NET – Re-‐architec/ng database environment based on standard data architecture principles

– Web-‐enable with framework/pa]ern like Model/View/Controller architecture

Typical Applica-on Moderniza-on

•  Objec/ves include: – Ability to assess situa/on and develop moderniza/on plans quickly

– Establish moderniza/on roadmap and proof-‐of-‐concept reference implementa/on that can be adjusted as addi/onal analysis and business requirements are iden/fied

RPG Summary

RPG •  Is a fixed format programming language •  Has a set of opcodes corresponding to statements or verbs in other languages

•  Has operands in fixed posi/ons –  Factor1 and factor2 operands

•  Uses indicators to check the results of previous opera/ons and func/on keys pressed by the user

•  Runs on the OS/400 opera/ng system with Control Language (CL)

Why RPG/400 Migra-on?

•  High cost of opera/ons, upgrades •  High price-‐performance of AS/400 ecosystem •  Lack of flexibility to meet business needs •  Long /me-‐to-‐market for new products-‐ slow to change

•  Poor supportability •  Lack of available resources on AS/400 and RPG/400

Benefits of eCube’s Migra-on Service ARM

•  RPG applica/on is migrated to a web applica/on based on open standards –  J2EE, Struts, Hibernate, etc.

•  Provides an agile placorm that is responsive and aligned to business requirements

•  Tool based migra/on ensures –  Quick turn-‐around –  Considerable ROI and reduc/on of TCO –  Reduced risk due to:

•  Pre-‐transforma/on analysis and remedia/on •  Transforma/on automa/on •  Proven business logic remaining unchanged •  Problema/c business logic remedia/on/improvement •  Post-‐transforma/on analysis and remedia/on

Moderniza-on Road Map

•  General Survey: Enterprise Assessment –  Focused on business/architecture –  Supports planning and strategy

•  In-‐depth Survey: Project/Applica/on-‐Level Assessment –  Technical, supports consolida/on remedia/on and scenario modeling –  Representa/ve code inventory and analysis

•  Confirma/on: Demonstra/ng capabili/es –  Proof-‐of-‐Concept transforma/on –  Design and implement Proof-‐of-‐Concept applica/ons to validate

moderniza/on models and target solu/on capabili/es •  Transforma/on: Full process

–  Based on assessment and client’s business needs –  Targeted incremental transforma/on or phased complete

transforma/on

Moderniza-on Road Map: Enterprise Assessment (Phase I)

•  Interview based •  Cross-‐func/onal •  Engages key stakeholders •  Business view of enterprise architecture •  Maps to business lines and units •  Provides planning and strategy baseline

Moderniza-on Road Map: Assessment and Remedia-on (Phase II)

•  In-‐depth technical analysis •  Addressed technical, data and applica/on architecture

•  Tool and meta-‐model based •  Driven by moderniza/on projects •  Remedia/on may be required at this phase of the process

Moderniza-on Road Map: Moderniza-on and Transforma-on (Phase III)

•  Automated modernizing of data, applica/on, user interface and placorm

•  Remedia/on may be required at the end of the process

•  May be delivered in a targeted fashion with Phase III iterated through several /mes for individual business components (the most cri/cal delivered first)

Enterprise and Project/Applica-on Assessment Goals

•  Uncover and ar/culate business and IT requirements •  Develop holis/c view of exis/ng inventory and enterprise architecture –  Business architecture –  Applica/on architecture

•  Create founda/on and framework for subsequent transforma/on efforts –  Use and test case development

•  Plan Proof-‐of-‐Concept moderniza/on implementa/on and deployment strategy

•  Draf follow-‐on applica/on moderniza/on implementa/on and deployment strategy

Typical Source and Target Matrix

Source Target

RPG Display File JSP pages with Struts

RPG Program Service class, DAO class, Struts controller classes (Ac/on and Ac/onBean)

RPG Database Rela/onal Schema, En/ty classes, Hibernate mapping xml

CL/400 Scripts UNIX/Windows Shell scripts

Transforma-on Overview with ARM Analysis and Remedia-on

Reverse Engineering

Tools REPOSITORY

Forward Engineering

Tools

RDBMS RPG Data Store

RPG/400 Applica/on Components

J2EE Applica/on Components

eCube’s Metalogic Transforma-on Tool Set Analysis and Remedia/on

Analysis and Remedia/on

RPG/400 Migra-on Process

Database DDS Files

Screen DDS Files

RPG Source

CL/400 Source

DB Parser

Screen Scraper

RPG Parser

CL Parser

Reverse Engineering Toolset

Forward Engineering Toolset

Analysis and Repor/ng

Tool

Code Genera/on

Tool

Code Refactoring

Tool

DB Migra/on Tool

RPG/400 Metadata Repository

Analysis Reports

Shell Scripts

JSP with Struts

Java Code

Hibernate Mapping Files

Rela/onal Schema

En/ty Classes

Migrated Applica-on Architecture RDBMS Database Access

Layer

(Hibernate ORM)

Screen Objects

HTML

JSP + Struts

(Browsers)

PC Clients

Struts Controller Converted JAVA Components

Monolithic Legacy Applica/on is par//oned into: •  Presenta/on layer in JSP with Struts •  Data store in Rela/onal Database (Oracle/DB2) •  Core business logic in Open Systems Java •  Data Access Layer in Hibernate ORM

•  The architecture supports popular frameworks like Struts and Hibernate

•  The migrated applica/on runs in a J2EE container

•  Hibernate handles object to rela/onal data mapping (ORM)

Outputs and Customer Interac-on

Inventory Analysis

Data Modeling

Unit Test

Integra/on

Implementa/on & UAT

Source Conversion

•  Inventory Reports

•  Discrepancy Reports

•  CRUD Reports •  Cross-‐reference

reports

•  Rela/onal schema •  Hibernate mapping files •  En/ty classes ____________________________ •  Converted CLs, programs,

screens

•  Job wise/ Screen wise Test reports

•  Execu/on logs •  Issue

resolu/ons

•  Integra/on modules •  Scheduler scripts

•  UAT results •  Issue resolu/ons •  Sign Off

•  Program sources including screens and CL

•  Data defini/ons (DDS) •  Missing objects (if

any)

•  Customer confirma/on

•  Test cases and test data

•  Issue resolu/on support

•  Module defini/on •  Environment provision

•  Implementa/on support

•  UAT

Modernized User Interface

The Modernized User Interface: •  Is browser enabled •  Is an independent

presenta/on layer •  Leverages JSP/Struts •  Is designed to replicate iSeries

terminal screens –  Minimizing training –  Ensures immediate produc/vity

•  Is easily customizable with cascading style sheets (CSS)

RPG Screen DDS

Thank you for viewing this quick overview of the eCube Systems iSeries Moderniza/on Process for RPG/400 to Java Migra/on. If you have any ques/ons, please email ecube-‐[email protected]

iSeries Modernization: RPG/400 to Java Migration

Technology

Transcript of iSeries Modernization: RPG/400 to Java Migration