Presentation Subtitle. 9 th CA 2E/CA Plex Worldwide Developer Conference

Transcription

1 Presentation Subtitle 1

2 Introduction/Welcome Message. 2

3 Speakers Lucio Gayosso Sr. Consultant/Nearshore Team Lead. MIS/M, PSM I, BoS Kiyoshi Terasawa Architect 3

4 Agenda o Why.NET? Stay with C++ if Opportunity to spend $? o Benefits o Yes, it will be painful but Common requirements Best Practices We help you 4

5 Why.NET? 5

6 Stay with C++ if o You, Managers, and Users are all happy o You don t like a change 6

7 Opportunity to spend $? o If you want to make your application look and feel current 7

8 Opportunity to spend $? o If you want to expand application features and want to keep CA Plex Easy to integrate with current third party features Java and C# are the final programming languages that CA Plex generates for you *1 Don't worry about using as much as Source code to implement a cool feature that isn't supported by CA Plex ü *1 Unconfirmed statement by CA 8

9 Opportunity to spend $? o If your current Plex application is: WinC Client and RPG Server Your application is deployed to multiple countries (national languages) 9

10 Opportunity to spend $? o If your current Plex application is: WinC Client and WINNTC Server You cannot avoid Unicode, Plex C++ application is non-unicode application runs on Unicode OS even recently upgraded C++ generator 10

11 Benefits 11

12 Benefits o The Application become cool and shine again Customizable Look and Feel o Opening opportunity to integrate with outside world Using newer User Control on the Panel Consuming WebAPI and handle Json or XML output Accessing NoSQL data 12

13 Benefits (Savings) o You might be able to consolidate a number of System i o Opportunities to re-factor and remove obsolete code and features o QA Automation Ready o Ease Deployment via Click Once Scenario: Deploying.NET ClickOnce in CA Plex Application 13

14 Benefits (cont.) o Opportunity to review and establish ALM Practices Suggestion: CM MatchPoint 14

15 Benefits (CA Plex provides) o CA Plex supports Unicode with.net and RPGIV CA Plex Unicode Support o Usable level of Localization support o Expose Plex Functions as Web API 15

16 Yes, it will be painful but 16

17 Common requirements (Team) o Mindset Changes Accept that Plex cannot do everything Accept the Differences and do not complain Off course, you still get a benefit of Model bas development 17

18 Common requirements (prepare) o Analyze application and model o Understand Package and Code Library concept o Source code Object approach decision Model Variant Meta Condition ç recommended o Report Conversion o Application Help System o etc 18

19 Common requirements (dev) o Define Packages Functions o Define Code Library o Source Code Conversion o Report Function Conversions 19

20 Common requirements (Deployment) o Deployment Plan o Document application changes for users 20

21 Best Practices o Analyze your model and make a plan o Have a C# engineer available especially you have C++ or VB source codes o Ask for help before it is too late o Accept differences Think about that there maybe alternate and better solution 21

22 We help you o CMFirst is one of a few organization to provide support for your.net migration Experienced multiple C++ to.net Migration projects With experienced Plex engineers as well as one of the main Plex developer 22

23 CMFirst helps you o CMFirst will Help project planning and implementation Mentor you through the migration project o As a result, you will become Independent get stable environment receive good after Service 23

24 Thank you 24

25 Contact Website: 25