Install Oracle Application Express by downloading a ZIP file from the Oracle Application Express download page.
To install Oracle Application Express:
For installations where the development will be in English only, download the file apex_21.1_en.zip from the Oracle Application Express download page. If the development will include languages other than English, download apex_21.1.zip from the Oracle Application Express download page. See:
Note that the actual file name may differ if a more recent release has shipped since this document was published.
Unzip downloaded zip file:
If English only, unzip apex_21.1_en.zip as follows, preserving directory names:
UNIX and Linux: $ unzip apex_21.1_en.zip
Windows: Double click the file apex_21.1_en.zip in Windows Explorer
If multiple languages, unzip apex_21.1.zip as follows, preserving directory names:
UNIX and Linux: $ unzipapex_21.1.zip
Windows: Double click the file apex_21.1.zip in Windows Explorer
Note:
You should keep the directory tree where you unzip the files short and not under directories that contain spaces. For example, within Windows unzip to C:\TEMP.
Change your working directory to apex.
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog SQL> CONNECT SYS as SYSDBA Enter password: SYS_password
On UNIX and Linux:
$ sqlplus /nolog SQL> CONNECT SYS as SYSDBA Enter password: SYS_password
Disable any existing password complexity rules for the default profile.
Select the appropriate installation option.
Full development environment provides complete access to the App Builder environment to develop applications. A Runtime environment enables users to run applications that cannot be modified.
Available installation options include:
Full development environment. Run apexins.sql passing the following four arguments in the order shown:
tablespace_apex is the name of the tablespace for the Oracle Application Express application user.
tablespace_files is the name of the tablespace for the Oracle Application Express files user.
tablespace_temp is the name of the temporary tablespace or tablespace group.
images is the virtual directory for Oracle Application Express images. For installations using EPG, /i/ is the required value for the images argument. To support future Oracle Application Express upgrades, define the virtual image directory as /i/.
Example:
@apexins.sql SYSAUX SYSAUX TEMP /i/
Note:
If you receive the following error, exit SQL*Plus and change your working directory to where you unzipped the installation file, for example C:\TEMP in Windows, before starting SQL*Plus:
SP2-0310: unable to open file "apexins.sql"
Runtime environment. Run apxrtins.sql passing the following arguments in the order shown:
tablespace_apex is the name of the tablespace for the Oracle Application Express application user.
tablespace_files is the name of the tablespace for the Oracle Application Express files user.
tablespace_temp is the name of the temporary tablespace or tablespace group.
images is the virtual directory for Oracle Application Express images. To support future Oracle Application Express upgrades, define the virtual image directory as /i/.
Example:
@apxrtins.sql SYSAUX SYSAUX TEMP /i/
When Application Express installs, it creates the following database accounts:
APEX_210100 - This account owns the Application Express schema and metadata.
FLOWS_FILES - This account owns the Application Express uploaded files.
APEX_PUBLIC_USER - This minimally privileged account is used for Application Express configuration with Oracle REST Data Services or Oracle HTTP Server and mod_plsql.
If you configured RESTful Web services, then these additional accounts will be created:
APEX_REST_PUBLIC_USER - The account used when invoking RESTful Services definitions stored in Oracle Application Express.
APEX_LISTENER - The account used to query RESTful Services definitions stored in Oracle Application Express.
If you are upgrading from a previous release, then FLOWS_FILES already exists and APEX_PUBLIC_USER is created if it does not already exist.