Databases Reference
In-Depth Information
■
Because all script types are standard SQl and pl/SQl, you have the option of writing quite complex logic that
can decide within the script what steps to take. however, there is no interactivity or shared session state between the
individual scripts, so you can't decide in the first script whether to run the second or third script. every script in the set
will be run regardless of the result of the previous scripts. errors are shown only after all scripts have been run.
Note
The process of building a packaged application that includes supporting objects can be daunting. The good news
is that, in a standard IT environment, the scripts to migrate database objects are rarely processed using supporting
objects. Although supporting objects are very useful, they tend to lend themselves to situations, such as shrink-
wrapped software, where applications are sent to remote sites where there is little or no direct interaction with the
installing user.
For applications that are being developed and deployed in a single organization, rules and guidelines are
probably in place for migrating applications to production. Make sure you check with your organization and adhere to
those standards.
Importing
APEX applications can be imported by providing the application export script. You can import into a different
workspace or into the original workspace. The Application Import Wizard is available from the Application Builder
home page. Figure
10-18
shows the initial page of the wizard.
Figure 10-18.
Import file identified as a database application
As you can see, the wizard allows you to import many different types of APEX export scripts. Make sure you
choose the right type for the file you're trying to import. When importing an application export script, click Browse to
choose the application export file, and be sure to choose Database Application, Page, or Component Export.
