14 Deploying an Application

System Development Life Cycle Methodologies to Consider

The system development life cycle (SDLC) is the overall process of developing software using a series of defined steps. There are a number of SDLC models that work well for developing applications in Oracle Application Express.

The SDLC waterfall is probably the best known model. In this methodology, the development process is broken down into the following stages:

1. Project Planning

2. Requirements Definition

3. Design

4. Development

5. Integration and Testing

6. Installation and Acceptance

7. Maintenance

This methodology is referred to as a waterfall because the output from one stage is the input for the next stage. One of the primary problems with this approach is that it is assumed that all requirements can be established in advance. Unfortunately, requirements often change and evolve during the development process.

The Oracle Application Express development environment enables developers to take a more iterative approach to development. Unlike many other development environments, creating prototypes is easy. With Oracle Application Express, developers can:

• Use built-in wizards to quickly design an application user interface

• Make protoypes available to users and gather feedback

• Implement changes in real time, creating new prototypes instantly

Other methodologies that work well with Oracle Application Express include:

• Spiral - This approach is actually a series of short waterfall cycles. Each waterfall cycle yields new requirements and enables the development team to create a robust series of prototypes.

• Rapid application development (RAD) life cycle - This approach has a heavy emphasis on creating a prototype that closely resembles the final product. The prototype is an essential part of the requirements phase. One disadvantage of this model is that the emphasis on creating the prototype can cause scope creep; developers can lose sight of their initial goals in the attempt to create the perfect application.

Deployment Options to Consider

When you develop an application in Application Builder, you create the application within a specific workspace. Each workspace has a unique ID and name. A common scenario is to create the application in a development instance and then deploy it to a production instance.

During the deployment process, you must decide whether you want to use the existing application ID, the existing workspace, the existing database, the existing Oracle HTTP Server, or create new ones. Deployment options to consider include:

1. Create Application Express End Users. The simplest way to deploy an application is to create Application Express end users and then send the URL and login information to users. This approach works well for applications with a small and tolerant user population. See "About Publishing the Application URL" and "Managing Application Express Users" in Oracle Application Express Administration Guide.

2. Use the same workspace and same schema. Export and then import the application and install it using a different application ID. This approach works well when there are few changes to the underlying objects, but frequent changes to the application functionality.

3. Use a different workspace and same schema. Export and then import the application into a different workspace. This is an effective way to prevent a production application from being modified by developers.

4. Use a different workspace and different schema. Export and then import the application into a different workspace and install it so that it uses a different schema. This new schema will need to have the database objects required by your application. See "About the Database Object Dependencies Report".

5. Use a different database with all its variations. Export and then import the application into a different Oracle Application Express instance and install it using a different schema and database.

Deciding Whether to Copy a Workspace

Deciding whether to copy an existing workspace is a matter of preference. Keep in mind that the production version must have access to all the appropriate objects. For example, you might want to copy a workspace in the following situations:

• When the application subscribes to other Oracle Application Express objects within the workspace.

• When the application relies on Oracle Application Express authentication. Copying the workspace automatically migrates all the required user data.

Deciding Whether to Copy a Database

When deciding whether to copy the database, remember that the schema against which the application runs must have access to the same objects as the development instance. The actual name of the schema is unimportant. You can change it during the import process.

About the Application ID

It is not necessary to have matching application IDs for a development version and production version of an application. In fact, as a best practice never hard code the application ID into your application. Instead, use the application alias (defined on the Edit Definition page), or use a built-in substitution string (such as APP_ID and APP_ALIAS). Using a substitution string is the better approach because it enables you to change the application ID without affecting any application functionality.

Deciding to Install a New HTTP Server

In order to run, Oracle Application Express must have access to either the embedded PL/SQL gateway or Oracle HTTP Server and mod_plsql. Installing a new HTTP server is another way to separate a development version and production version of an application. To learn more about HTTP server configuration options, see "Choosing a HTTP Server" in the appropriate installation guide for your operating environment. See "Related Documents".

About Managing Database Objects

Before you export an application and the appropriate related files, you must determine if you also need to migrate the database objects referenced by the application. If you are unsure of which database objects to move, review the Database Object Dependencies report.

If the target schema is different from the schema used in the development environment, you need to migrate the database objects referenced by the application. In many cases, this process can be as simple as using Oracle database export and import utilities to copy the application schema from the development environment to target instance. The following are two common scenarios where this approach does not work:

• When the object development schema refers to tablespaces to which the target instance schema does not have access

• When the development instance schema has sample data that you do not want to migrate to the target instance schema

