Your SlideShare is downloading. ×

M3 CA 2E (Synon) Modernization

1,289

Published on

Modernization of CA 2E (Synon) to Java or C# Applications using CA Plex

Modernization of CA 2E (Synon) to Java or C# Applications using CA Plex

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,289
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • There are a lot of ways to quote modernize from green screen to the web based environment. For example, screen scraping and native code translation programs are options. However, there are not many true modernization methodologies that modernize both the presentation layer and also bring your development environment into the modern day. For many people this represents the holy grail of modernization, that many seek but few actually find.
  • If your organization is looking into fully modernization options, then there are a few questions that you should be asking your modernization vendor. The first question is the degree of automation. There are many that claim their approach is highly automated, but when the rubber meets the road the level of automation may only reach somewhere between 60-95%. If your modernization vendor cannot give you a fixed bid and schedule for the CA 2E model migration, then perhaps they are not employing truly automated techniques, which could leave you open to cost and schedule overruns.The second is maintainability by your staff. In many cases the new technology cannot be effectively maintained, due to learning curve or due to poor translation techniques. Ask to see examples of code, and try some refactoring yourself. The bottom line may be that the CA Plex model based environment is most productive option, due to its close similarities to CA 2E.Third, see if you can take your application immediately to the web and communicate with other enterprise app via SOA service buses. The M3 approach is instantly web 2.0 and SOA-enabled.The fact is that there are few options that can meet all of these criteria. We
  • The M3 approach is more than just a code migration tool, it is a complete start to finish methodology to modernization – from analysis to regression test. It includes re-platforming, web, and SOA as core components.The M3 approach help you avoid costly mistakes that others have made:Web facing and screen scraping, for example, are excellent point solutions for putting your applications on the web. However, many have found the results limiting, and the costs to maintain business logic at multiple levels excessive.Manual migrations often suffer from uneven quality, and the time and cost required is often unpalatable for the business.Syntax translations of CA 2E generated code can suffer from maintainability issues or contain runtime charges you must pay year after year.The total ownership costs of packages can often be far above the original acquisition cost – requiring year over year maintenance, and heavy programming burdens to integrate and customize.
  • The M3 approach is more than just a code migration tool, it is a complete start to finish methodology to modernization – from analysis to regression test. It includes re-platforming, web, and SOA as core components.The M3 approach help you avoid costly mistakes that others have made:Web facing and screen scraping, for example, are excellent point solutions for putting your applications on the web. However, many have found the results limiting, and the costs to maintain business logic at multiple levels excessive.Manual migrations often suffer from uneven quality, and the time and cost required is often unpalatable for the business.Syntax translations of CA 2E generated code can suffer from maintainability issues or contain runtime charges you must pay year after year.The total ownership costs of packages can often be far above the original acquisition cost – requiring year over year maintenance, and heavy programming burdens to integrate and customize.
  • Lets take a look at what model based migration from CA 2E to CA Plex looks like. It means taking your green screen applications into a new technology, that gives you the ability to execute your tried and true business logic with new presentations. One option is to take your application and generate as client-server. Modernized applications can also be generated as true Ajax web apps, right out of the box.
  • Lets take a look at what is involved in an end to end migration.In a typical CA 2E modernization exercise, the bulk of the code is of course embedded in the CA 2E model. However, in many cases there is also significant code that lies outside the model – for example user source or user programs that may be hand coded in RPG or COBOL. There is also likely CL programs, that may control platform dependent constructs like data queues, printers, etc.It is important that a migration consider all of this in a holistic manner, so the first step to any modernization should be an analysis step. In this step we look at your model using automate tools, and identify any activities that must be done with custom components. For example, a submit job step would be accomplished differently on a Windows platform. If you have a large amount of hand written code, the other tools can employed to address this.After analysis, the code migration step begins. For the CA 2E code, this is an automated step that involves converting the CA 2E model to XML and running a rules-based process to migrate into Plex, using the Plex model API’s. For native code, this means either an automated migration or if there are small amounts of code, doing this manually.Regression testing is integral to the process. We recommend using automated tooling like Worksoft certify, to ensure that functional equivalence has been reached.Once you have reached functional equivalence, you are then in a new modern environment that you can use to exploit new technologies like SOA and the web. Your developers will have graphical IDE’s at their disposal, such as CA Plex, Eclipse, Rational, and Visual Studio. Functions can be deployed to new environments like Websphere, using modern languages like Java. Modern databases like DB2 UDB, SQL Server, and Oracle can also be utilized.
  • Demo DataboroughCreate ERD’sCreate Function FlowsCreate DocumentationExtract Business RulesCreate Application Area
  • Demo DataboroughCreate ERD’sCreate Function FlowsCreate DocumentationExtract Business RulesCreate Application Area
  • Ok, I hope that the demo was enlightening on how our process works. I would like to summarize on three key pointsUsing the M3 migration capability, you end up with a truly maintainable and re-factorable end product, that is web based and can be extended to SOA frameworks.You can make use new tooling such as CA Plex, Eclipse, and Rational - that make the development process more effective, and enable you to integrate into other enterprise applications.You can start to use new application capabilities, such as tab presentations and web portals – to make your CA 2E application more user friendly and attractive to your users.
  • Transcript

    • 1. CA 2E / CA Plex Modernization Roadmap Overview & Demonstrations Chicago and Cincinnati, Sept 2010
    • 2. A Multitude of Ways to Modernize But few RIGHT WAYS
    • 3. The Right Way Know before you buy • Effective modernization requires: • High levels of automation, approach 100% • maintainability by existing staff • web applications and SOA • Few get it right • ADC does • M3 methodology
    • 4. The M3 Way Automated modernization with refactoring • More than a tool – an entire methodology • fast & maintainable • +multiplatform, +web, +SOA • Avoid costly risks: • Dual environment web facing / screen scraping • Keep business logic out of presentation layer • manual migration (uneven quality, cost, timeframe) • syntax translators (maintainability, “JOBOL”, runtimes) • packages (acquisition & customization expense)
    • 5. M3 Steps Automated modernization with refactoring Analysis & Migration
    • 6. Step 1 – CA 2E WebOption • Optional Step, but with powerful advantages • Web Interface generated directly from CA 2E • Quick success with minimal investment • Your developers and users do not require extensive retraining • The first step on the journey • Exposure to web technology, developers and users • Start to link 5250 business logic with the rest of the business • Compatible with next steps on journey • Code remains in migrate-able 2E logic • CSS and styles can be reused.
    • 7. CA 2E Web Option • Web environment for IBM i applications • Convert your green screens to HTML pages • Access your existing applications from the web • Open up your applications to customers, suppliers, vendors • Differentiator: Model Based Generator with seamless integration to CA 2E
    • 8. CA 2E Application CA 2E Markup Language DDS Generator Skeletons 5250 Data Stream HTML Skeleton Page Links CA 2E Web Option External HTML Java Applets Java Cascading HTML Page Pages Script Style Sheets
    • 9. CA 2E 8.5 – New Capabilites • Additional Management of Multiple Environments • Additional JavaScript Capabilities • Example – built in context menu • Example – detect multiple input attempts • Performance Enhancements • Skeleton Control Enhancements • Dev and Production Value Separation • Caching
    • 10. Web UI - Walkthrough – Step 1 Genius Main Menu ‘Underwriting’ is selected to begin creating a policy…
    • 11. Web UI - Walkthrough – Step 2
    • 12. Web UI - Walkthrough – Step 3
    • 13. Web UI - Walkthrough – Step 4
    • 14. Web UI - Walkthrough – Step 5
    • 15. Web UI - Walkthrough – Step 6
    • 16. M3 Steps Automated modernization with refactoring Analysis & Migration
    • 17. ADC’s M3 Model-based Migration Methodology
    • 18. M3 Process XML based design migration Original 5250 New Environment (SOA & Web) Migration Analysis (discovery XML 2E) (ADCMS services) • CA 2E (Synon) models & generated applications • Native code • Native: modernization • RPG • COBOL • Worksoft Certify • CL/i5/OS artifacts regression testing
    • 19. Analysis Entire Application Application Areas Application Area 1 Rules Application Area 2 Rules Application Area 3 Rules 24 Copyright © 2009
    • 20. Automated XML / Plex API’s 25
    • 21. Demonstration
    • 22. M3 Steps Automated modernization with refactoring Analysis & Migration
    • 23. Refactoring… Main Menu 1. Work with Conferences 2. Work with Venues Work Work Work with with Conf Venue Other Enter Cancel Change Create Change Delete Create Change Delete Conf Venue Venue Venue Other Other Other Conf Conf Work Work with with Details Addr Create Change Delete Create Change Delete Details Details Details Addr Addr Addr Work with Dtls Create Change Delete Dtls Dtls Dtls 28
    • 24. SOA / Workflow / Automation Modernized Panel Function SOA Bus Modernized Server Function XML/SOAP Web Service Call
    • 25. Summary More than modernization • Refactoring = business advantage • new business logic • SOA / open access • New development process • no screen scraping • no syntax translation • New application capabilities • user-friendly features (tabs, wizards, portals, etc.)

    ×