Exporting an Application

When you export an application, Oracle Application Express generates a text file containing PL/SQL API calls.

To export an application:

1. Navigate to the Export page:

   1. On the Workspace home page, click the Application Builder icon.

   2. Select an application.

   3. On the Application home page, click Export/Import.

   4. On the Export/Import page, click Export and then click Next.

2. From Application, select the application to be exported.

3. From File Format, select how rows in the export file will be formatted:

   • Choose UNIX to have the resulting file contain rows delimited by line feeds.

   • Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.

4. From Owner Override, optionally select another owner. By default, the application is owned by the owner identified in the application attribute owner.

5. From Build Status Override, select one of the following:

   • Run Application Only - Developers can only run an application

   • Run and Build Application - Developers can both run and edit an application

   Selecting Run Application Only is an effective way to protect an application from modifications from other developers.

   
   

   Tip: If you select Run Application Only, you cannot set the argument p_trace to Yes. See "Using Build Options to Control Configuration". Also, the only way to change this setting after you import the application, is to log in to Oracle Application Express Administration Services. See "Changing Application Build Status Set During Deployment" in Oracle Application Express Administration Guide.

   
   

6. From Debugging, select one of the following:

   • Yes exports the application with debugging enabled.

   • No exports the application with debugging disabled.

7. From Exporting Supporting Object Definitions, specify whether to export supporting object definitions with your application. Available options include: See "How to Create a Packaged Application".

8. From Export Comments, specify whether to export comments for this application. See "Adding Developer Comments".

9. Use the As of field to export your application as it was previously defined. Specify the number of minutes in the field provided.

   This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases can have the same UNDO_RETENTION parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo tablespace, forcing older data to be archived.

10. Click Export Application.

In addition to exporting the actual application file, you may also need to export other related files such as cascading style sheets, images, and script files.