If a database administrator or an Oracle Application Express administrator is the person responsible for exporting Oracle Application Express applications, be sure to clearly communicate if he or she:

• Should include all data when exporting your application

• Should not include data from specific tables you identify

How a Packaged Application Simplifies Deployment

From a user's perspective, importing and installing an application is a complicated process. First, you create the target database objects and seed data. Second, you import and install the application definition and all related files, including images, themes, and any other required static files.

Creating a packaged application using the Supporting Objects utility greatly simplifies this process. Instead of performing numerous steps to create the database objects and then import and install the application and all supporting files, you can define the supporting objects so that the application and supporting files can be migrated in a few easy steps.

After users import and install the application definition, a wizard guides them through a few simple configuration steps. Then, the wizard asks whether to install the supporting application objects. Users have the option of installing the supporting application objects then or doing it later.

From a developer's perspective, this feature has a number of advantages:

• Ensures that the supporting objects are created in the correct order.

• Provides users with an automated process for deploying an application quickly using very few steps.

• Gives users the option to install supporting application objects when they import and install the application definition or at a later time. See "Installing Supporting Objects".

• Enables users and developers with a convenient method for removing the application definition, supporting files, and all database objects. See "Deinstalling Supporting Objects".

• Enables users and developers with an easy way to upgrade a previously released packaged application. See "Upgrading a Packaged Application".

Plus, you can also take advantage of the Deinstall and Install features to quickly edit the underlying database objects that support an application. For example, you can deinstall and remove all database objects, edit the underlying database object creation scripts, and reinstall to create the redefined application objects.

Creating a Packaged Application

To create a packaged application, you must create installation scripts that define your application's supporting objects (including database objects, images, and seed data) and any preinstallation validations. You define these objects and the installation and deinstallation scripts and the messages that display when the user installs or deinstalls on the Supporting Objects page.

This section contains the following topics:

• Accessing the Supporting Objects Page

• About the Supporting Objects Page

About the Supporting Objects Page

The top of the Supporting Objects page displays the application name and indicates current selections for the following: Check for Objects, Verify System Privileges, Required Free KB, Prompt for License, Substitutions, Build Options, Validations, Installation Scripts, Upgrade Scripts, Deinstallation Script, and Include in Export.

Description of the illustration sup_object_sum.gif

The rest of the page is divided into four categories.

Installation

Use the links under Installation to define the following types of information:

• Prerequisites. Defines built-in checks required before installing the application, including required free disk space, required system privileges, and schema object restrictions.

• Application substitution strings. Lists static substitution strings defined for the application. You can define static substitution strings for phrases or labels that occur in many places within an application. See "Substitutions".

  When packaging an application, you can include prompts for substitution strings which users can specify when they install the packaged application.

• Build Options. Lists build options defined for this application. You can use build options to conditionally display specific functionality within an application. See "Using Build Options to Control Configuration" and "Exporting Build Options or Build Option Status".

  When packaging an application, you can include prompts for specific build options which display when the application is installed.

• Pre-installation Validations. Lists validations defined for the packaged application. Similar to normal page validations, these validations prevent a user from installing database objects if the user-defined conditions are not satisfied. To create a new validation, click Create and follow the on-screen instructions.

• Installation Scripts. Enables a you to define multiple installation scripts that install supporting objects for the application. To create a new script, click Create and follow the on-screen instructions. To edit an existing script, click the Edit icon.

Message

Use the links under Message to define message to display when the user installs or deinstalls the application. Supported HTML tags include <b>, <i>, <u>, <p>, <br>, <hr>, <ul>, <ol>, <li>, and <pre>. Available message types include:

• Welcome

• License

• Application Substitutions

• Build Options

• Validations

• Confirmation

• Post Installation

• Upgrade

• Deinstallation

Note that when these messages display, only a limited set of HTML tags are recognized in order to prevent a cross site-scripting (XSS) attack. See "Understanding Cross-Site Scripting Protection".

Upgrade

Click Upgrade scripts to define scripts to upgrade database objects, images, and seed data when upgrading an existing application. See "Upgrading a Packaged Application".

Deinstallation

Click Deinstallation script to define a script to drop database objects and static files created by the installation scripts. To edit an existing script, click the Edit icon.

Adding Installation Scripts for an Image, Cascading Style Sheet, or Static File

You can create installation scripts for images, cascading style sheets, and static files you have previously uploaded for your application or workspace on the Installation Scripts page. Oracle Application Express uses the name of the file you select as the name for each new script. It also adds corresponding API calls to the end of the deinstallation script (or creates one if one does not already exist), which removes the selected files when the application's supporting objects are deinstalled.

