From Online to Rich Client Applications (Magic xpa 4.x)
When changing your application from the Online paradigm to the Rich Internet paradigm, there are initial steps that you need to perform and some behavioral changes that you need to take into consideration. In addition, there are performance considerations that must be taken into account.
Before making any changes to your Client-Server application, you should execute the Rich Client Preparation utility, which you access by selecting Rich Client Preparation from the Options menu. This utility scans your models and creates new Rich Client Display models based on the existing GUI Display models. The new Rich Client models will be used later on when converting the GUI display forms into Rich Client display forms.
Tasks with an RM Compatible logic unit cannot be converted to Rich Client tasks. You should convert such logic into an event-driven logic. Use the Record Main converter (RMC), which is an optional product that you can choose to install when installing Magic xpa. The RMC will also provide you with a list of issues that it did not handle.
Run the Magic Optimizer on your application. The Optimizer is an optional product that you can choose to install when installing Magic xpa. The Optimizer will produce a report indicating the places demanding manual intervention for the conversion.
The tool does not supply information for all cases, such as components being used by the application.
Note that the Optimizer version that is bundled with Magic xpa is only a demo version with execution limitations, except for the documentation option, which is fully functional.
|
The Magic xpa Single User Edition does not support the Record Main converter and the Optimizer.
|