Oracle Forms Developer and OracleAS Forms Services Migrating Forms Applications from Forms 6 10g (9.0.4) Part Number B10469-01 |
|
Oracle Forms provides a tool that updates obsolete usage in your PL/SQL code in order to migrate your Forms 6i applications to Oracle Forms. The tool issues warnings when it cannot make the required changes automatically. This tool has a command line and a wizard version.
This chapter contains the following sections:
Go to http://otn.oracle.com for the latest version of the tool.
The Oracle Forms Migration Assistant does the following for all Forms module types (including object libraries and PL/SQL libraries):
You run the Oracle Forms Migration Assistant in batch mode. You can re-enter the utility as needed to run the migration process on a Forms application more than once.
By editing the converter.properties file, you can set options before you start the batch migration. By editing the search_replace.properties file you can specify the strings that the Oracle Forms Migration Assistant will search for and replace, and edit the warnings that are issued when an obsolete Built-ins is encountered.
The tool creates a log file so that you can navigate to problem areas in the application and make modifications manually.
The Forms Migration Assistant allows you either to write all log information into a single log file or span mutiple 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 since the type of log file was specified in the converter.properties. The Forms Migration Assistant generates two log files: test_fmb.log and test_mmb.log.
To change migration options, edit the converter.properties file in a text editor. You can set the following migration options:
The search_replace.properties file contains the strings that the Oracle Forms Migration Assistant will search for and replace. It also contains a list of obsolete Built-ins that will generate warnings.
You can edit this file to add your own search-and-replace strings, as follows:
SearchString|ReplaceString
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
obsoleteCallBuiltin
DataParameterWithReports
You can add more Built-in warnings to an existing class, or create new classes and warnings:
You should upgrade the common modules (such as OLB files) and Libraries (PLL files) that a Form relies upon and ensure that these are available in the FORMS90_PATH, before running the migration assistant.
Note: The forms90\rp2rro.pll and forms90\EnableDisableItem.pll files should be in the FORMS90_PATH in order to convert RUN_PRODUCT to RUN_REPORT_OBJECT. |
ifplsqlconv90 mode=batch module=<modulename> log=<log>
f90plsqlconv mode=batch module=<modulename> log=<log>
You can also specify additional command line parameters, as described in Table 2-2, "Oracle Forms Migration Assistant Command Line Parameters":
Parameter | Description |
---|---|
modulename (required) |
Specifies the module to migrate. The modulename parameter can take only one value. See "About the Migration Assistant in Batch Mode" if you want to migrate more than one file at a time. |
log (optional) |
Specifies the log file to which the migration results are written. If not specified, the default values from the converter.properties file are used. |
Mode (optional) |
This option has two values (batch and wizard). Use mode=batch to run Converter in Batch mode. |
Information about the progress of the migration process is displayed on the screen. It is also saved to the log file that you specify in the converter.properties file. (To change migration options, see Editing the converter.properties File.)
Check the log file for information about required migration steps that the tool did not modify. Manually make these changes to your application.
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 NT, create a batch file (for example upgrade.bat) that contains the following:
for %%ff in (%1) do call ifplsqlconv90 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 f90plsqlconv.sh module=$ff done
Then run the shell script as follows:
upgrade.sh *.fmb
or
upgrade.sh foo*.mmb
To start the Migration Assistant in batch mode in Windows:
ifplsqlconv90 mode=batch module=<filename> log=<logname>
To start the Migration Assistant in batch mode in UNIX:
f90plsqlconv 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:
ifplsqlconv90 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".
You can run the wizard version of the Forms Migration Assitant and edit converter options.
To start the wizard version of the Forms Migration Assistant:
setenv FORMS90_PATH $Oracle_Home/forms90
or
f90plsqlconv mode=wizard in UNIX.
The Conversion Wizard Welcome dialog displays.
Note: For information about setting the search_replace.properties file, see "Editing the converter.properties File". |
You can set conversion options before running the wizard:
|
Copyright © 2003, 2003 Oracle Corporation. All Rights Reserved. |
|