2 Using the Oracle Forms Migration Assistant

Multiple Log Support

The Forms Migration Assistant allows you either to write all log information into a single log file or span multiple log files. If the Forms Migration Assistant spans multiple log files, the Forms Migration Assistant generates individual log files for each module that is processed.

You'll need to specify the directory in which the Forms Migration Assistant writes the log files. The name of the log file which is generated is modulename_moduletype.log.

For example, if you process a module by name, such as test.fmb, the name of the log file is test_fmb.log. If you select test.fmb and test.mmb for migration, the Forms Migration Wizard does not overwrite the log files. However, if you converted two modules test.fmb from two different directories, the log files will be overwritten. The Forms Migration Assistant generates two log files: test_fmb.log and test_mmb.log.

Adding Search-and-Replace Strings

You can edit this file to add your own search-and-replace strings, as follows:

1. Open the search_replace.properties file in a text editor.

2. Go to the end of the list of search-and replace strings.

3. Add a string to search for and replace using the following syntax:

   SearchString|ReplaceString
   
   

4. Save the search_replace.properties file.

Modifying Warnings for Obsolete Built-Ins

The warnings for Built-ins have the following syntax:

<class>.Message=<WarningMessage>
<class>.Warning1=<BuiltIn1>
<class>.Warning2=<BuiltIn2>
<class>.Warning3=<BuiltIn3>
etc.

For example, for the class obsoleteMenuParam, the warnings are coded as follows:

obsoleteMenuParam.Message=Menu Parameters are no longer supported, the parameter and usage of %s should be replaced using a Forms parameter or global variable.
obsoleteMenuParam.Warning1=MENU_PARAMETER
obsoleteMenuParam.Warning2=QUERY_PARAMETER
obsoleteMenuParam.Warning3=TERMINATE

<class> is a group of Built-ins that have a common warning. <WarningMessage> can contain one variable string (%s).

When the Oracle Forms Migration Assistant finds a Built-in for which a warning should be issued, it logs the warning and replaces the variable string (%s) with the Built-in name.

Classes that have already been created in the search_replace.properties file are:

• obsoleteItemTypeBuiltin

• obsoleteBuiltin

• obsoleteMenuParam

• obsoleteItemTypeConstantProp

• obsoleteConstantProp

• obsoleteConstant

• obsoleteHardCodedUserExit

• obsoleteComplexBuiltin

• DataParameterWithReports

• NoErrorOrWarningFromForms

You can add more Built-in warnings to an existing class, or create new classes and warnings:

1. Open the search_replace.properties file in a text editor.

2. Go to the end of the list of warning messages.

3. Add a warning to an existing class or create new classes and warnings using the syntax described above.

4. Save the search_replace.properties file.

   
   

   Note: Do not delete the last two commands in the search_replace.properties file.

   
   

About the Migration Assistant in Batch Mode

You can convert multiple applications by running the Forms Migration Assistant in batch mode from the command line. Batch mode is useful for converting multiple Forms applications. For example, on Windows, create a batch file (for example upgrade.bat) that contains the following:

for %%ff in (%1) do call frmplsqlconv module=%%ff

Then run the batch file as follows:

upgrade *.fmb

or

upgrade foo*.mmb

On UNIX, create a shell script (for example upgrade.sh) that contains the following:

for file in $*
do
   frmplsqlconv.sh module=$ff
done

Then run the shell script as follows:

upgrade.sh *.fmb

or

upgrade.sh foo*.mmb

Starting the Migration Assistant in Batch Mode

To start the Migration Assistant in batch mode in Windows: 

frmplsqlconv mode=batch module=<filename> log=<logname> 

To start the Migration Assistant in batch mode in UNIX: 

frmplsqlconv.sh  mode=batch module=<filename> log=<logname> 

where <filename> is the name of the file you want to convert, and <logname> is the name of the log file that will get generated.

In the following example:

frmplsqlconv mode=batch module=d:\temp\test.fmb log=d:\temp\test.log

Forms Migration Assistant will look for the file Òtest.fmbÓ in the d:\temp directory and will name the generated log file Òtest.logÓ and place it in the d:\temp directory. You can give the log file any name you want and specify any location you want. By default the log file is written in $ORACLE_HOME\bin. The module parameter can take only one value.

The output of the conversion is displayed on the screen. It is also saved to the default log file. Note that in batch mode, all converter options are taken from the converter.properties file. To change the converter options, see "Editing the converter.properties File".

Running the Wizard Version of the Forms Migration Assistant

You can run the wizard version of the Forms Migration Assistant and edit converter options.

To start the wizard version of the Forms Migration Assistant:  

1. On Windows systems, set the environment variable FORMS_PATH:

   SET FORMS_PATH=%ORACLE_HOME%\forms

   On UNIX systems, set the variable FORMS_PATH as in the example below:

   setenv FORMS_PATH $ORACLE_HOME/forms

2. In Windows, from the Start menu, select ORACLE_HOME | Forms Developer |Oracle Forms Migration Assistant (GUI Mode), or at the command line, start the conversion utility by entering: frmplsqlconv.bat mode=wizard.

   or

   in UNIX, enter frmplsqlconv.sh mode=wizard.

   The Conversion Wizard Welcome dialog displays.

   
   

   Note: You can get help by typing -h after the command, for example, frmplsqlconv -h.

   
   

3. Click Next.

4. In the Modules dialog, click the Add Module(s) button.

5. Select the modules that you want to convert.

6. Click Next.

7. In the Converter options dialog, enter the location and name of the log file that will be generated. A browse button is provided to assist in choosing a location.

8. If you have Forms that include embedded reports, fill in the remaining fields. Otherwise, you may ignore these fields.

9. For more information about the Reports fields, see Reports Developer Reference. For more information about advanced converter options, see the following section, "Setting Advanced Converter Options".

10. Click Next.

11. In the Finish dialog, you will see the modules you selected. Click Finish to start the conversion.

12. Progress displays in the Log window. (Log output is written to the log file name(s) that you specify in the Options dialog. See the following section for information about setting options.)

13. Check the log file(s) for information about required conversion steps that the tool did not modify. Manually make these changes to your application.