- Home
- » Exodus™
- » Code Conversion Process Overview
- » Code Conversion Process Overview
- » Exodus™
The Steps of Conversion
-
Step 1 - Oracle Forms
The Oracle Forms .fmb module, library and PL/SQL procedures are used as source files. All of this source programming is utilized by Exodus which creates a readable version of the Forms application in Java.
-
Step 2 - Exodus™ Migration
Once the key structures and functions have been organized, Exodus™ translates the original application's components into the corresponding Java plug-in or JSF (ADF) components as required. In doing so, the migrated application maintains the same business logic and can optionally either show the same look and feel as the original application, or convert to a specific user defined screen.
-
Step 3 - Compilation
The compilation process can be performed in any IDE, such as JDeveloper, VisualAge and NetBeans to compile, maintain, and upgrade the migrated application. The Application is now 100% J2EE compliant Java code and as such can be integrated into ANY Java supporting environment or development tool.
-
Step 4 - Deployment
The generated Java Code is object oriented, readable and fully maintainable, ready to be deployed on any J2EE compliant application server and environment. It can now be free of and dependency on proprietary environments and tools. The entire application can now be maintained by any Java proficient developer.
-
Step 5 - Maintaining the converted application
Exodus-VE™ is a visual editor that provides drag and drop capabilities to the maintenance and enhancement of the converted application. This enables clients to start maintaining and enhancing their application immediately after conversion with relative ease.
- Exodus™ - Architecture
Runtime Diagram and Framework - Exodus™ - Benefits
Benefits of Automated Conversion - Exodus™ - Features
Features of the Technology - Exodus-ADF™
Migrate to Oracle ADF - Exodus-VE™
The new visual editor - PL/SQL to J2EE Converter
Benefits and features