|Oracle® Application Express Application Migration Guide
Part Number E21675-02
|PDF · Mobi · ePub|
Oracle Application Express Application Migration Workshop (Application Migrations) enables you to migrate a Microsoft Access application or convert an Oracle Forms application to an Oracle Application Express application.
This section describes provides a general description of the steps needed to migrate applications from Microsoft Access or Oracle Forms to Oracle Application Express.
You begin the migration process by exporting your Microsoft Access metadata using the Exporter tool with Oracle SQL Developer Migration Workbench. After that initial step, you use Application Migration to review the retrieved objects and resolve any issues regarding invalid objects. As the final step, you have the option of generating either an application based on valid forms and reports or a maintenance application based on valid tables and views.
Once the application is generated, you can take advantage of all the functionality in Oracle Application Express to further develop and enhance the migrated application.
Topics in this section include:
Before you begin the migration process, verify that your system meets these requirements:
Oracle Application Express version 3.0 or later
You must install Oracle Application Express 3.0 or later. You use the Application Migration feature within Oracle Application Express to download the Exporter tool as well as to migrate Microsoft Access forms and reports to Oracle Application Express.
Oracle SQL Developer 2.1 or later (available in English only)
You must install Oracle SQL Developer version 2.1 or later. You use the Migration Workbench extension to migrate the Microsoft Access schema and data to Oracle.
Exporter tool version 10.2.0.2.5 or later (available in English only)
You can install the Exporter tool using the Download Exporter link within Oracle Application Express. For instructions, see "Step 1: Export Microsoft Access Metadata".
If you are using Oracle SQL Developer version 2.1 or later, you can access the Exporter tool directly from the Migration menu.
Your local system must have Microsoft Access installed, and it must be installed where the Exporter tool and .
mdb file reside.
Microsoft Data Access Components (MDAC)
Your local system should have the latest version of Microsoft Data Access Components (MDAC) installed. You can download the latest version from the Microsoft Web site.
Your local system must have a printer installed so that a report can be opened in design view. This is a requirement for exporting your Reports information from an .
.mdb file before you export your database. Follow the instructions in the next section.
Using Microsoft Access, you should analyze your .
mdb file before you export your database. Performing these steps will minimize errors in the migration.
In Microsoft Access, analyze the objects in your .
From the Microsoft Access menu bar, select Tools, Analyze, and then Documenter.
Select the All Object Types tab, and then click the Select All button to select all the objects within the application for analysis.
Remove or resolve any erroneous objects reported by the Documenter.
Ensure the application contains no missing references:
In Microsoft Access, launch the design IDE (press Alt+F11 keys).
From the menu bar, select Tools and then References.
Remove or resolve any missing references.
Ensure the application compiles successfully:
From the menu bar in the IDE view, select Debug and then Compile.
Resolve any reported errors.
Perform a compact and repair on the database:
From the menu bar in Microsoft Access, select Tools, Database Utilities, and then Compact and Repair Database.
Ensure that all linked tables are valid links:
From the menu bar in Microsoft Access, select Tools, Database Utilities, and then Linked Table Manager.
Verify that all links are up-to-date and pointing to an existing .
mdb file that is not read-only.
In addition to Oracle support, you can post questions on the Database and Applications Migrations forum:
You begin the process by converting Oracle Forms metadata to Extensible Markup Language (XML). Then, you create a conversion project within Oracle Application Express. Once you have reviewed and edited the application metadata within the project, you generate an Oracle Application Express application. Then, you can customize your application and change application attributes or add new pages within Application Builder.
Topics in this section include:
Before you begin the conversion process, you must:
Install Oracle Application Express version 3.2 or later
You must install Oracle Application Express 3.2 or later to convert an Oracle Forms application to Oracle Application Express.
Install Oracle9i Oracle Developer Suite or later
You must install Oracle Developer Suite to convert Oracle Forms applications and Oracle Reports to XML format. Specifically, you need:
Oracle Forms Builder
You must have Oracle Forms Builder installed to access the
Forms2XML conversion tool and the File Conversion utility for converting Oracle Forms application files.
Oracle Reports Builder
You must have Oracle Reports installed, to convert Oracle Reports (including, binary (.
REX), and .
JSP) to XML format.
Convert Oracle Forms Metadata
To start the conversion process, you convert:
Oracle Forms FormModule (.
FMB), ObjectLibrary .
OLB), or MenuModule (.
MMB) files to XML format using the Forms to XML conversion tool,
Oracle Reports (including, binary (.
REX), and .
JSP) to XML format using the File Conversion option in Reports Builder
PL/SQL library .
PLL files to .
PLD text files using the File Conversion option in Oracle Forms Builder
Associate Oracle Forms Schema with Oracle Application Express workspace
You must ensure the schema associated with your Oracle Application Express workspace contains the database objects for your Oracle Forms application. Further information on Oracle Application Express workspaces and associating schemas is provided in subsequent chapters.
See Also:"Converting an Oracle Forms Application"
In addition to Oracle support, you can post questions on the Oracle Application Express Forum: