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 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)

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

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

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

Application layer - JEE Servlet (WAR)

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.

How hard is it to maintain the code?

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.

Do you recommend deploying the Java application to the cloud?

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.