Skip Headers
Oracle® Application Express Application Builder User's Guide
Release 4.1

Part Number E21674-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

Exporting an Application and Related Files

You export and import application definitions and all associated files using the Export, Workspace, Application, Websheet, Files, Themes, Plug-ins, Defaults, and Feedback tabs located at the top of the Export page.

Description of export_tabs.gif follows
Description of the illustration export_tabs.gif

It is not necessary to export an entire workspace unless you want to migrate workspace users or replicate shared component subscriptions in the target instance.

Once you export an application and any related files, you must import them into the target Oracle Application Express instance and then install them. As a general rule, always import the application first and then the related files. See "How to Move an Application to Another Development Instance".

Tip:

You can simplify the steps needed to deploy an application by creating a packaged application. See "How to Create a Packaged Application".

Topics:

Where Images, CSS, and Script Files Are Stored

In order to run, Oracle Application Express must have access to either Oracle HTTP Server and mod_plsql or the embedded PL/SQL gateway. Where images, CSS, and script files are stored depends upon the HTTP server you choose.

Topics:

Where Images, CSS, and Script Files Are Stored When Using Oracle HTTP Server

In an Oracle HTTP Server or Oracle Application Server configuration, images are stored on the file system in the location referenced by the alias /i/. To locate the images directory on the file system, review the following files and search for the text alias /i/:

  • Oracle9i HTTP Server Release 2—see the httpd.conf file.

  • Oracle HTTP Server distributed with Oracle Database 11g—see the dads.conf file.

  • Oracle Application Server 10g—see the marvel.conf file.

Specific examples for locating the text alias /i/ can be found in Oracle Application Express Installation Guide

Where Images, CSS, and Script Files Are Stored When Using the Embedded PL/SQL Gateway

When running Oracle Application Express with the embedded PL/SQL gateway, images are stored directly in the database within the Oracle XML DB repository. You can access images by using the WebDAV feature of Oracle XML DB or by using FTP. To learn more, see "Using Protocols to Access the Repository" in Oracle XML DB Developer's Guide.

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. On the Application Builder home page, click Export.

  2. On the Export page, click the Application tab.

  3. Under Choose Application, select the application to export.

  4. Under Export Application, specify the following:

    1. 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.

    2. Owner Override - Optionally select another owner. By default, the application is owned by the owner identified in the application attribute owner.

    3. 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.
    4. Debugging - Select one of the following:

      • Yes exports the application with debugging enabled.

      • No exports the application with debugging disabled.

    5. As of - Enables you to go back in time and export a previous version of your application. For example, you can use this option to export a version of your application that contain an object that is currently deleted. 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.

  5. Under Export Preferences, select Yes or No to include or exclude the following:

    To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark. See "About Field-Level Help".

  6. 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.

Exporting Application Components

You can export shared components or components of a page on the Component Export page. You can use this wizard to:

  • Export shared components or page components to another application or workspace

  • Back up a component before editing it

  • Create an export to function as a patch to another Oracle Application Express instance

To export shared components or page components:

  1. Navigate to the Component Export page:

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

    2. Select an application.

    3. Click Shared Components.

    4. From the Tasks list, click Export Application Components.

      The Component Export page appears.

  2. Click the following tabs and select the components to export:

  3. Click Add to Export.

  4. Click Next.

  5. On Components to Export:

    1. 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.

    2. Use the As of field to export a page 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 may 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.

    3. Click Export Components.

Exporting a Workspace

You can make an application available to other users by exporting a workspace. When you export a workspace, Oracle Application Express creates an ASCII text SQL script of users, any defined user groups and Team Development data.

To export a workspace:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. On the Export page, click the Workspace tab.

  3. Under Export Workspace:

    • Include Team Development - Select Yes to include Team Development data such as Features, Milestones, To Do, Bugs, Feedback, Links and News. Otherwise, select No.

    • 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. Click Export Workspace.

See Also:

"Managing Application Express Users" in Oracle Application Express Administration Guide

Exporting a Page in an Application

You can also export a specific page within an application by clicking the Export page icon on the Page Definition. When exporting a page, remember that exported pages can only be imported successfully if they have the same application ID and workspace ID.

To export a page in an application:

  1. Navigate to the appropriate Page Definition. See "Accessing the Page Definition".

  2. On the Page Definition, click the Export Page icon in the upper right corner.

    Description of export_pg_ico.gif follows
    Description of the illustration export_pg_ico.gif

    The Export Page Wizard appears.

  3. From Page, select the page to export.

  4. 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.

  5. Use the As of field to export a page 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 may 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.

  6. Click Export Page.

Exporting a Websheet

Use the Export Websheet utility to make a Websheet application available to other users.

To export a Websheet application:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. On the Export page, click the Websheet tab.

  3. For Websheet Application, select the Websheet to export and click Set Application.

  4. Follow on screen instructions.

Exporting Cascading Style Sheets

Use the Export Cascading Style Sheets utility to export uploaded cascading style sheets. Note that you can use this utility to export only uploaded cascading style sheets.

To export related cascading style sheets:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. On the Export page, click CSS.

  3. On the Export Cascading Style Sheets page, select the following:

    1. Stylesheets - Select the cascading style sheets to export.

    2. 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.

    3. Click Export Style Sheets.

Exporting Images

