Upgrading from eDeveloper V9.4 to Magic xpa 2.2 and Above (Magic xpa 2.x)
Magic xpa does not support eDeveloper V9's export file structure.
Applications from eDeveloper V9 should be converted to the new Magic xpa structure.
Upgrading an eDeveloper V9.4 application to Magic xpa 2.2 and above is a two-phase migration process.
First, you need to migrate your eDeveloper V9.4 project to a uniPaaS V1.0 project.
-
Magic xpa provides a collection of wizards to easily migrate your application, INI settings, and interface builder data.
-
In the Migration subfolder of the product, located in the Start menu of your desktop, you will find a shortcut to each of the available conversion wizards. Note that these tools are also provided with Magic xpa 2.x, so you do not need to install uniPaaS V1.x for the migration.
Migrating your application to uniPaaS V1.x is done in three main steps:
-
Prepare your application for export.
-
Export your application.
-
Use the Conversion utility to convert an eDeveloper 9.4SP7 application and onward to a uniPaaS project file. After the conversion is finished, you need to open this application using Magic xpa in order to complete the process and convert the application to a Magic xpa application.
Magic xpa also provides the following utilities:
-
The Builder Data Converter, which lets you convert the data created by the eDeveloper V9 COM, WSDL, EJB, and MCI Builders to a Magic xpa project.
-
The Magic.ini Converter, which lets you modify the settings in the V9 Magic.ini to be compatible with Magic xpa.
See also:
Differences Between eDeveloper V9 and uniPaaS V1
Terminology Changes
Then, migrate the resulting uniPaaS V1.0 project to Magic xpa 2.2 and above as described in the Migration from eDeveloper V10.1 or uniPaaS V1.x through V2.0x to Magic xpa topic.
