Page tree
Skip to end of metadata
Go to start of metadata


Morphis Transformer is a product designed to extract original code structure and semantics using it to generate models which can be either converted, migrated or transformed into new languages or new models. Transformer can assist you either in the evolution into a new language (migration) or in the readjustment of your code components or structure (remediation).

  • Converts Oracle Forms Modules into 100% pure Java code and HTML or Flex
  • Produces up to 100% of the converted applications final code
  • Produces database independent code

How to Use It

1.1.  Starting the Transformer Wizard

Run the Forms2JavaTransformer.exe application.

The conversion wizard gathers all the information required to build an application based on the modules you select.

1.2.  Choosing the Output Settings

Choose the output settings that you want for the current conversion.

If you are generating an application for the first time choose create a project in a new solution.

When converting a fragment of an already converted application or when re-generating only some forms, you should select the option to generate the code into an existing directory and point to the previously created directory.



During the conversion process, the settings for the current conversion are stored in the project workspace directory. When you select a directory, in this page, where a previous conversion has been executed, those settings are loaded. This allows repeated conversions of the same set of modules, or reusing conversion settings on different sets of modules.

Note: Converting the same module multiple times will overwrite previously generated code. If you want to generate incrementally, a good practice is to create the solution and project on the first generation, then copy the Forms2Net workspace directory to a project subdirectory, e.g. generated, and perform subsequent conversions into that directory. You then copy the new generated code into the project directory. This procedure allows you to convert modules that had already been converted without losing any changes that have been made on the generated code.

1.3.  Selecting application files to convert

This page is used for the definition of the conversion scope. The following data should be supplied:

  • Application Name –Name that will identify the converted application;
  • Files to convert –Files containing the Oracle Forms modules to convert;
  • License File –File that allows the conversion of forms for which a license was purchased.

1.4.  Defining the conversion settings

The Settings page allows the definition of settings that influence the way code is generated for the forms. This includes extra information about the database schema underlying the application.



  • From Oracle Forms Version – Information about the original Oracle Form Builder version. The available options are Oracle 6i, Oracle 9i and Oracle 10g;
  • Java platform – Define here the target type for the migrated application. The available options are Java2EE XPL Application and Java2EE Flex Application;
  • Oracle Forms Codepage in use – Define here the codepage in use by Oracle Form Builder. By default, the codepage in use by windows is selected. If your Oracle Form Builder is using a different codepage, please select it here. Note that the codepage in use by Oracle Forms Builder is specified in NLS_LANG value set at the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEx” (where “x” is the unique number identifying the Oracle home).
  • Coordinate System, Real Unit – Information about the settings of original form measurement units. This is necessary so that the Transformer can extract this information correctly. The available options are the same as the ones available in Oracle Forms Builder;
  • Database Schema File – Define the XML file containing the schema of the relevant Oracle database. This file is produced by the Db Schema Extractor;
  • Generate Commented Function Code – When checked, the converter generates the converted code inside methods of common modules (libraries) as comments. Function methods will also include a default return value according to its return type. This feature allows an easy compilation of the converted forms in the early phases of migration. Since libraries may include methods that are not relevant for the current forms under migration, or even unused methods, this allows developers to be concerned only on relevant methods. Developers will uncomment methods incrementally, during the whole migration process;
  • Do NOT overwrite common files – When checked, the files in the common folder will not be generated. This option is usually used so as to not override the changes already made to the files in this folder. For example, when Transformer is used for reconverting an Oracle Forms application and there were some changes or customizations made to the files in the common folder.


1.5.  Executing the conversion

After defining the scope and the settings for the conversion, the wizard is ready to perform the conversion and produce the Java code.



The conversion process may take some time to execute, depending on the size and complexity of the modules.


1.6.  Check the errors

The final wizard page presents the error count and links to the error log files that may have occurred during the conversion.



Morphis recommends that log files related to conversion errors for which the developer cannot find any solution, should be sent to us. Please include explanatory comments for further processing by the Morphis support team.



  • No labels