EGL Conference 2011 - Application Migration

4,338 views

Published on

Modernization via automated application migration (featuring customer success stories). See www.eglcon.org for more information.

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,338
On SlideShare
0
From Embeds
0
Number of Embeds
648
Actions
Shares
0
Downloads
141
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • This is an real example of a Software AG cost structure that should be articulated b/c if these Natural customers are not experiencing these types of cost increases this is an opportunity to make them aware that it is highly likely in the future.
  • >> Tell a story about the failed rewrite Legacy application under active development One year later… Unable to keep up with changes to ongoing development A lot of money and resources spent with little to show for Rewrite hugely under-estimated Project doomed to failure! Recovery challenge A good portion of the budget is gone Solution Modernization via automation Repeated rule-based transformation The only option during active development maintenance
  • Enhanced transformations and Refactoring uncovered Navigation and menuing system Some items were pushed to be done after conversion Scope of the project identified Understand the impact based on requirement Generates data for project planning Printing uses ActiveX
  • 2 digit year to be transformed into a 2 digit Heisei date.
  • Unicode: UTF-16 2-bit
  • Requirements & Design document management Defect Tracking SCM and Release Management Support the migration workflow
  • EGL Conference 2011 - Application Migration

    1. 1. Application Modernization via Migration Todd Britton, IBM Rational Elvin Hoyer, Xact Karlheinz Peter, PKS Danny Backx, KBC Eric Simone, ClearBlade
    2. 2. Agenda Topic Type Minutes Speaker Application Transformation via Migration Overview 15 Todd Britton Ideal/Datacom migration to EGL/DB2 (and EGL RUI) Case Study 20 Elvin Hoyer & Slavik Zorin Modernization of COBOL and RPG Case Study 20 Karlheinz Peter Cool:Gen migration to EGL Case Study 20 Danny Backx VG Text UI migration to EGL Rich UI Case Study 20 Eric Simone
    3. 3. Application Transformation Overview
    4. 4. Legacy Application Concerns <ul><li>Applications not aligned with strategic corporate directions </li></ul><ul><li>Application technologies are unsupported OR don’t allow applications to evolve </li></ul><ul><li>High license fees from proprietary language / database vendors not in synch with value </li></ul>Inhibits strategic investments Business Rule Discovery and Management ILOG Web 2.0 and Mobile License Fees Value Applications CICS IMS WAS DB2 Applications ApplicationS IBM i Mainframe Distributed
    5. 5. Application Modernization Options Automated Migration Packaged application Re-Write Elapsed Time & Risk Functionality & Stability 50% 75% 100% 25%
    6. 6. Rational’s Application Transformation Solutions Migrate from older languages and expensive tools to modern development platforms, languages, databases and tools Operating costs were reduced 55 percent by migrating from the VAGen legacy application to Java. “The migration to EGL combines the best of both worlds: The stability of IBM System z and the flexibility of Java.” Massive cost savings are also included! — Frank Landewee, project manager, Atos Origin GmbH, Essen SAG Natural/Adabas CA Ideal/Datacom CA Cool:Gen RPG COBOL Green screen text UI’s (3270 or 5250) VA Generator GUI’s <ul><li>Rational Migration Extension for Rich UI </li></ul><ul><li>Rational Migration Extension for IBM i </li></ul><ul><li>Rational Migration Extension for Natural </li></ul><ul><li>Rational Migration Extension for CA </li></ul>Conversion Tooling EGL Testing, Remediation, Deployment System z – CICS System z – Linux 1 System z – Batch System z – WAS 2 System z – VSE IBM i - WAS IBM i - Native AIX HP - UX Solaris Linux Windows 1 Eligible to run on IFL 2 Eligible to run on zIIP and zAAP WEB 2.0
    7. 7. Technical Value of Migration <ul><li>Leverages proven applications </li></ul><ul><ul><li>Includes years of business and application evolution </li></ul></ul><ul><ul><li>No need to reconstitute lost application knowledge </li></ul></ul><ul><ul><li>Matches existing business processes </li></ul></ul><ul><li>High level of maintainability </li></ul><ul><ul><li>Mapping to EGL is highly optimal for this </li></ul></ul><ul><li>Platform and runtime flexibility </li></ul><ul><ul><li>Leverage specialty processors on System z </li></ul></ul><ul><ul><li>Target strategic platforms without change </li></ul></ul><ul><li>Old UI’s can be migrated to Web 2.0 </li></ul><ul><ul><li>100% automation for standard migration </li></ul></ul><ul><ul><li>No refactoring required </li></ul></ul><ul><li>+ New business initiatives </li></ul><ul><li>+ User requirements </li></ul><ul><li>+ Bug fixes </li></ul><ul><li>+ Regulatory changes </li></ul><ul><li>+ Mergers, acquisition </li></ul><ul><li>+ Response to competition </li></ul><ul><li>+ More Bug Fixes </li></ul><ul><li>Original Application </li></ul><ul><li>= World class stability and alignment with business needs </li></ul>
    8. 8. Business Value of Migration <ul><li>Position proven applications to react to business needs for next decade </li></ul><ul><li>Increase I/T flexibility </li></ul><ul><li>Eliminate high license and maintenance fees </li></ul><ul><li>Low risk </li></ul><ul><ul><li>Main effort is testing, not creating </li></ul></ul><ul><ul><li>No “scope creep” in base migration </li></ul></ul><ul><li>Low cost </li></ul><ul><ul><li>5 to 10 times cheaper than rewriting </li></ul></ul><ul><ul><li>Customization of packaged apps is costly </li></ul></ul><ul><li>Quick ROI </li></ul><ul><ul><li>Highly automated – 95% to 100% </li></ul></ul><ul><ul><li>Most projects < 18 months </li></ul></ul>U.S. Energy Company (recently started migration project to EGL) Shipping company in US projected ROI after migration from Natural/ADABAS of $5M after 3 years and $14M after 5 years SI in Europe chose migration to EGL and deployment to specialty processors and realized 55% decrease in MIPS costs (annual savings of over $1.5M Real estate company in AP chose migration to EGL and EGL RUI after a $50M rewrite project failed Total I/T costs I/T Expenses Business As Usual (2011 - 2015) $ 27,075,000 With migration to EGL & upgrade of mainframe (2011 - 2015) $ 22,236,821 Savings over 5 years $ 4,838,179 Savings as a percentage of Business As Usual costs 18%
    9. 9. Recent Migration Projects Started <ul><li>Credit Insurance company in South Africa </li></ul><ul><ul><li>4M LOC Natural/ADABAS </li></ul></ul><ul><ul><li>Cost pressure from SAG forced the move using RMEn and RMErui from Natural/ADABAS to EGL/DB2 </li></ul></ul><ul><ul><li>Started in January, expect to conclude project in 1Q 2012 </li></ul></ul><ul><ul><li>Customer testing first deliverable now </li></ul></ul><ul><li>Energy Utility company in U.S. </li></ul><ul><ul><li>Migration using RMEn & RMErui from Natural/ADABAS to EGL/DB2 driving savings (18% of I/T costs over next 5 years) </li></ul></ul><ul><ul><li>Project starting in April </li></ul></ul><ul><ul><li>Duration of 12 months </li></ul></ul><ul><li>Copyright Management company in Europe </li></ul><ul><ul><li>Sophisticated Client/Server GUI screens being migrated to EGL Rich UI by RMErui </li></ul></ul><ul><ul><li>Driven by need to drive new business opportunities and to be in a supported environment </li></ul></ul><ul><ul><li>Web deployment will save costs and simplify operations </li></ul></ul><ul><ul><li>Project starting in April </li></ul></ul><ul><li>Pension Fund company in Europe </li></ul><ul><ul><li>Client/Server VA Generator GUI being migrated to EGL Rich UI by RMErui </li></ul></ul><ul><ul><li>Project starting in April </li></ul></ul>
    10. 10. Agenda Topic Type Minutes Speaker Application Transformation via Migration Overview 15 Todd Britton Ideal/Datacom migration to EGL/DB2 (and EGL RUI) Case Study 20 Elvin Hoyer & Slavik Zorin Modernization of COBOL and RPG Case Study 20 Karlheinz Peter Cool:Gen migration to EGL Case Study 20 Danny Backx VG Text UI migration to EGL Rich UI Case Study 20 Eric Simone
    11. 11. Case Study: Ideal/Datacom migration to EGL/DB2 (& EGL RUI)
    12. 12. Modernization of Real Estate Application <ul><li>Source Platform </li></ul><ul><ul><li>Language – CA-Ideal and COBOL </li></ul></ul><ul><ul><li>Database – CA-Datacom </li></ul></ul><ul><ul><li>UI – 3270 Panels </li></ul></ul><ul><ul><li>Runtime – z/OS </li></ul></ul><ul><li>Application Stats </li></ul><ul><ul><li>CA-Idea Programs count – 6400+ </li></ul></ul><ul><ul><li>CA-Idea Panels count – 4500+ </li></ul></ul><ul><ul><li>CA-Idea Dataviews count – 800+ </li></ul></ul><ul><ul><li>CA-Idea Reports – 100+ </li></ul></ul><ul><ul><li>COBOL Programs – 150+ </li></ul></ul><ul><li>Platform Transformation </li></ul><ul><ul><li>CA-Ideal to EGL </li></ul></ul><ul><ul><li>COBOL to EGL </li></ul></ul><ul><ul><li>CA-Datacom to DB/2 </li></ul></ul><ul><ul><li>3270 to Rich UI / Web 2.0 </li></ul></ul><ul><li>Target Architecture </li></ul><ul><ul><li>Runtime – z/OS and AIX </li></ul></ul><ul><ul><li>Single tier to 3-tier architecture </li></ul></ul><ul><li>Additional Requirements </li></ul><ul><ul><li>Code page conversion </li></ul></ul><ul><ul><li>Emperor era to Gregorian date </li></ul></ul><ul><ul><li>Conversion Flat files to RDMS </li></ul></ul><ul><ul><li>Enhanced Web 2.0 Widgets </li></ul></ul>
    13. 13. Global Project – Teams in 3 Continents <ul><li>Xact – RMEca (Europe) </li></ul><ul><ul><li>Ideal to EGL </li></ul></ul><ul><ul><li>COBOL to EGL </li></ul></ul><ul><ul><li>Datacom to DB2 </li></ul></ul><ul><li>Synchrony – RMErui (North America) </li></ul><ul><ul><li>EGL TUI Programs to UI Programs </li></ul></ul><ul><ul><li>EGL TUI Forms to EGL Rich UI </li></ul></ul><ul><li>Global SI (Asia) </li></ul><ul><ul><li>Project Management </li></ul></ul><ul><ul><li>Custom Development </li></ul></ul><ul><ul><li>Integration and Testing </li></ul></ul>
    14. 14. Modernization Methodology Employed <ul><li>Modernization Analysis </li></ul><ul><li>Automated, ruled-based transformation from Ideal to EGL </li></ul><ul><ul><li>Programs </li></ul></ul><ul><ul><li>Data </li></ul></ul><ul><ul><li>User Interface </li></ul></ul><ul><li>Conversion Support Libraries </li></ul><ul><li>Interface to custom development </li></ul><ul><ul><li>Application initialization </li></ul></ul><ul><ul><li>Session management & security </li></ul></ul><ul><ul><li>Reporting & Printing subsystem </li></ul></ul><ul><li>Re-migration of latest versions of the application </li></ul>
    15. 15. Language Transformation <ul><li>Ideal program  EGL program </li></ul><ul><li>Ideal procedure  EGL function </li></ul><ul><li>Ideal dataview  EGL SQL record </li></ul><ul><li>Ideal Working area  EGL Basic record </li></ul><ul><li>Ideal Parameter area  EGL Basic record </li></ul><ul><li>Ideal Panel  EGL Form </li></ul><ul><li>Ideal builtin functions  Equivalant EGL Library Functions or Xact build reusable EGL functions </li></ul>
    16. 16. Language Transformation Challenges <ul><li>Emperor era to Gregorian Date </li></ul>Example: change 2 digit year into 2 digit Heisei date IF WW-YY > 88 SUBTRACT 88 FROM WW-YY ELSE ADD 12 TO WW-YY ENDIF
    17. 17. <ul><li>Unicode </li></ul><ul><ul><li>Substructures </li></ul></ul><ul><ul><li>Substring </li></ul></ul>1 A X 30 2 B X 11 2 C N Z 4 2 D X 15 Language Transformation Challenges 10 A Unicode (30); 20 B Unicode (11); 20 C Num (4); 20 Fill Char (4); 20 D Unicode (15); EBCDIC CP-932 EGL Unicode A B C D A SO SI B C D あ x1 x2 x3 x4 x5 x6 x7 x8 x1 x2 x3 x4 x5 x6 x7 x8 x9 x10 A B C D あ x1 x2 x3 x4 x5 x6 あ SUBSTR(&quot;A あ BCD“), Start=1, length=5 A あ BCD A あ BC A あ Result
    18. 18. Data Transformation <ul><li>Dataview </li></ul><ul><ul><li>Define Primary Key </li></ul></ul><ul><ul><li>Redefines </li></ul></ul><ul><ul><ul><li>Additional tables </li></ul></ul></ul><ul><ul><ul><li>Include all redefinitions in the table </li></ul></ul></ul><ul><ul><li>Occurs </li></ul></ul><ul><ul><ul><li>Additional tables </li></ul></ul></ul><ul><ul><ul><li>Primary key + Index </li></ul></ul></ul><ul><ul><li>Types </li></ul></ul><ul><ul><ul><li>Examine data to determine types </li></ul></ul></ul><ul><ul><ul><li>Validate content of all data – including code-page </li></ul></ul></ul>Data validation run by Customer at Customer site using Xact tool
    19. 19. Modernization Strategy – Retain Program Logic Integrity EGL RUI Application Ideal 3270 Program Ideal Panel converse EGL/RUI response UI Record request transmit EGL UIProgram UI Record Host Tier Client Tier EGL Program Interface EGL/RUI Interface RUI Gateway JEE Middle Tier C O N V E R S I O N
    20. 20. Before and After – Sample Widget Transformation
    21. 21. Before and After – Complex Layout & Widgets
    22. 22. Integration <ul><li>Automated testing support with Rational Function Tester </li></ul><ul><ul><li>Script generation </li></ul></ul><ul><ul><li>Widget tagging </li></ul></ul><ul><ul><li>Navigation meta-data </li></ul></ul><ul><li>TAM (Tivoli Access Manager) integration </li></ul><ul><ul><li>Authentication </li></ul></ul><ul><ul><li>Authorization </li></ul></ul><ul><ul><li>Timeout </li></ul></ul><ul><li>3 rd -party reporting and printing subsystem </li></ul>
    23. 23. RTC Integration – Multiple Teams in Multiple Continents Project Integration Stream Conversion T Stream Custom Dev T Stream Test T Stream Conversion Team Stream Manager Custom Dev Team Stream Manager Test Team Stream Manager Test Team member Custom Dev Team member Conversion Team member Communicate about the delivering conditions
    24. 24. Agenda Topic Type Minutes Speaker Application Transformation via Migration Overview 15 Todd Britton Ideal/Datacom migration to EGL/DB2 (and EGL RUI) Case Study 20 Elvin Hoyer & Slavik Zorin Modernization of COBOL and RPG Case Study 20 Karlheinz Peter Cool:Gen migration to EGL Case Study 20 Danny Backx VG Text UI migration to EGL Rich UI Case Study 20 Eric Simone
    25. 25. Case Study: Modernization of COBOL and RPG
    26. 26. System z Cobol Modernization – ATOS Retail Application <ul><li>Situation </li></ul><ul><ul><li>Retail Application </li></ul></ul><ul><ul><li>System z with IMS, DB2, IMS, DB, VSAM </li></ul></ul><ul><ul><li>Languages Cobol + VAGEN </li></ul></ul><ul><ul><li>Batch + Online (3000 users) </li></ul></ul><ul><li>Requirements </li></ul><ul><ul><li>Reduce Operating expenses by more than 30% </li></ul></ul><ul><ul><li>Modern Web UI and development environment </li></ul></ul><ul><ul><li>Low risk and ROI < 12 months </li></ul></ul>
    27. 27. System z Cobol Modernization – ATOS Retail Application <ul><li>Evaluation </li></ul><ul><ul><li>Stay on the mainframe or downsizing? </li></ul></ul><ul><ul><li>What’s the right language – Cobol, Java or EGL? </li></ul></ul><ul><ul><li>Compare different solutions with pilots! </li></ul></ul><ul><li>Solution </li></ul><ul><ul><li>Decision for EGL + Application Transformation </li></ul></ul><ul><ul><li>Stay on mainframe but move workload to cheaper Specialty Engines </li></ul></ul><ul><ul><li>Highly maintainable “Business Java” Code in EGL </li></ul></ul><ul><ul><li>Automated Transformation Engines for Cobol and VAGEN available </li></ul></ul><ul><ul><li>Very smooth step by step migration </li></ul></ul><ul><ul><li>8 months project including preparations + staff training </li></ul></ul>
    28. 28. System z Cobol Modernization – ATOS Retail Application <ul><li>Result </li></ul><ul><ul><li>Application stays on System z </li></ul></ul><ul><ul><li>Application runs with Java and Websphere </li></ul></ul><ul><ul><li>99% of the code migrated automatically </li></ul></ul><ul><ul><li>Savings 55% - ROI 11 months </li></ul></ul>zAAP NALC CPU usage GP zIIP 46% 31% 16% 7% Cost comparison 100% 47% before after
    29. 29. System i RPG Modernization – Tigges GmbH ERP <ul><li>Situation </li></ul><ul><ul><li>ERP Application </li></ul></ul><ul><ul><li>System i with ILE RPG + 5250 Screens </li></ul></ul><ul><ul><li>In house development </li></ul></ul><ul><ul><li>2 mio. Loc. RPG + 450 screens </li></ul></ul><ul><li>Requirements </li></ul><ul><ul><li>Modern business process oriented development </li></ul></ul><ul><ul><li>Modern and fast GUI based User Interface </li></ul></ul><ul><ul><li>Reuse existing application logic </li></ul></ul><ul><ul><li>Preserve System I </li></ul></ul><ul><ul><li>Small transformation steps that can be handled by the RPG team </li></ul></ul>
    30. 30. <ul><li>Evaluation </li></ul><ul><ul><li>Buy a packaged application? </li></ul></ul><ul><ul><li>Use Screen Scraping? </li></ul></ul><ul><ul><li>Use EGL and do a step by step transformation? </li></ul></ul><ul><li>Solution </li></ul><ul><ul><li>Create a GUI for the RPG programs with PKS WebAPI </li></ul></ul><ul><ul><li>Educate RPG developers in EGL and write new functionality in EGL in a Business Process friendly architecture (SOA) </li></ul></ul><ul><ul><li>Integrate the new EGL functionality with the RPG application via WebAPI </li></ul></ul><ul><ul><li>Migrate RPG programs step by step into EGL and integrate them into the future Business Processes </li></ul></ul>System i RPG Modernization – Tigges GmbH ERP
    31. 31. <ul><li>Result </li></ul><ul><ul><li>Modern business process oriented development with existing RPG team </li></ul></ul><ul><ul><li>Modern and fast GUI based User Interface with nice enhancements </li></ul></ul><ul><ul><li>Step by Step reuse of existing application logic for future Business Processes now possible </li></ul></ul><ul><ul><li>Preserve System I and make it much more attractive </li></ul></ul>System i RPG Modernization – Tigges GmbH ERP
    32. 32. Agenda Topic Type Minutes Speaker Application Transformation via Migration Overview 15 Todd Britton Ideal/Datacom migration to EGL/DB2 (and EGL RUI) Case Study 20 Elvin Hoyer & Slavik Zorin Modernization of COBOL and RPG Case Study 20 Karlheinz Peter Cool:Gen migration to EGL Case Study 20 Danny Backx VG Text UI migration to EGL Rich UI Case Study 20 Eric Simone
    33. 33. Case Study: Cool:Gen migration to EGL
    34. 34. <ul><li>KBC is an integrated bancassurance group, catering mainly for retail customers, small and medium-sized enterprises and private banking clientele. </li></ul><ul><li>It occupies leading positions on its home markets of Belgium and Central and Eastern Europe, where it specialises in retail bancassurance and asset management activities. </li></ul><ul><li>Elsewhere around the globe, the group has established a presence in selected countries and regions. </li></ul> * 
    35. 35. Agenda <ul><li>Intro </li></ul><ul><ul><li>KBC & Osiris history, numbers (how big is Osiris) </li></ul></ul><ul><ul><li>Why do we do this, why do we do it this way </li></ul></ul><ul><li>Iterative approach, macro planning, other projects </li></ul><ul><li>Differences </li></ul><ul><ul><li>COOL:Gen vs EGL, Cobol vs Java, DB2 vs Oracle </li></ul></ul><ul><ul><li>Maintainability/readability, performance </li></ul></ul><ul><li>What I won’t tell you … </li></ul><ul><ul><li>How we use EGL on 3 platforms to reduce tools and complexity, and increase reuse </li></ul></ul><ul><ul><ul><li>see Johan Geybels’s talk at the Zurich 2008 conference … </li></ul></ul></ul><ul><ul><li>VA/G to EGL migration of 250 developers, 18000 objects, </li></ul></ul><ul><ul><ul><li>6 waves over 1½ years, 3 platforms </li></ul></ul></ul>   * 
    36. 36. What are we doing & why <ul><li>… bought Osiris source code ~1995 </li></ul><ul><ul><li>At the time, the company had selected IEF / Composer / COOL:Gen as strategic development environment </li></ul></ul><ul><ul><li>Merger between banks & insurance company in 1998 became KBC </li></ul></ul><ul><ul><li>Osiris ended up as the only COOL:Gen application left, and the only major application on an aging platform. Version of COOL:Gen frozen (2002). </li></ul></ul><ul><li>KBC evolves from a mostly Belgian company to one with significant presence in 5 Central European countries </li></ul><ul><li>In 2006 .. 2008, an effort to redesign the securities domain was started but abandoned. Decision to go for evolution rather than .. </li></ul><ul><li>Beginning of 2009 : selection of partner for automatic conversion, and start of a programme to develop a mainframe-like platform for use in the new Data Center </li></ul><ul><li>TC Osiris reoriented : deliver on new platform instead of mainframe, to enforce maturity in the new platform … </li></ul> * 
    37. 37. … & how <ul><li>Osiris sources contain full 3270-based user interface </li></ul><ul><ul><li>Before cleanup, ~1500 online screens </li></ul></ul><ul><ul><li>Decision not to rewrite this to create a 3-tier web based application </li></ul></ul><ul><li>Stick to EGL “Text UI” model </li></ul><ul><ul><li>Is what we had intended to use on MVS/IMS/DB2 </li></ul></ul><ul><ul><li>Is also what we can use on HP-UX/Oracle if we replace the current PCOMM 3270 emulator by a VT220 emulator </li></ul></ul><ul><li>For Xact, the platform change is almost transparent </li></ul><ul><ul><li>Don’t generate IMS sources (e.g. PSBs) </li></ul></ul><ul><ul><li>Take some limits into account (EGL generates code that hits 64K Java limits) </li></ul></ul><ul><ul><li>DB2 vs. Oracle statement syntax </li></ul></ul><ul><li>Numbers : ~1000 onlines, 300 batches  3500 sources </li></ul> * 
    38. 38. What is Osiris ?  *  <ul><li>3270 application, internal use </li></ul><ul><li>Links with other applications via exchange of files and asynchronous messages </li></ul>
    39. 39. Migration approach - cooperation <ul><li>Xact already had “starter pack” (migration engine from COOL:Gen to EGL) based on previous work. Additional effort needed to </li></ul><ul><ul><li>Correctly translate the COOL:Gen statements used by KBC </li></ul></ul><ul><ul><li>Produce EGL that complies sufficiently to KBC standards </li></ul></ul><ul><ul><li>Reach maturity (performance, readability, ..) </li></ul></ul><ul><li>Iterative approach : 4 .. 8 week cycles </li></ul><ul><ul><li>Receive converted code, implement & test, send back defect descriptions </li></ul></ul><ul><ul><li>Work by Xact on conversion engine steered by KBC priorities  SCRUM </li></ul></ul><ul><li>Conversion based on extractions </li></ul><ul><ul><li>Extraction based on queries on COOL:Gen, and CE Access output </li></ul></ul><ul><ul><li>Time consuming and error prone : only do a small number of extractions … driven by necessity (source changes by other projects) </li></ul></ul><ul><li>Weekly conference calls with Xact keep us on track towards a win-win </li></ul> * 
    40. 40. Migration approach - phasing <ul><li>Start with a well chosen small percentage of Osiris source, use this for a long time </li></ul><ul><ul><li>Only increase % of converted code after a while </li></ul></ul><ul><li>Divide the timeline in chunks : choose which battle to fight when </li></ul><ul><ul><li>Keep source code for Xact frozen initially </li></ul></ul><ul><ul><ul><li>Focus on converting code right, and getting more of the source code converted </li></ul></ul></ul><ul><ul><li>Then start following Osiris source code changes </li></ul></ul><ul><ul><ul><li>Allow testing </li></ul></ul></ul><ul><ul><ul><li>Avoid confusing testers (functionality shouldn’t differ much from production) </li></ul></ul></ul><ul><ul><ul><li>Make sure we can convert the new code </li></ul></ul></ul><ul><ul><ul><li>Professionalize everything </li></ul></ul></ul> * 
    41. 41. Migration approach – debugging & testing <ul><li>To me, these are two different activities </li></ul><ul><ul><li>Overcoming all technical hurdles (see next slides) </li></ul></ul><ul><ul><li>This project changes *everything* so must address all this in debugging </li></ul></ul><ul><ul><li>Similar projects in other companies may be less ambitious </li></ul></ul><ul><li>Overcoming technical issues  ICT testing (= debugging) </li></ul><ul><ul><li>Currently a sizeable team to be ready for batch issues, hope to cut down quickly </li></ul></ul><ul><ul><li>Not possible to do detailed ICT test of every batch program </li></ul></ul><ul><li>Functional testing : by our business </li></ul><ul><ul><li>Not entirely dependent of the amount of technical change </li></ul></ul><ul><ul><li>Significant test preparation effort was done to get ready for several projects in this period </li></ul></ul>
    42. 42. Timing  *  5/2012 : production migration 1/2012 : acceptance migration 10/2011 : Other project #2 with impact on Osiris sources 1Q2011 : Test Osiris on “stable test” platform 5/2011 : Other project #1 with impact on Osiris sources 2 0 1 0 2 0 1 1 2 0 1 2
    43. 43. Core : migrate COOL:Gen to EGL  *  Xact automated source to source Conversion (RMEca) Rewrite batch scripts in perl Rewrite non-COOL:Gen in EGL no queries on operational database handle dependencies but avoid redesign provide testable code very early Referential Integrity in Oracle instead of COOL:Gen What’s a Unix anyway ? Periodically get a new surprise challenge
    44. 44. Agenda Topic Type Minutes Speaker Application Transformation via Migration Overview 15 Todd Britton Ideal/Datacom migration to EGL/DB2 (and EGL RUI) Case Study 20 Elvin Hoyer & Slavik Zorin Modernization of COBOL and RPG Case Study 20 Karlheinz Peter Cool:Gen migration to EGL Case Study 20 Danny Backx VG Text UI migration to EGL Rich UI Case Study 20 Eric Simone
    45. 45. Case Study: VisualAge Generator Text UI migration to EGL RUI
    46. 46. Visiting Nurse Service of New York: Phase 1 <ul><li>4 VAGen 3270 systems converted to EGL Text UI </li></ul><ul><ul><li>Physician Referral </li></ul></ul><ul><ul><li>Order Processing </li></ul></ul><ul><ul><li>Service Charge Processing </li></ul></ul><ul><ul><li>Plan of Care </li></ul></ul><ul><li>264 large VAGen programs </li></ul><ul><li>DB2 & VSAM data access </li></ul><ul><li>COBOL & Assembler interaction </li></ul><ul><li>3.56M lines of code </li></ul><ul><li>1,658 Screens </li></ul><ul><li>3 calendar months total effort </li></ul><ul><ul><li>Analysis & Planning </li></ul></ul><ul><ul><li>Code Conversion </li></ul></ul><ul><ul><li>Development & Runtime Setup </li></ul></ul><ul><ul><li>Regression Testing </li></ul></ul><ul><ul><li>Training & Mentoring </li></ul></ul><ul><ul><li>Cutover </li></ul></ul>
    47. 47. Visiting Nurse Service of New York: Phase 2 <ul><li>Physicial Referral EGL TUI > EGL RUI (Pilot) </li></ul><ul><li>RMErui conversion w/ Synchrony </li></ul><ul><ul><li>12 screens converted </li></ul></ul><ul><ul><li>ClearBlade Katana Framework used </li></ul></ul><ul><ul><li>VNS style sheets incorporated </li></ul></ul><ul><ul><li>Portal like look & feel established </li></ul></ul><ul><ul><li>Mash-up functionality added </li></ul></ul><ul><ul><li>Google maps </li></ul></ul><ul><ul><li>Address validation </li></ul></ul><ul><ul><li>Current weather </li></ul></ul><ul><ul><li>Phase 3 planned for Q2 </li></ul></ul><ul><ul><li>Larger conversion </li></ul></ul><ul><ul><li>Salesforce.com integration </li></ul></ul><ul><ul><li>Healthways integration </li></ul></ul>
    48. 48. Quit talking and show me something
    49. 49. Green Screen to Web 2.0/SOA – Conversion ( Not Screen Scraping ) <ul><li>A screen is a visual record </li></ul><ul><li>Convert screen to record </li></ul><ul><li>Convert screen to Web 2.0 page </li></ul><ul><li>One-time conversion </li></ul><ul><li>Result is static code </li></ul>RECORD Upgrade to Web 2.0 1-time static conversion
    50. 50. Green Screen to Web 2.0/SOA - Runtime <ul><li>A screen is a visual record </li></ul><ul><li>Screen data is passed as a record </li></ul><ul><li>App server runs IBM Gateway </li></ul><ul><li>Gateway passes record as a Service </li></ul><ul><li>Browser runs HTML/Javascript </li></ul><ul><li>SOA architecture to legacy program </li></ul>Program converse JEE Middle Tier (WAS) Program converse IBM Gateway request response SOA RECORD
    51. 51. Thank You

    ×