Oracle Forms to Java Automated Migration

Oracle Forms to Java Automated Migration

ORMIT™ - Java: The Game Changing Oracle
Forms
to Java Automated Migration Tool

The only fully automated Oracle Forms to Java tool. Ormit™-Java is powered by Re_Forms21

ORMIT™ - Java Makes Business Sense

At least 50% cheaper than a manual migration

SAVE
MONEY
50%+
CHEAPER THAN A
MANUAL MIGRATION

Automated migration will save you considerable time

SAVE
TIME
75%+
TIME SAVED WITH
AUTONOMOUS MIGRATION

reduce the risk of migration error by more than 70%

ELIMINATE
RISK
90%
LESS MIGRATION
ERRORS

ORMIT™-JAVA Makes Technological Sense

Gradual & Secure Migration

No Big Bang approach. Gradual and secure migration allowing you to switch back to Forms on the same database. 

Same DB Structure & Business Logic

The same ease of development as Oracle Forms: an untouched database structure and business logic

An Eclipse IDE Development Environment

Development Environment based on Eclipse IDE

No End User Retraining

Same appearance, transaction handling, shortcuts etc.

Technical aspects of the solution

Powered by Re_Forms21, ORMIT™ Java is a migration to a modern three-layer architecture based on a Java platform

 

User interface layer - Vaadin and HTML5

User interface layer - Vaadin and HTML5

User interface layer - Vaadin and HTML5

Application layer - Java Servlet as application controller

Application layer - Java Servlet as application controller

Application layer - Java Servlet as application controller

Database layer - Oracle database and PL/SQL stored procedure

Database layer - Oracle database and PL/SQL stored procedure

Database layer - Oracle database and PL/SQL stored procedure

New Java Web Architecture

New Java Web Architecture

Why Migrate from Forms to Java?

  • Technology

    Java technology is virtually ubiquitous within large organisations vs Forms

  • Manpower

    The number of Java experts far outweigh that of Forms

  • Costs

    To break away from Oracle licensing costs (application server) and contracts

Oracle Forms to Java Migration FAQ

ORMIT™-Java is a complete solution that allows automatic migration from Oracle Forms to modern three-layer web application. It consists of:

●  A set of Java libraries imitating the operation of Oracle Forms components

●  A set of tools for conversion of Oracle Forms code to Java and XML

●  Developer Toolkit (IDE)

ORMIT™-Java is the only tool that automates between 92% and 98% of real work inputs.

Automated conversion with ORMIT™-Java does not require much analysis, development work or IT expenditures.  Automation leads to cost savings. The bulk of the work is in accompanying clients and testing the applications post migration. Migration will take approximately 25% of the time that rewriting would.

With migration, the functionality remains the same therefore significantly reducing the occurence of bugs that come with rewriiting. On average, opting for migration reduces the risk of errors by around 90%. Testing and  Quality Assurance allow for direct comparison of the quality of the system before and after migration.

It can look exactly like the current Oracle Forms application or have a more modern, customized appearance leveraging HTML5 and CSS. It will also be able to be launched in the browser but without running the Java applet. The user interface will remain unchanged. The same user interface means that business users do not require additional training.

The migration process is a secure phased process that allows you to switch back to Forms at any moment.

Yes it can with some development changes.

ORMIT™-Java is a complete solution that allows automatic migration from Oracle Forms to modern three-layer web application

The layer of the user interface - HTML5 and JavaScript

Application layer - JEE Servlet (WAR)

Database layer - Oracle database and stored procedures PL / SQL

ORMIT™-Java applications can work with any modern application server capable of running Java Servlet API 3.1 (WAR files), eg Tomcat, JBoss, WildFly, WebLogic etc.

All of the business logic contained in Oracle Forms is converted to Java. The business logic contained in database (in stored procedures, functions and packages) remains unchanged. This approach makes it easy to have both Forms and Java version running in parallel during the gradual conversion process.

Our Forms to Java migration solution keeps intact all current business logic and code structures (and nomenclatures) to make sure that it will be easy for your developers to maintain the Java code once migrated.

Since our tool converts Oracle Forms to standard Java code, there is no limit to the choice of application server that can be selected for deployment including but not limited to Tomcat, JBoss or any other open source or proprietary application server running on Oracle Cloud, AWS, Azure or any other on prem server.

Absolutely, after the migration, you get a Java application. It can run on any valid Java environment (including the one within docker).

Sure, as long as you use valid application server (it needs to support Servlet API 3.1). Tomcat will be installed in the Docker container and WAR file will be deployed to Tomcat.

ORMIT-Java natively supports Maven. You can translate Maven configuration to Gradle after the migration and CI/CD should work, however the support for Gradle in IDE may be limited.

Testimonials

"As part of the cooperation, Re_Forms 21 carried out the migration of Toyota Forms system to Toyota JBoss open systems (Java) for Toyota Motor Poland...The migration allowed us to gain better support for the company's operational activity, without having to change the procedures and structure of the application. We could rely on full support from Re_Forms 21, during the migration process..."

Toyota Motor Poland

Toyota Motor Poland

Why RENAPS ?

With more than 20 years of experience, RENAPS has positioned itself as a trusted partner of many high profile brands. Our unparalleled knowledge and experience with Oracle Products make us the ideal partner to help you migrate to Java on time and on budget

Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?Why RENAPS ?