Use the Export Images utility to export uploaded images. When you export images using this utility, the images are converted to a text document. Note that you can use this utility to export only uploaded images.

To export upload images:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. On the Export page, click Images.

  3. On the Export Images page, select the following:

    1. Export Images in Application - Select an application from which to export images.

      Be aware that selecting Workspace Images only exports those images in your repository that are not associated with a specific application. If all of your images are associated with specific applications, then the workspace image export file will be empty.

    2. 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. Click Export Images.

Exporting Static Files

Use the Export Static Files utility to export static files you have imported. Note that you can use this utility to export only uploaded static files.

To export related static files:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. On the Export page, click Files.

  3. On Export Static Files page, select the following:

    1. Static Files - Select the files to export.

    2. 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.

    3. Click Export File(s).

About Importing into Another Oracle Application Express Instance

Note that you cannot use the Web interface described in this section to import exported static files into another Oracle Application Express instance. To import exported static files into another Oracle Application Express instance, use SQL*Plus while connected to the database. Note that you must export from and to a workspace having the same name and workspace ID.

Exporting Themes

Use the Export Theme utility to export themes from one Oracle Application Express development instance to a file.

Exporting a Theme from the Export Page

To export an application theme from the Export page:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. Click the Themes tab at the top of the page.

  3. On the Export Application Theme page, select the following:

    1. Export Theme - Select the theme to export.

    2. 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.

    3. Click Export Theme.

Exporting a Theme from the Themes Page

To export an application theme from the Themes page:

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

  2. Select an application.

  3. On the Application home page, click Shared Components.

  4. Under User Interface, select Themes.

    The Themes page appears.

  5. On the Tasks list, click Export Theme.

    The Export page appears.

  6. On the Export Theme page, select the following:

    1. Export Theme - Select the theme to export.

    2. 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.

    3. Click Export Theme.

Exporting Plug-ins

Use the Export Plug-in utility to export plug-ins from one Oracle Application Express development instance to a file.

To export a Plug-in from the Export page:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. Click the Plug-ins tab at the top of the page.

  3. On the Export Plug-in page, select the following:

    1. Export Plug-in - Select the plug-in to export.

    2. 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.

    3. Click Export Plug-in.

Exporting Script Files

You can transfer selected scripts from your current Script Repository to a Script Repository in a different Workspace by using the Export and Import tasks.

To export script files:

  1. On the Workspace home page, click the SQL Workshop icon.

  2. Click SQL Scripts.

  3. On the Tasks list, click Export.

  4. Select the appropriate script files and click Add to Export.

  5. Review the file name and click Export All.

    Select the Remove check box to remove the script.

See Also:

"Using SQL Scripts" in Oracle Application Express SQL Workshop Guide

Exporting User Interface Defaults

Exporting User Interface Defaults is useful when you plan to develop on a target system. User Interface Defaults are divided into two categories, the Table Dictionary, and the Attribute Dictionary.

  • The Table Dictionary consists is specific to tables and columns within a selected schema. These defaults are used over those defined in the Attribute Dictionary.

  • The Attribute Dictionary contains a set of attributes about a column that is used in creating forms and reports. The definitions are matched by column name and a particular definition can be shared among several columns by using synonyms.

When you export User Interface Defaults, all User Interface Defaults for the selected dictionary and schema are exported to a single SQL Command script. When prompted, save this file to your hard drive. The file contains an API call to create table hints by making calls to the application PL/SQL API. You can use this file to import User Interface Defaults to another database and Oracle Application Express instance.

See Also:

"Importing User Interface Defaults" and "Managing User Interface Defaults" in Oracle Application Express SQL Workshop Guide.

Exporting User Interface Defaults from the Export Page

To export User Interface Defaults from the Export page:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. On the Export page, click User Interface Defaults.

  3. On the Export User Interface Defaults - Table Dictionary page, select the following:

    1. Schema - Select the schema that owns the table associated with the User Interface Defaults.

    2. 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.

    3. Click Export.

  4. To export Attribute Dictionary, click Attribute Dictionary tab.

  5. Click Export.

Exporting User Interface Defaults from the User Interface Defaults Page

To export User Interface Defaults from the User Interface Defaults page:

  1. On the Workspace home page, click the SQL Workshop icon.

  2. Click Utilities.

  3. Click User Interface Defaults.

    The User Interface Defaults page appears.

  4. Select the dictionary you want to export:

    • Manage Table Dictionary - select this button to export specific tables and columns within a selected schema.

    • Manage Attribute Dictionary - select this button to export a set of column attributes used to create forms and reports.

  5. Under Tasks, click Export link.

  6. On the Table Dictionary page, select the file format:

    • 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.

  7. Click Export.

Exporting Feedback

Use the Export Feedback utility to synchronize feedback from a production or test system to the development system. The development system is identified by using the workspace setting Feedback Synchronization Source Identifier which is set on the Edit Workspace Information page. If exporting from a development system, the export process has an additional attribute called Deployment System where you specify to which deployment system, production or test, you want to synchronize the updated feedback to.

To export Feedback:

  1. Navigate to the Export page:

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

    2. On the Application Builder home page, click Export.

  2. On the Export page, click the Feedback tab.

  3. For Export Feedback:

    • Changes Since - select the date of the oldest feedback to export. All feedback from this selected date until the current date is exported.

    • File Format - select the format of the export file.

  4. Click Export.

  5. Follow on screen instructions.