Databases Reference
In-Depth Information
The second option,
Reuse Application ID from Export File
, will use the application
ID that is speciied in the export ile. This will be the same ID as the original
application. When you use this option, the previously deployed application, if there
is one, will be overridden. You will be prompted if you want to replace the existing
application (
Figure 17
):
Figure 17: Confirmation Question to Replace an Existing Application
This should be the option you want to use. This way, you will only have one version
of the production application in the production environment. There will never be
any confusion as to which application is the "real" one.
If you auto assign a new application ID, the import process will also alter your
application alias. Using an application alias is very convenient, because it allows
you provide the users with a single URL, such as
http://xp-vm:8080/apex/
f?p=DOCMAN
.
This URL doesn't need to change after you deploy the new version of the application.
The last option with regard to the application ID is to change it. When you choose
this option, you will see a new text item where you can input your new application
ID. There is a restriction, however. Not all application IDs are allowed. Oracle
reserves the range between 3000 and 9000.
After you complete this form, the actual installation of the application will start:
Figure 18. Processing Animation when Installing
