3rd Annual Plex/2E Worldwide Users Conference Page based on Title Slide from Slide Layout palette. Design is cacorp Title text for Title or Divider pages should be either 40 pt for short titles/28 pt for subtitles or 32 pts for longer titles/24 pt for subtitles. DATE text box is not on master and can be deleted. The date should always be 20 pts. 3D Modernizing a Legacy RPG Banking Application Christer Ahlstedt, IBS Konsult September 20, 2007

2September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Bio Slide >Christer Ahlstedt >IBS Konsult AB/Sales & Marketing Manager >More than 30 years experience in software development and project management. Over the past four years, IBS Konsult has successfully run modernization projects, with the mission to stepwise modernize business critical legacy applications. >I live in Gothenburg, Sweden, my is

Why modernize an old RPG Application? Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles No DATE on divider pages. Page based on Title and Text from Slide Layout palette. Design is 2_Default Design Slide Master ▪ Limited use of primary bullets To reapply Master on Divider pages ONLY, [Format > Slide Design > Apply a design template: > (choose Design 1, 2, or 3) > Apply to Selected Slides]

Applications Hardware Business Processes, Objects, Business Rules Operativ system databases Years Source: Compuware Lifecycle of strategic applications Focus on Business Processes & Business Rules Modernized appl.

5September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Goals for the Modernization projects  Protect the IT investments you already have done  Reuse as much as possible. Pick the “low hanging fruits” first. These changes will pay off immediately. Saves time and money.  Make it possible to implement new features faster and cheaper in the future (time to market).  Make future maintenance faster and cheaper (reduction with up to 50%)  Improve possibility to stay current with new technology, and reduce platform dependency  Introduce new concepts (SOA, Webservices)

Modernizing a Legacy RPG Banking Application Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles No DATE on divider pages. Page based on Title and Text from Slide Layout palette. Design is 2_Default Design Slide Master ▪ Limited use of primary bullets To reapply Master on Divider pages ONLY, [Format > Slide Design > Apply a design template: > (choose Design 1, 2, or 3) > Apply to Selected Slides]

7September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA RESULTS >Modern flexible application where new offerings are put together by “end users”, no coding involved >Time consuming monthly batch runs replaced by smaller runs overnight or ad hoc >New datamodel implemented >New development projects run in parallel with the Modernization project >Modern (GUI) clients The Bank CHALLENGE >Need to respond to market demands faster – new offerings >Application not flexible - Business rules hard coded >Large volumes of transactions >Dependency of Key persons SOLUTION >Stepwise modernization >New functionality and DB implemented each month) >Reuse of existing RPG-modules Page based on Title Only from Slide Layout palette. Design is cacorp 2006.

8September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA This presentation covers >The IBS ”modernization approach”  How to modernize an application ”in production” = real life  A Modernizing project in stead of replacing the legacy application with a new standard application  Development cycle: Iterative process, small steps (4-8 weeks), no big bang implementation  How to modernize the foundation of the application (change database layouts and relations)  Tools used

9September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Modernization Background >Mission critical applications, represents a big value for the customer >”Mature”, at least years old. Some pgms are from the 1980’s >Hard to replace the appl. with new standard appl. >Limited integration with other applications >Difficulty to adapt new solutions eg. web solutions. Application

10September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Modernization Background  Programs  The programs are big and monolithical  The database is not normalised or does not fully support business processes any longer  Documentation does not exist or is not up-to-date  Experienced (key) developers have to maintain some of the big programs  Platform dependency (System i )

The Challenge is to redesign and replace the super- tanker with a fleet of small special units, cooperating to deliver the cargo on time with no delays. The Challenge

One module for each business function

Feasibility Study Informations- beskrivning Funktions- beskrivning Aktivitets- beskrivning Process beskrivning Processkarta Start of an IBS Modernization project Process Map Processes Datamodel Activities Functions

We analyse, document.. >Business processes and datamodel >Any known requirements Business has on IT

