Databases Reference
In-Depth Information
Figure 1-7.
Defining an application alias
You can also do the same thing with a page alias, as shown in Figure 1-8.
Figure 1-8.
Defining a page alias
Now instead of the URL
http://yourserver/pls/apex/f?p=1000:1:
our users can use
http://yourserver/pls/apex/f?p=ORDERS:HOME:
which is a little bit nicer, I hope you'll agree. One thing to bear in mind is that, internally, whenever APEX
generates any links within your application, it will use the numeric application id, unfortunately ,rather
than the application alias. The end results of this means that the application alias and page alias will be
changed in the URL to the numeric ids once the user starts navigating within the application.
But you can go a bit further with the use of Apache Virtual hosts. You have a couple of options at this
point: you can either put the definition of the virtual hosts in the main
httpd.conf
file itself, or include
them in a separate file. My own personal choice is to try and keep the main
httpd.conf
as clean as
possible and to do all my own customizations in my own files that are included from the main
httpd.conf
. To achieve this, I create a subdirectory called
vhosts
(you can name it anything you like) in
$ORACLE HOME/ohs/conf
and then include the following line at the end of the
httpd.conf
file:
