Frequently Asked Questions

Do you have a demo?

Yes. You can find it here: M2J Converter Demo

Should we upgrade to Magic uniPaaS?

We currently support converting business logic developed in Magic version V9.4 and earlier versions. Once your code is in uniPaaS there is no way back. Upgrading from Magic eDeveloper to Magic uniPaaS should not be underestimated: If your application has Record Main logic, you will have to factor in the time and cost of identifying and modifying the code the uniPaaS RM Converter (bundled with uniPaaS) has generated to address changes in behavior and change code that could not be converted by the uniPaaS RM Converter.

Check out this short uniPaaS RM Converter clip that demonstrates the RM Converter and a few of the challenges of moving to uniPaaS' event driven paradigm.

We completely avoid these RM removal problems for you when you convert your business logic to Java. You can find more details about upgrading to uniPaaS here.

Do you convert all our Magic Record Main logic?

Why is it that M2J can convert all the Record Main logic, while MSE can't?

No. You do not need a runtime license to deploy your application. Furthermore: the resulting code does not use any third party software either. This means that you are free to duplicate, and distribute your application as you see fit.

How does the converter work?

The M2J converter reads and parses your business logic from the export file and your environment files. The fully automated conversion process converts your business logic into native Java code. All you have to do is specify where the input files are and specify where you want the output to go. We do not convert or duplicate Magic's development or deployment executables. Before the conversion, your business logic needs to be interpreted by Magic's deployment environment. After the conversion your business logic has been translated into native Java code which no longer needs to be interpreted by a proprietary runtime environment.

The automated conversion process takes less than an hour to perform its Magic to Java conversion for even the largest applications.

Absolutely. After all, we only convert your  business logic. We have been very careful not to infringe on MSE's copyright. This was easy: We did not need MSE's products or proprietary information to build the converter nor do you need any of MSE's products or proprietary information during deployment for that matter. We do not convert any of MSE's products. We simply let you use Java's standard runtime environment to deploy the application logic we generate. Java's standard runtime offers us a superset of capabilities compared to Magic's runtime. There was no need to reinvent or reverse engineer the wheel.

Is the resulting code 100% pure Java?

Yes. And 100% open source as well. You decide how you want to deploy your application.

Can I use Eclipse to maintain the resulting Java code?

Yes. You can maintain the resulting code in the Java IDE of your choice. There are many great Java IDE's available, and most of them are free, including Eclipse, NetBeans, jDeveloper and many others. You will see the same task hierarchy in these Java IDE's as you used to design your business logic in Magic eDeveloper, as nested Magic tasks have become nested Java classes.

Will my entire Magic Client/Server application be converted?

Yes. All your business logic, all your models, programs, tasks, operations, event handlers, GUI forms and their controls, your menu systems, and your database definitions will be converted to a fully functional Java application.

There are two main reasons:

0. The application logic you develop with Magic eDeveloper is very structured, and very high level, with clean separation between data access, business rules and GUI. Converting this type of application logic is easier than say converting from RPG or COBOL.
0. The Java target platform offers a superset in functionality of what is offered in Magic eDeveloper. This means every part of the conversion can be automated.