To create installation scripts for an image, cascading style sheet, or static file:

1. Navigate to the Supporting Objects page:

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

   2. Select the application.

      The Application home page appears.

   3. Click Supporting Objects.

      The Supporting Objects page appears.

2. Under Installation, click Installation scripts.

   The Installation Scripts page appears.

3. Click Create.

4. At the bottom of the page, click Create Script to Install Files.

   A list of available cascading style sheets, images, and static files appears.

5. Select the files to include with your packaged application and click Create Script.

Adding an Access Control List to a Packaged Application

You can control access to an application, individual pages, or page components by creating an access control list.

To add an access control list of a packaged application:

1. Create an access control list. See "Controlling Access to Applications, Pages, and Page Components".

2. Navigate to the Supporting Objects page:

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

   2. Select the application.

      The Application home page appears.

   3. Click Supporting Objects.

      The Supporting Objects page appears.

3. Under Installation, click Installation scripts.

   The Installation Scripts page appears.

4. Click Create.

5. At the bottom of the page, click Create Scripts for Access Control Tables.

   If Access Control tables are defined, the Create Script page displays the tables to be included.

6. Click Create Script.

Installing Supporting Objects

After you edit your supporting objects and create the appropriate scripts, you can run your installation scripts by clicking Install Supporting Objects on the Tasks list.

End users can also use this feature if they elect to not install the packaged application (or supporting objects) after they import and install the application definition.

To install supporting objects:

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

2. Select the application.

3. Click Supporting Objects.

   The Supporting Objects page appears.

4. Click the Install Supporting Objects on the Tasks list.

5. To view details about the installation script before running it, click Preview Installation Script.

   The Preview Scripts page appears listing summary information, prerequisites, and the actual scripts to be run.

6. To exit the Preview Scripts page and continue, click Close.

7. From Install Supporting Objects, click Yes and click Next.

8. Follow the on-screen instructions.

Deleting Supporting Objects Scripts, Messages, and Installation Options

You can delete the metadata that defines supporting object scripts, messages, and installation options associated with a packaged application by clicking Remove Supporting Object Installation on the Tasks list on the Supporting Objects page.

To delete the metadata that defines supporting object scripts, messages, and installation options:

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

2. Select an application.

3. Click Supporting Objects.

   The Supporting Objects page appears.

4. On the Tasks list on the right side of the page, click Remove Supporting Object Installation.

5. Follow the on-screen instructions.

Upgrading a Packaged Application

You can define scripts to upgrade a previously published application on the Upgrade page.

This section contains the following topics:

• Defining an Upgrade Script

• Upgrading a Packaged Application

Deinstalling Supporting Objects

Once you create or install a packaged application, you can deinstall it by either:

• Clicking the Deinstall Supporting Objects on the Supporting Objects page

• Clicking Delete this Application on the Application home page

When you deinstall an application, you have the option of removing the current application definition and running the deinstallation script defined in the Supporting Objects.

To deinstall a packaged application:

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

2. Select the application.

3. Click Supporting Objects.

   The Supporting Objects page appears.

4. Click Deinstall Supporting Objects.

5. Select a deinstallation option:

   • Remove Application Definition removes the current application definition.

   • Deinstall Database Objects runs the deinstallation script defined in the deployment attributes for this application.

6. Follow the on-screen instructions.

Viewing an Install Summary

You can view a log of recent installation and deinstallation by clicking View Install Summary on the Tasks list on the Supporting Objects page. Note that this log only displays results from the most recent installation or deinstallation that occurred during the current Application Express session.

To view the Install Summary:

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

2. Select the application.

3. Click Supporting Objects.

   The Supporting Objects page appears.

4. On the Tasks list on the right side of the page, click View Install Summary.

   A Summary page appears.

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.

Exporting Workspace Users

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

To export workspace users:

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. On the Export page, click the Workspace Users tab.

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

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 be exported:

   • Components displays shared application components and entire pages. Use the navigation bar at the top of the page to search for components. See "Working with Shared Components" and "Exporting Build Options or Build Option Status".

   • Components by Page lists components of the selected page. Navigate to a specific page by making a selection from the Page. Click Check All to select all components.

   • Application Attributes displays application attributes. Press CTRL or SHIFT to select multiple attributes. See "About the Edit Definition Page".

   • Build Option Status displays available build options. Use this page to turn build options on and off. See "Exporting Build Options or Build Option Status".

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 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 sucessfully 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 a Page Definition".

2. On the Page Definition, you can export a page in two ways:

   • Click the Export Page icon, the down arrow in the upper right corner.

   • From the View list, select Export and click Go.

   The Export Page Wizard appears.

