Technical aspects of the solution

User interface layer - Vaadin and HTML5

Application layer - Java Servlet as application controller

Database layer - Oracle database and PL/SQL stored procedure

Set of Java libraries simulating the operation of Oracle Forms components

A server capable of running a Java Servlet (e.g. WebLogic)

Automatic migrator of Oracle Forms to Vaadin forms

Business logic included in the triggers in forms is transferred with automatic support according to a pre-defined scheme

Logic included in database's PL/SQL stored procedures remains unchanged

Set of Java libraries simulating the operation of Oracle Forms components

A server capable of running a Java Servlet (e.g. WebLogic)

Automatic migrator of Oracle Forms to Vaadin forms

Business logic included in the triggers in forms is transferred with automatic support according to a pre-defined scheme

Logic included in database's PL/SQL stored procedures remains unchanged

Code Compare before and after

PL/SQL

Java




PACKAGE EMP_PKG IS
  PROCEDURE fill_job_name;
END;



PACKAGE BODY EMP_PKG IS 
  PROCEDURE fill_job_name IS
    CURSOR lookup_job IS
      SELECT job_title
      FROM jobs
      WHERE job_id = :EMP_BLOCK.JOB_ID;
  BEGIN
    OPEN lookup_job;
    FETCH lookup_job INTO :EMP_BLOCK.JOB_NAME;
    CLOSE lookup_job;
  END;
END;












TRIGGER "WHEN-NEW-FORM-INSTANCE" IS
BEGIN
  Execute_Query;
END "WHEN-NEW-FORM-INSTANCE";


TRIGGER "POST-QUERY" ON EMP_BLOCK IS
BEGIN
  EMP_PKG.fill_job_name;
END "POST-QUERY";

@FormController("EXAMPLE1")
public class Example1Form{

  @Inject EmpPkg emp_pkg;
  public static abstract class EmpPkg {
    public abstract void fill_job_name();
  }
 

  @Package
  public class EmpPkgBody extends EmpPkg {
    
    
    public void fill_job_name() {
      SqlCursor  lookup_job = cursorFor(
        "SELECT job_title FROM jobs WHERE
        job_id = :EMP_BLOCK.JOB_ID"
      );
      try {
        open(lookup_job);
        fetchInto(lookup_job) ,
        nameIn("EMP_BLOCK.JOB_NAME"));
      } finally {
        if (lookup_job.isOpen()) {
          close(lookup_job);
        }
      }
    }
    
    
  }
  
  
  @WhenNewFormInstance
  public void form_WHEN_NEW_FORM_INSTANCE() {
    executeQuery();
  }
  
  
  @PostQuery("EMP_BLOCK")
  public void block_EMP_BLOCK_POST_QUERY() {
    emp_pkg.fill_job_name();
  }
}

Oracle Forms to Java Migration FAQ

What is ORMIT™-Java?

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 proprietary libraries imitating the operation of Oracle Forms components based on Vaadin Framework

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

● Proprietary Developer Toolkit (IDE)

How automated is the conversion process from Oracle Forms to Java with ORMIT™-Java?

ORMIT™-Java (Re_Forms21) automates between 90% and 95% of real work inputs. Considerable Testing and other manual steps are required for each project.

Why is converting applications from Oracle Forms to Java cheaper than rewriting them?

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.

Why migrating from Forms to Java is safer than rewriting the applications?

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.

How will the application look after migration?

It can look exactly like the current Oracle Forms application or have a more modern and customized appearance using HTML5 and CSS. It can also be launched in the browser but without running the Java applet. The user interface will remain unchanged. The same user interface means business users don't need additional training.

What about maintaining business continuity?

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

Can the application work on mobile devices after conversion?

Yes it can with some development changes.

What are the technical elements of ORMIT™-Java?

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 (proprietary framework based on Vaadin)

Application layer - JEE Servlet (WAR) with proprietary libraries from Reforms21

Database layer - Oracle database and stored procedures PL / SQL

On which application servers do ORMIT™-Java applications run?

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.

What happens to the business logic?

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.

Banner

Oracle Forms to Java Automated Migration

Oracle Forms to Java Automated Migration

ORMIT™ - Java: Oracle Forms to Java Automated Migration Tool

ORMIT™ - Java Makes Business Sense

At least 50% cheaper than a manual migration

Automated migration will save you considerable time

ELIMINATE RISK

ORMIT™-JAVA makes sense

Gradual & Secure Migration

Same DB Structure & Business Logic

A Proprietary Eclipse IDE Development Environment

No End User Retraining

Technical aspects of the solution

User interface layer - Vaadin and HTML5

Application layer - Java Servlet as application controller

Database layer - Oracle database and PL/SQL stored procedure

New Java Web Architecture

Why Migrate from Forms to Java?

Technology

Manpower

Costs

Looking to migrate to open source React/Angular frameworks with ZERO proprietary libraries?

Code Compare before and after

PL/SQL

Java

Oracle Forms to Java Migration FAQ

Oracle Forms to Java: Meet the complete Automated ORMIT™ Migration Suite

Why RENAPS ?

ORMIT™ - Java: Oracle
Forms to Java Automated Migration Tool