CM M3 CA2E to PLEX Modernization
•Download as PPTX, PDF•
1 like•279 views
In this presentation you will learn about our proprietary methodology to migrate CA 2E to PLEX. The process has three primary phases sandwiched between a time of preparation and the final project completion. Find out why Fortune 500 companies used CM First to spear head the project. Cm First also compares the CA 2E model functionality with Plex model functionality. Understanding the several areas of similarity will help with the modernization process.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to CM M3 CA2E to PLEX Modernization
Similar to CM M3 CA2E to PLEX Modernization (20)
Recently uploaded
Recently uploaded (20)
CM M3 CA2E to PLEX Modernization
- 1. CM M3 CA 2E to CA Plex Modernization
- 2. Who is CM First? Enterprise Software Development Integrator • Offices in Switzerland, USA, Italy, France, India • Network of worldwide resale partners (Americas, EMEA, APJ, ANZ) CA Primary Sales and Technology Partner • CA 2E, CA Plex, CA Repository • Footprint covers 20% of Installed Base IBM Advanced Partner • IBM Power Systems and zOS App Dev Products • CM Matchpoint ALM Suite • CM WebClient • CM Power (PHP) Suite • CM M3 (CA Migration / Modernization) • CM Meta Analytics Semantic Design Partner • DMS Code Analysis / Transformation
- 3. Select CM First Modernization Customers
- 4. Before CA 2E with RPG or COBOL
- 5. After CA Plex with Java / Rich Web App
- 7. Phases • Project Preparation • Phase 1 – Model Analysis • Phase 2 – Model Conversion • Phase 3 – Testing • Project Completion
- 8. Migration Phases - Project Preparation • CA 2E Model • Clean Application • Test Data • Install Model at CM First
- 9. Migration – Phase 1 • Phase 1 – Model Analysis • Number of objects • Types of objects • User source • Execute Messages • Helps determine complexity, cost and duration.
- 10. Migration- Phase 2 • Phase 2 – Model Conversion • Preliminary Model • Preliminary Migration • Validation • Migration Adjustments • Final Model • Final Migration • Validation
- 11. Migration- Phase 2 • Phase 2 – Convert 2E Model to XML 2E Model XML Documents XML Documents XML Documents
- 12. Migration- Phase 2 • Phase 2 – Transform XML to Plex Version XML Documents XML Documents XML Documents Plex Definitions
- 13. Migration- Phase 2 • Phase 2 – Import into Plex Plex Definitions Plex Model
- 14. Migration- Phase 3 • Phase 3 – Testing and Validation • Test Converted Application • Compare Functionality with 2E Application • Review Screen Updates • Review Server Functionality • Correct Any Issues Encountered • Customer Acceptance
- 15. Migration- Completion • Project Completion • Deliver Plex Local Model • Training on Migrated Model • Support • CM First Guarantee
- 17. Compare 2E to Plex • Data Files
- 18. Compare 2E to Plex • File Definitions
- 19. Compare 2E to Plex • Function Screens
- 20. Compare 2E to Plex • Action Diagrams
- 21. Compare 2E to Plex • Action Diagram User Points - DSPFIL
- 22. Compare 2E to Plex • Messages
- 23. Compare 2E to Plex • Call to Function in 2E
- 24. Compare 2E to Plex • Call to Function in Plex
- 26. Next Steps • Migration Questionnaire • Start to have conversation on precise scope • Sizing of environment, technical details • Formal Analysis Proposal • Analysis Project • Migration Assessment Report • Fixed Price Proposal
Editor's Notes
- In this presentation, we will take a look at …
- First, for those of you who are not familiar with CM First, here is an overview. Who is CM First? CM First is an Enterprise Software Development and Integrator with offices in Switzerland, US, Italy, France and India. We have a worldwide network of resale partners in the Americas, Europe, Middle East and Africa, Asia, Pacific and Japan and Australia and New Zeland. Our primary business partnership is with CA. We primarily focus on CA 2E, CA Plex and CA Repository. We do a lot of work to enhance customer experience around these products. CM First is also and IBM Advanced Partner on the IBM Power and zOS. We also develop and maintain several of our own products. Matchpoint ALM Suite, WebClient, CM Power PHP Suite, M3 migration and Modernization and Meta Analytics. CM First is also a partner with Symantic Design where we were together to develop DMS Code Analysis and Transformation
- Select CM First / SD Modernization Customers Here are some of our more recognized customers. We are pleased to be able to work with companies of many sized and assist companies in reaching specific goals.
- 6
- Project Preparation During the project preparation we are working together with the customer to get a successful foundation for the project. The cleaner the 2E model is the better the migration becomes. There is no need to send extra functions, fields and unwanted objects into Plex. This is the best time to make sure the unwanted objects are eliminated. It is also important that the 2E application directly represents the 2E Model. To do this compile all the programs and fix any issues that come about. We find that over the years there are some objects that have been manipulated by hand or do not represent the current state of the 2E function definition. The best way to manage this is to deliver a freshly compiled application. There will be a lot of testing going on at several stages of the process so it is important to get data that can be used to test all of the application functionality. The data will be used by several engineers to it is best to not take a copy of production and send that. CM First does enforce confidentiality but we want to focus on the migration and not on data security. Once CM First gets a clean model we will install it on our IBMi for conversion purposes. If the model is 8.1 or earlier we will need to upgrade the model to a current version of 2E. It could take additional time if the model is from a version of 7 or earlier.
- Before the migration begins it is important for CM First to receive a model that does not have a lot of invalid object definitions. The customer will find it beneficial as well because there is no need to migrate objects that are not actually part of the application anymore. Most models have collected field definitions, functions, files and messages that are no longer needed. These unused object definitions should be removed before sending the model to CM First. The application should also be newly generated and compiled to make sure that the application directly reflects the model. This will eliminate the possibility of manually fixed programs, programs that have been deleted in 2E but not in the application and other potential issues. CM First will need test data that can be used by several engineers to test the current application and the application once it has been migrated to Plex. This data should not be live confidential data. Once CM First receives the save files of the model, application and data the model and application are installed on the CM First IBMi. If the model is prior to 8.5 it must be upgraded. The recommended 2E version to us is 8.6. If CM First has to convert the application from a 2E version prior to 8.1 there will be additional time and cost added to the project.
- CM First does an extensive analysis of the 2E Model. We determine the number of objects in the model by type We review the user source by quantity and complexity. Execute user messages must be reviewed as they are much like user source. There are options to look at when dealing with the user source. CM First can be contracted to rewrite the source in Plex or java. Customer can rewrite the source in Plex or Java. Plex APIs can be used to call the native programs. Each method has pros and cons. However, a decision must be made on how to handle the user source in order to complete the project successfully on budget and within an acceptable timeframe. The full analysis that CM First completes helps to determine the expected length, cost and duration of the project. Results are used in creating an acceptable project timeline and assignment of appropriate resources to the tasks.
- The migration process is run at least 2 times. First we do a preliminary model migration. During this migration we will identify any issues that came up. Issues will be looked at and a solution will be defined. In some cases it may mean the model needs to be adjusted while in other cases it could mean a modification of Plex patterns. By the time we are done with this phase we will expect a 99+ percent of the 2E model supported objects to be migrated into the Plex. The final migration normally occurs with a freshly delivered model that is adjusted for the final migration. This model will provide the excellent results that we would expect. Once the migration is completed we will validate that the objects expected to migrate were migrated as expected. Full testing of the Plex Model and generated application occur in Phase 3. There are several key steps in the actual migration phase.
- The 2E model is first converted to XML. We are not talking about just functions or fields but the entire 2E repository is converted to 5 different XML documents. These documents contain everything from field definitions to conditions to location of fields on the screens.
- The XML files are then run through a transformation process that takes all the XML and converts it to object files that Plex will be able to import. This transformation is where the magic happens. Everthing needed to build the Plex Model from the 2E model is defined and refined so Plex can use the information.
- Finally, a Plex API is used to import the transformed files into Plex. We have created some Plex patterns that help create a model that maintains some similarities to 2E in order to help 2E developers move into Plex development more quickly. At the end of this import you will have a fully functional Plex Model that represents your original 2E Model.
- Once the migration is completed intensive testing must be done. The goal of this process is to make sure the Plex model and application have at least the same functionality as the 2E model and application. Testing is done at the model level to insure the model is migrated correctly to Plex. Testing is also done on the migrated application to demonstrate that the application has the same functionality that the original 2E application had. This intense testing is accomplished with the Customer’s involvement. Once the Customer is satisfied with the migration it is considered complete.
- Upon completion CM First delivers the customer a Plex Local Model. This model contains all the migrated information from 2E and has been thoroughly tested by both CM First and the customer. Our job is not done until the customer is happy. We also provide training for developers to learn how to work with the new model in Plex. CM First takes pride in providing outstanding support to all customers. There is also a Guarantee that any supported feature will be guaranteed to work at no additional charge
- 16
- Here is an example of the 2E database relations screen vs the Object browser in Plex. You can see that in Plex all the Data files are placed under a Data Entity in Plex. This provides a similar organization in Plex as in 2E. Instead of doing a Z to get to the access paths the tree is simply expanded in Plex to easily find the file.
- File definitions are also very similar between 2E and Plex. In 2E on the File Definition screen you can see a single file definition by entering an S on a file. In Plex a similar display is seen by opening a file in the Model Editor. Here you see what are called Triples. These Triples have a similar look to a 2E file definition. Note that Triples are a major tool used in Plex to define most objects.
- Here you see the 2E screen editor and a Plex Panel editor. In the Panel editor you can move the buttons and fields around as needed to make the application look good. This panel can be generated in Java Swing directly from Plex or in an AJAX web screen by using Web Client.
- Both 2E and Plex use action diagrams to add logic to a program. This example displays a common CASE statement in both action diagrams. Just like in 2E there are user points where logic can be added.
- Here is a comparison of User points in 2E with some of the User points in Plex. We developed a pattern so that Action Diagrams User points were similar between Plex and 2E.
- 2E and Plex have similar methods of calling functions. Here you see a 2E action diagram calling a function Saisie in file Article. When you do an FF on the function call the parameters are displayed.
- Here you see a Call command in the Plex action diagram to the function Saisie in file Article. The parameters can also be seen in the function window.
- These are just a few of the similarities between 2E and Plex. Plex does include a host of additional functionality that is not available to 2E. So once you get comfortable with the pieces of Plex that you need for your maintaining you 2E application you will be able to gain more efficiency and capabilities as you get into the world of Plex. So where do we go from here?
- Next Steps We can provide you with a Migration Questionnaire to help in organizing thoughts on the scope of your migration. It is important to consider the size of your environment and to look into the details of your system. The information from the questionnaire can be used to get you a formal analysis proposal. Once this step is completed we can begin an analysis and create a custom Migration Assessment report. We feel confident that when we complete a full assessment we have sufficient information to make a realistic Fixed Price Proposal. This way you know exactly what to expect. We do not want you to have any unwanted surprises down the road.