3. From Page, select the page to be exported.

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 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. 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. Click the CSS tab at the top of the page.

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. 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. Click the Images tab at the top of the page.

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. 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. Click the Files tab at the top of the page.

3. On Export Static Files, select the following:

   1. Static Files - Select the files to be exported.

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

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.

Exporting Themes

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

Exporting User Interface Defaults

Exporting User Interface Defaults is useful when you plan to develop on a target system.

When you export User Interface Defaults, all User Interface Defaults for the selected 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.

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.

This section contains the following topics:

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

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

Importing an Application or Page

To import an Application or Page Export into a target Oracle Application Express instance:

1. Navigate to the Import 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 Import and then click Next.

2. For Specify File, specify the following:

   1. Import file - Click Browse and navigate to the file.

   2. File Type - Select Application, Page, or Component Export.

   3. Verify that File Character Set is correct.

   4. Click Next.

   Once you import a file, you have the option to install it.

3. To install an imported file, click Next.

   The Install Application wizard appears.

4. In the Install Application wizard, specify the following:

   1. Parsing Schema - Select a schema.

      This is the schema against which all of the application's SQL and PL/SQL will be parsed.

   2. Build Status - Select one of the following:

      • Run Application Only - Users can only run an application.

      • Run and Build Application - Users can run an application and 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, 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.

   3. Install As Application - Select one of the following:

      • Auto Assign New Application ID

      • Reuse Application ID From Export File

      • Change Application ID

      Use these options to avoid application ID conflicts. These options come in handy when you have two versions of the same application in the same instance. For example, you might be migrating an application to a production instance and still need to maintain the development version.

   4. Click Install.

      If you are installing a packaged application (that is, one for which you have defined Supporting Objects), the installer prompts you to install the packaged installation scripts. Follow the on-screen instructions.

Importing Cascading Style Sheets

After you import an application into the target Oracle Application Express instance, you must import all related files.

To import a CSS Export file:

1. Navigate to the Import 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 Import and then click Next.

2. For Specify File, select the following:

   1. Import file - Click Browse and navigate to the file.

   2. File Type - Select CSS Export.

   3. File Character Set - Verify that File Character Set is correct.

   4. Click Next.

   Once you import a file, you have the option to install it.

3. To install an imported file, click Next.

4. Click Install CSS.

Importing Static Files

After you import an application into the target Oracle Application Express instance, you must import all related files.

To import a static file:

1. Navigate to the Import 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 Import and click Next.

2. For Specify File, select the following:

   1. Import file - Click Browse and navigate to the file.

   2. File Type - Select File Export.

   3. File Character Set - Verify that File Character Set is correct.

   4. Click Next.

   Once you import a file, you have the option to install it.

3. To install an imported file, click Next.

4. Click Install Static Files.

Importing Images

After you import an application into the target Oracle Application Express instance, you must import all related files.

To import an Image Export file:

1. Navigate to the Import 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 Import and click Next.

2. On Import Definition, select the following:

   1. Import file - Click Browse and navigate to the file.

   2. File Type - Select Image Export.

   3. File Character Set - Verify that File Character Set is correct.

   4. Click Next.

   Once you import a file, you have the option to install it.

3. To install an imported file, click Next.

4. Click Install Image.

Importing Themes

After you import an application into the target Oracle Application Express instance, you must import all related files.

To import a Theme Export file:

1. Navigate to the Import 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 Import and click Next.

2. On Import Definition, select the following:

   1. Import file - Click Browse and navigate to the file.

   2. File Type - Select Theme Export.

   3. File Character Set - Verify that File Character Set is correct.

   4. Click Next.

   Once you import a file, you have the option to install it.

3. To install an imported file, click Next.

4. Click Install Theme.

Importing User Interface Defaults

User Interface Defaults enables you to assign default user interface properties to a table, column, or view within a specified schema.

After you import an application into the target Oracle Application Express instance, you must import all related files.

To import User Interface Defaults:

1. Navigate to the Import 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 Import and then click Next.

2. Select an application.

3. On Import Definition, select the following:

   1. Import file - Click Browse and navigate to the file.

   2. File Type - Select User Interface Defaults.

   3. File Character Set - Verify that File Character Set is correct.

   4. Click Next.

   Once you import a file, you have the option to install it.

4. To install an imported file, click Next.

5. Click Install User Interface Defaults.

Accessing the Export Repository

When you import an application and any related files into a target Oracle Application Express instance, the files are stored in the Export Repository.

