Converting MAGIC-based Applications to RIA
 
Particularly in today's difficult economic climate, enterprises are looking for ways to reduce their IT budgets. RIA significantly lowers total cost of ownership since it eliminates the need to install client-side software and maintain each user, while performing application and platform updates on a centralized server.
An increasing number of enterprises are in the process of transitioning their client-server business applications to Rich Internet Applications (RIA). To address this growing trend, Kopel Reem Software has developed a special set of filters that enable migrating fast and therefore relatively low costs, from any older version to any new uniPaaS RIA.

Conversion of client-server applications to RIA must take into account the following needs
    • Conversion of all online screens to rich client screens

    • Conversion of all batch processes that perform calls to rich client tasks

    • Changes in logic due to the division of "work" between the client and the server

    • Code changes to enrich the RIA application to compensate for lack of certain functionality at the client level

 

How It Works

Kopel Reem makes it easy for enterprises to upgrade their MAGIC-based business applications, allowing them to benefit from the advantages of RIA. Automatic tools facilitate straightforward conversion of existing client-server applications to RIA architecture with minimum cost and effort. Conversion to RIA avoids the costs and complexity of developing browser-based applications from scratch, while preserving the existing knowledge of your developers.
Using
KopelReem's proven methodology, the conversion process is performed in three stages.
 

Stage 1 – Mapping

This stage is executed in a completely automated fashion using a unique tool developed by Kopel Reem – the KopeliZer. The tool generates an easy-to-use display of the application's flow structure, saving valuable time in the actual conversion by eliminating the use of "trial and error" methods. This provides a high-level view of the project and facilitates decision-making regarding the required changes (without requiring previous familiarity with the application).
During this stage,
KopelReem will identify all the potential problems in the conversion and categorize them by subject and severity. The highly accurate mapping information will reduce the chance of error and save time and money. In addition, the accuracy of this analysis allows Kopel Reem to provide customers with precise cost estimates for the entire conversion process in advance..
 
Stage 2 - Automatic Conversion
The main stage of the conversion is performed using automatic tools that substantially shorten the time required and minimize the number of bugs. The information gathered in the Mapping stage can be used to minimize the conversion effort by identifying and converting only those programs that are truly needed. Moreover, only batch processes that call online tasks in their sub-tree need to be converted, for example, task managers or tasks that execute certain logic before they call an online program.
Moving logic from Task Prefix to Record Prefix in the case that TP contain Client Side logic, Changing all the Online task transaction as needed. The online tasks, together with their structures, controls and modules, automatically become rich client-compatible. Automatic tools handle conversion problems related to printing.
 
Stage 3 - Manual Handling and Completion
This stage is performed by Kopel Reem's skilled experts, who have vast experience in carrying out these types of activities. Manual handling is needed in cases where there is a need of concept changes, for example, all the use of I/O functions (FileCopy, FileDelte, FileDlg….) or using of OCX, DLL's, UDP, UDF… Kopel Reem has developed components that can be used to enhance the manual activities.
This stage also includes reorganizing the flow in places where the business logic creates unnecessary calls to the server. Manual changes to the business logic may be required to replace functions that are not supported in RIA, like KBPut and KBGet.