Re-platforming CA IBM I Applications

1. Re-platforming CA IBM I Applications

2. Speakers Roger Hammer Director of Software Development & Services CM First Abram Darnutzer Senior Consultant CM First Eric Giron Senior Consultant CM First

3. Agenda • CM M3 Overview • Why M3 • M3 Components • Assessment • High Level Process Model • POC Result • M3 Agile Project Management Approach • Demo • Project Experiences • CM evolveIT Plex Model Analysis • Q&A

4. 2E Plex Terminology • Model • Access path • Context (CTX) • Sub file • Group Model • View • Variable • Grid

5. CM M3 Overview Reuse Code Base and Layout Web / Mobile ASAP

6. CA 2E (Synon) models & generated applications Native Code: RPG COBOL CL/i5/OS artifacts Plus: Native code modernization Replatform from IBM i - AS/400 Regression testing CM M3 Process: From 2E to Plex/Java/C# Original 5250 Screens Robust Plex/Java Environment(for APIs/SOA, Web, Mobile) Modernize some or all of the Model

7. Why M3?

8. M3? Model based Modernization Methodology

9. Why M3? M3 is your solution if you … • want to modernize 2E application to Web application • don’t like Screen Scraper • don’t like or know native language coding • love model base tool • consider leaving System i

10. Why M3? Benefits • Great Web UX opportunity • The application design is maintained with Model base tool • No need to learn native language • Two re-platform options • Stay on System i • Move off ofSystem i

11. High Level Process Model

12. Start with Green Screen Application

13. Migration Decision Process Go / No Go Results, Plan, Proposal Automated Objects Fixed Price

14. Overall Migration Process Automated Migration Refactoring (CMF/Client) Production Quality Assurance (Client)

15. Migration Technical Process Build and Test in Plex / Java / Linux 2E Model Extraction Set up environment / Clean 2E Model Extract App Structure as XML Validate Completeness Of XML Customer Validation Ready

16. M3 Components

17. M3 Components • CA Plex Group Models for M3 • M3 Transform Engine • M3 Java Runtime • CM WebClient for M3

18. CA Plex Group Models for M3 • M3 ADCMS • Library Model that enables your 2E objects behave as Web Application • M3 Migbase • The model your 2E objects are migrated

19. CA Plex Group Models for M3 • WebClient readiness Panel Design • STS field is defined as Combo box • Command keys defined as button • Sub-file selectors as button

20. M3 Transform Engine • M3 Transform engine Migrate XML to Plex • Entity Relations • Functions with action diagram • Ready for use panel layout designs • Adding Events with push button • Tab sequence • Color Conversion • User Defined Field Type

21. M3 Java Runtime • Fill the Gap between 2E and Plex application behavior differences! • Provide 2E like CTX (Region) fields handling • External and Internal function CTX sharing like WRK, LCL • Populate CTX like PGM, JOB • Provide 2E like event/screen processing • Access Database via JDBC • Batch Function Call • EXECMSG

22. CM WebClient for M3 • Run on Web browser • Calendar Control for Date Edit Control • Confirm Prompt as pop up • Customize control via template

23. Converted Application

24. Customized Application

25. Assessment

26. Assessment Goals • Counts and Lists of Objects • Manual Refactoring Analysis • Non supported code and structures • Security • And much more • “AS-IS” and “TO-BE” Architectures • Report with Appendices • Project Plan with Fixed Price and Time and Material components.

27. Process • 2 Engineers for 6 weeks • -1 week on site • Access to model, code, and SME’s • Off-premise model analysis is preferable • Automated tools • Manual inspection • Discussions and decisions on architecture of “To Be” application and incremental phases (if used).

28. Don’t migrate what you don’t need 3 0 % 6% database objects • conditions • functions • messages • fields,etc.

29. POC Results

30. POC Prototype Summary • Full Model Counts • 21935 functions • 1165 tables • POC Counts • 1000 functions (5 demo screens) • 1165 tables to Plex, 10 with data to Oracle • Target • Plex/Java/Eclipse • Oracle for one table (The rest left in DB2) • Tomcat / RIA Browser App (Any Platform)

31. M3 Agile Project Management Approach

32. CM First Agile Project Approach • Agile Approach • Value Driven Delivery • Stakeholder Engagement • Team Performance • Adaptive Planning • Problem Detection and Resolution • Continuous Improvement (Product, Process, People)

33. Value Driven Delivery • Deliver Valuable Results • High Value Increments • Deliver Early & Often • Stakeholder feedback • Feedback used to improve

34. Stakeholder Engagement • Build a Trusting Environment • Align with Needs and Expectations • Balance Requests with Understanding • Participation & Collaboration • Tools for Effective and Informed Decisions

35. Team Performance • Trusting, Learning, Collaboration • Conflict Resolution Promoting Self-Organization • Strong Relationships Among Teams • Cultivate Culture of High Performance

36. Adaptive Planning • Plan Based on Goals, Values, Constraints • Produce and Maintain Evolving Plan • Stakeholder Feedback • Review findings

37. Problem Detection and Resolution • Continuously Identify Problems, Impediments, Risks • Prioritize and Resolve in Timely Manner • Monitor and Communicate Status • Implement Process Improvements

38. Continuous Improvement • Continuously Improve Quality • Continuously Improve Effectiveness • Continuously Improve Value of: Product, Process & People

39. CM First Project Management Approach • PMP Certified Project Consultant • Agile SCRUM Team Process • Multi-level planning (Project, Sprint, Daily) • State of the Art Communication Processes • Project Automation at Every Level • The near-shore team in Honduras • QA and DevOps overview Customer Delight Project Excellence

40. Planning at Every Level • Project Gantt Chart Planning • Sprint Planning • Daily SCRUM Planning • Early Problem Identification • Fast Resolution

41. Communication • Daily Planned & Ad-Hoc Team Communication • Weekly Status Meeting with Stakeholders • Automated Task / QA / Issues Communication • Continuous Social Media style communication

42. Distributed Teams • Experienced Distributed Team Model • Brings the Right Skills to the Project • Excellence in Communications • Anywhere in the World! • Customer / Stakeholders • Integrated Off Shore Team - Honduras Like Sitting Around A Table

43. DevOps process • Distributed Development – Eclipse + GIT / SVN • Proprietary Gen / Build Technology • Continuous Integration • Automated Testing - SmartBear

44. Project Tools • Immediate Communications to the right Person or Group • Trello - Task & Issue Management • Every Team member has Desktop Sharing • 1 to 1 or Group Communications - Skype for business Trello Boards Skype for Business

45. $ Identify Errors Identify Errors Re-Discover Re-Code Agile Approach Distributed Teams Bring the right resources to each project with support available at a moments notice Agile – SCRUM focuses teams on the right actions at the right time with continuous delivery. CM First Projects Continuous Improvement Adaptive Planning • Adaptive Planning and Execution reduces risk and brings projects in on-time – Savings! • Always looking for better ways to bring value to a customers project

46. Demo

47. Demo • Demo: 2E Application • Transform: 2E Model XML to Plex Model  • Development: Plex developer work with MatchPoint • Build: Plex Model to deployable file • Run: How 2E application looks as Web Client 

48. 2E Application

49. 2E Application

50. 2E Application