To access the Export Repository:

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

2. Select an application.

3. On the Tasks list, click Manage Export Repository.

   The Export Repository appears.

Installing an Application Export from the Export Repository

After you import an application export into an Oracle Application Express instance, you must install it before it can become active or available in Application Builder.

To install an application export from the Export Repository:

1. Navigate to the Export Repository:

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

   2. Select an application.

   3. On the Tasks list, click Manage Export Repository.

      The Export Repository appears.

2. Select an application export and click Install in the Action column.

3. Specify the following:

   1. Parsing Schema - Select a schema.

      This is the schema against which all of the application's SQL and PL/SQL will be parsed.

   2. Build Status - Select one of the following:

      • Run Application Only

      • Run and Build Application

      Select Run Application Only to run the application in the target instance and make it inaccessible to developers.

      Tip:

      If you select Run Application Only, 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" Oracle Application Express Administration Guide.

   3. Install As Application - Select one of the following:

      • Reuse Application ID from Export File

      • Auto Assign New Application ID

      • Change Application ID

      Use these options to avoid application ID conflicts. Use these options when you must have two versions of the same application in the same instance. For example, you might be migrating an application to a production instance and still need to maintain the development version.

   4. Click Install.

Installing Other Files from the Export Repository

After you import files into an Oracle Application Express instance, you must install them before they can become active or available in Application Builder.

To install files stored in the Export Repository:

1. Navigate to the Export Repository.

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

   2. Select an application.

   3. On the Tasks list, click Manage Export Repository.

      The Export Repository appears.

2. Select the file to be installed and click Install in the Action column.

3. Follow the on-screen instructions and click the Install button.

Deleting Files from the Export Repository

You can delete a file from the Export Repository.

To delete a file from the Export Repository:

1. Navigate to the Export Repository.

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

   2. Select an application.

   3. On the Tasks list, click Manage Export Repository.

      The Export Repository appears.

2. Select the file to be deleted and click Delete Checked.

Installing Export Files from SQL*Plus

You can also install export files from SQL*Plus. Note there are two restrictions:

• The export file must originate from the same user database account as the one into which you are installing.

• If the export file is an application, the application ID will be overwritten. Therefore, the target workspace must own the ID of the application being installed.

• If the export file contains Supporting Object scripts, the scripts are not run when the application is installed. You can either log in to the Application Builder to install Supporting Objects, or copy the installation scripts to a standalone SQL*Plus script and run them from there.

This section contains the following topics:

• Verifying If Source and Target Workspace IDs Are Identical

• Using SQL*Plus to Install Export Files

Creating Build Options

You create a build option for an application on the Build Options page.

To create a build option:

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

2. Select an application.

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

4. Under Application, click Build Options.

5. To create a new build option, click Create.

6. Follow the on-screen instructions.

Managing Build Options

Build options have two possible values: INCLUDE and EXCLUDE. If you specify an attribute as being included, then the Application Express engine considers it part of the application definition at run time. Conversely, if you specify an attribute as being excluded, then the Application Express engine treats it as if it did not exist.

To include or exclude a build option:

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

2. Select an application.

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

4. Under Application, click Build Options.

5. Select the appropriate build option.

   The Create/Edit Build Option page appears.

6. For Status, select either INCLUDE or EXCLUDE.

Exporting Build Options or Build Option Status

You can export build options or build option status on the Component Export page. Exporting build option status is an effective way to toggle build options on or off within another environment. For example, you can use this feature to deploy a production application with a hidden feature.

To accomplish this, you associate the components of the hidden feature with a build option having the status of EXCLUDE. After deployment, you can enable the hidden feature by changing the status of the build option to INCLUDE and then exporting the Build Option Status.

Once you apply the Build Options Status to the production instance, the new feature appears.

To export build options or build option status:

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 Component Export.

      The Component Export page appears.

2. Select the build options to be exported:

   1. Click the Components tab and select the build options to be exported.

   2. Click Add to Export.

3. Select Build Option Status to be exported:

   1. Click the Build Options Status tab and select the build options to be exported.

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

Viewing the Build Option Utilization Report

Once you create a build option, a Utilization tab appears on the Build Options page. This report details build option utilization in the current application.

To view the Build Option Utilization report:

1. Navigate to the Build Options page:

   1. Navigate to the Workspace home page.

   2. Click the Application Builder icon.

   3. Select an application.

   4. On the Application Builder home page, click Shared Components.

   5. Under Application, click Build Options.

      The Build Options page appears.

2. On the Build Options page, click Utilization.

   The Build Option Utilization report appears.

3. Select a build option and click Go.