.. analyse risks, set goals, and plan the first steps of the project >Together with the customer we set the ”goals” and plan the first steps of the modernization project. >Choose activities that will save time and money for the customer

Phase 1 Result: Analysis Phase Business processes Feasibility Study Documentation,Goals, Standards etc. Existing Datamodel

Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Iterative development - deployment 4-8 weeks

18September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Modernization project - planning Modernization project

19September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Modernization project and ongoing development New development project Modernization project

The IBS Modernization approach…………… You need a firm foundation ”The Bottom up approach” Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles No DATE on divider pages. Page based on Title and Text from Slide Layout palette. Design is 2_Default Design Slide Master ▪ Limited use of primary bullets To reapply Master on Divider pages ONLY, [Format > Slide Design > Apply a design template: > (choose Design 1, 2, or 3) > Apply to Selected Slides]

21September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA When rebuilding a house ….

22September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA..you need a model, and architechture...

23September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA..and a solid foundation for your new building

24September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Can you live with your foundation for another 10 years?

25September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Renovate Applications ….? >You need a proper datamodel, normalised and implemented as a Database. >On top of this solid foundation, you can modernize existing functions and also build new parts of the application. >This will prolonge the life of the application with many years

If necessary create a “to be” Data Model

27September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Stepwise implement the new datamodel 5250 Browser Data Logic Data Logic Modernization project Server pgm’s

The Modernization project Tools used Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles No DATE on divider pages. Page based on Title and Text from Slide Layout palette. Design is 2_Default Design Slide Master ▪ Limited use of primary bullets To reapply Master on Divider pages ONLY, [Format > Slide Design > Apply a design template: > (choose Design 1, 2, or 3) > Apply to Selected Slides]

29September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA The Development Lifecycle Business Modeling Analysis Design ConstructionTestDeployProduction Change Requests People Process Tools The Modernization project: Iterative steps weeks

30September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Development Tools >Rigth tools for the job >Project Planning >Modelling  Process  Data >Development  Generate code?  Handle versions of pgms. >Conversion of Data >Document Reqs and handle changes >Documentation >Testing >Deployment (production)

31September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA From analysis to deployment

32September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA CA ERwin DM Logical Generic Physical Physical CA ERwin and CA Plex CA Plex Plex Application Model Plex Data Model* DB2 CA Plex Function/Source

33September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA CA Plex Pre-build Class Libraries My Class Libraries Generators NT Back office.NETEJB iSeries C/S iSeries NPT JAVA Business rules CA Plex Repository Basic objects 123 BLOB’s Business objects Win/NT Oracle HTML XML

34September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA IBM Websphere Development Studio client (WDSc)

The Modernization project How to do it Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles No DATE on divider pages. Page based on Title and Text from Slide Layout palette. Design is 2_Default Design Slide Master ▪ Limited use of primary bullets To reapply Master on Divider pages ONLY, [Format > Slide Design > Apply a design template: > (choose Design 1, 2, or 3) > Apply to Selected Slides]

36September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA How to modernize the super tanker?  Programs  The programs are big and monolithical  Business logic is embedded in the programs  The database is not normalised

37September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Modernization – What?  Database  Redesign/DDS/SQL  Modularisation of programs  business functions, services  Complex batch programs (split into modules)  Presentation layer (UI)  5250  GUI Clients (Windows/Java)  Web browser clients (HTML, JSP)  Modernise the code: RPG II/III to RPG IV ILE/Java  Integration – web services, XML

Program code For Screen processing All Business Logic Database processing Going from monolithic (5250) programs to

Program code Code for Client processing 5250 Three-layer solution - Modularization of business logic, external Database Objects (pgms) and multiple clients Module n Program code Code for Business processes Module 2 Module 1 Card Program code Code for Database processing CustomerAccount Adress Database Objects Win/Java Webb 5250 Browser Web services

