|Oracle® Application Express Installation Guide
|PDF · Mobi · ePub|
This chapter provides an overview of installing Oracle Application Express and describes issues to consider before installing.
The installation process involves the following:
Plan your installation: This chapter offers an overview of the steps required to install Oracle Application Express. During the planning phase, you should determine whether to install a full development environment or runtime environment. You should also determine which Web Listener to use. Available options include the Oracle Application Express Listener, the embedded PL/SQL gateway, or Oracle HTTP Server and
A full development environment provides complete access to the Application Builder environment to develop applications. A runtime environment is an appropriate choice for production implementations in which you want to run applications that cannot be modified. To learn more, see "About the Oracle Application Express Runtime Environment".
Verify installation requirements: "Oracle Application Express Installation Requirements" describes the minimum requirements that your system must meet before you install the software.
Install the software: The required installation steps depend upon which Web Listener you decide to use.
If you have release 1.5.x, 1.6.x, 2.0.x, 2.2.x, 3.0.x, 3.1.x, 3.2.x, 4.0x or 4.1x of Oracle Application Express, following any of the installation scenarios in this guide upgrades your Oracle Application Express instance to release 4.2 and creates Oracle Application Express 4.2 database objects in a new schema and migrates the application metadata to the new release.
For testing and production instances, Oracle Application Express supports the ability to install just a runtime version of Oracle Application Express. This runtime environment minimizes the installed footprint and privileges and improves application security since in a runtime instance developers cannot inadvertently update a production application.
An Oracle Application Express runtime environment enables you to run production applications, but it does not provide a Web interface for administration. A runtime environment only includes the packages necessary to run your application, making it a more hardened environment. You administer the Oracle Application Express runtime environment using SQL*Plus or SQL Developer and the
APEX_INSTANCE_ADMIN API. To learn more see, "Managing a Runtime Environment" in Oracle Application Express Application Builder User's Guide.
Scripts are provided to remove or add the developer interface from an existing instance. To learn more, see "About the Oracle Application Express Runtime Environment".
In order to receive and respond to requests over the Internet, Oracle Application Express uses one of the following three web listeners, Oracle Application Express Listener, Oracle HTTP Server with
mod_plsql,or the embedded PL/SQL gateway.
For further information on selecting the best web listener, please review the Oracle Application Express Deployment page on Oracle Technology Network (OTN):
Oracle Application Express Listener communicates directly with the Oracle Application Express engine. Oracle HTTP Server uses the
mod_plsql plug-in to communicate with the Oracle Application Express engine within the Oracle database. Oracle Application Express Listener and the Oracle HTTP Server function as communication brokers between the Web server and the Oracle Application Express objects in the Oracle database. More specifically, they map browser requests into database stored procedure calls over a
SQL*Net connection. The following graphic illustrates the Oracle Application Express architecture using the Oracle Application Express Listener.
See Also:"Web Listener Requirements"
Note this three tier architecture consists of the following components:
Oracle Application Express Listener or Oracle HTTP Server with
Oracle database containing Oracle Application Express
The major advantage of Oracle Application Express Listener or Oracle HTTP Server (Apache) with
mod_plsql is the separation of the mid-tier and the database tier. Note that this architecture is appropriate for Oracle Real Application Clusters (Oracle RAC) environments. See "Selecting a Web Listener in an Oracle RAC Environment".
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/. If you are upgrading Oracle Application Express from a prior release, you can locate the images directory on the file system, by reviewing the following files and searching for the text alias
Oracle HTTP Server distributed with Oracle Database 11g release 1 and later — see the
Oracle Application Server 10g—see the
Specific examples for locating the text alias
/i/ can be found in "Downloading from Oracle Technology Network" on page 3-1.
Oracle XML DB Protocol Server with the embedded PL/SQL gateway installs with Oracle Database. It provides the Oracle database with a Web server and also the necessary infrastructure to create dynamic applications. The embedded PL/SQL gateway runs in the Oracle XML DB Protocol server in the Oracle database and includes the core features of
mod_plsql. The following graphic illustrates the Oracle Application Express architecture using the embedded PL/SQL gateway.
As shown in the previous graphic, the embedded PL/SQL gateway consists of a simple two tier architecture: a Web browser and an Oracle database containing the embedded PL/SQL gateway and Oracle Application Express.
Advantages of the embedded PL/SQL gateway include:
Ease of configuration
Included in the database
No separate server installation
The embedded PL/SQL gateway runs in the database as part of the XML DB HTTP Protocol Listener. Because the HTTP Listener runs in the same database where Oracle Application Express is installed, it is not possible to separate the HTTP listener from the database. For this reason, Oracle does not recommend the use of the embedded PL/SQL gateway for applications that run on the Internet.
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 "Accessing the Repository Using Protocols" in Oracle XML DB Developer's Guide.
When running Oracle Application Express in an Oracle Real Application Clusters (Oracle RAC) environment, Oracle recommends that you use Oracle Application Express Listener or Oracle HTTP Server with
mod_plsql. Oracle Application Express Listener or Oracle HTTP Server with
mod_plsql permit you to specify a connection in the service name format, so that one HTTP Server can access all nodes.
Oracle recommends that you do not select the embedded PL/SQL gateway option for Oracle RAC installations. The embedded PL/SQL gateway uses an HTTP Server built into the database instance, and because of this, it does not take advantage of the Oracle RAC shared architecture.
How you install Oracle Application Express, depends on which web listener you decide to use. This section provides an overview of each installation scenario.
See Also:"About Choosing a Web Listener" and "About the Oracle Application Express Runtime Environment"
Follow the steps in this scenario if you are downloading Oracle Application Express from Oracle Technology Network (OTN) and configuring the Oracle Application Express Listener. Required installation steps in this scenario include:
Step 4: Configure RESTful Services
Step 5: Restart Processes
Step 9: Security Considerations
Step 11: About Managing JOB_QUEUE_PROCESSES
Follow the steps in this scenario if you are downloading Oracle Application Express from Oracle Technology Network (OTN) and configuring the embedded PL/SQL gateway. Required installation steps in this scenario include:
Step 6: Security Considerations
Follow the steps in this scenario if you are downloading Oracle Application Express from Oracle Technology Network (OTN) and configuring Oracle HTTP Server with
mod_plsql distributed with Oracle Database 11g or Oracle Application Server 10g. Required steps in this scenario include:
Step 4: Restart Processes
Step 7: Security Considerations