Oracle Forms to Java Modernization
Our Evo™ Oracle® Forms to Java Modernization tool streamlines operations and generates flexible, non-proprietary web-based applications in both MyFaces JSF and ADF 11g frameworks.
Evolution is a Science. You can make it an art. With Evo™, you can create a real web application that leverages Java technologies and strategies. You can determine what should be re-used from your legacy application in the resultant application. Why convert redundant logic over and over again? You don't have to with Evo.
Evo automates a high percentage of a Forms-to-Java modernization project. Evo loads in a Forms file and extracts information about all the data access, UI elements, and PL/SQL code in form triggers, functions and procedures. Evo utilizes a powerful PL/SQL parsing engine to translate the PL/SQL code into Java.
During this process, Evo extracts the tables, views and stored procedures the application uses from the PL/SQL code and Forms meta-data. Using this data, and meta-data from the database, Evo creates a data-persistence layer using either EJB's or the J2EE DAO data access pattern.
Evo itself is laid out to follow your conversion methodology, from Analysis through Construction. Visibility into your existing application and accessibility to original constructs are at your fingertips.
About What You Have
Understanding how your Forms application is tied together is key. With the Evo Function Tree, this analysis is a few clicks away.
"Why is that important?" Good question. It's important to know what your dependencies are as you go through the conversion process in debugging the converted application or simply taking account for your actions. The Evo Function Tree provides you this view.
Java - Preview and Use
With Evo, you can preview what a PL/SQL module may look like translated in Java, on the fly and in real-time.
The Power of Object Re-use
One of the many benefits of Evo is the ability to have insight into how your original Forms application is constructed. In many client/server applications, code is redundant. The same PRE_INSERT_TRIGGER may fire many times within a Form or is used again within multiple Forms. With Evo, you can analyze code to check for redundancies and determine where you may need to consolidate your objects, creating a much more maintainable application.Object re-use doesn't stop there. Data access objects should be consolidated such that common methods for accessing data can be re-used throughout the application.
Once you've engineered your Evolution, the build is a click away. The important thing to know about Evo is that the Constructors, upon which Evo is built, are completely customizable by our experts at Vgo or, with training, you. When a Constructor is created for your project, it is available as a new conversion project and immediately usable.
With Evo, developers and architects have access to the missing link in automated conversions - complete access to all source code and the flexibility to do what they want. Client/server conversions can truly evolve with Evo. Let your developers focus on true design points in this difficult conversion while they automate their development with aspects that make sense to automate. You do not need to "settle" for hard-to-read code that blindly converts legacy components all over your Java application.
To see for yourself how Evo can help with your Oracle Forms conversion