Database Objects >Database object (DBO)  Data attributes  IO - functions –Single fetch of data –Block fetch of data –Read in other sequence –Write DBO –Change DBO –Delete DBO  Stored procedures –eg. for database integrity >Advantage  One function for each IO – process  One place to change  Fast and easy  Less and more simple code in calling program Program code Contain code for eg. Read Customer by Adress Database Objects Customer Data View Read Cust Write Cust Change Cust Delete Cust Fetch Adress

Program code For Screen processing All Business Logic Database processing Reuse existing RPG programs? Replace

42September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Modify RPG pgms to process data via external server pgms Program code For Screen processing All Business Logic CustomerAccount Address Database Objects Create external pgms to process OLD layouts Database Call Database ”Wrapper” Pgm

43September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Add new database layout to wrapper pgm Bank Prod Call Database ”Wrapper” Pgm CustomerAccount Adress Database Objects Program code For All Business Logic CustomerAccount Address Database Objects OLD NEW layouts Add

Which record layout to process? processing controlled via Wrapper Status flag inside wrapper O = old, N= new, B=both Bank Prod Call Database ”Wrapper” Pgm CustomerAccount Adress Database Objects Program code for Screen processing All Business Logic CustomerAccount Address Database Objects OLD NEW layouts Wrapper program executes database processing controlled via value of wrapper status flag

45September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Automating the development of wrapper functions? >We have developed programs, scanning through the RPG source code and implementing the ”wrapper” calls automatically,  commenting out the database processing statements  adding the calls to the database wrapper programs >We generate new ”wrapper server functions” automatically.

46September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Conversion of Production Data from old layout into new DB layouts >Delegate responsibility for conversion of data to a team member >Time consuming job, do not underestimate this task >Conversion of data may have to be run several times to keep data in synch.  To create testdata  To create a proper starting point for ”parallel runs”

47September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Testing is extremely important >Test Manager >We are deploying into production environment new functionality and database changes almost every month >The Test Manager is responsible for: >Systems testing >Integration testing >Reference testing >Parallel runs (OLD - New DB layouts)

48September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Capacity to run in parallel? >Hardware to run old and new application in parallel  Servers  Storage (DB)  Memory >Time to run over night or monthly jobs >End Users may have to work with two appl.

49September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Development -> Deployment Development Env. Source, Object Production systems Source, Object

50September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Deployment - Installing new software into production environment >Project Manager >The Project Manager can delegate all/part of the duties to a team member: >One person responsible for deployments (install new functionality and database changes into production env) >Responsible for setting the ”Wrapper Status Flags” >Control & synch. Data >Keep statistics of elapsed time of production runs.

51September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA RESULTS >Modern flexible application where new offerings are put together by “end users”, no coding involved >Time consuming monthly batch runs replaced by smaller runs overnight or ad hoc >New datamodel implemented >New development projects run in parallel with the Modernization project >Modern (GUI) clients The Bank CHALLENGE >Need to respond to market demands faster – new offerings >Application not flexible - Business rules hard coded >Large volumes of transactions >Dependency of Key persons SOLUTION >Stepwise modernization >New functionality and DB implemented each month) >Reuse of existing RPG-modules Page based on Title Only from Slide Layout palette. Design is cacorp 2006.

52September 20, 2007 [Modernizing a Legacy RPG Banking Application] Copyright © 2007 CA Summary of the Modernization project  Protection of the IT investments they already had done  Reuse of existing business logic. Stepwise implementation. Pick the “low hanging fruits” first. Saved time and money.  Made it possible to implement new features faster and cheaper (time to market).  Made future maintenance faster and cheaper  Improved possibility to stay current with new technology, and we have reduced platform dependency

Questions? Title text for Title or Divider pages should be either 40 pt for short titles /28 pt for subtitles or 32 pts for longer titles /24 pt for subtitles No DATE on divider pages. Page based on Title and Text from Slide Layout palette. Design is 2_Default Design Slide Master ▪ Limited use of primary bullets To reapply Master on Divider pages ONLY, [Format > Slide Design > Apply a design template: > (choose Design 1, 2, or 3) > Apply to Selected Slides]