• Step 1: Create a new tablespace to act as the default tablespace for APEX.

-- For Oracle Managed Files (OMF).

CREATE TABLESPACE apex DATAFILE SIZE 100M AUTOEXTEND ON NEXT 1M;

-- For non-OMF.

CREATE TABLESPACE apex DATAFILE '/path/to/datafiles/apex01.dbf' SIZE 100M AUTOEXTEND ON NEXT 1M;

• Step 2: - Change directory to the directory holding the  APEX software.

cd $ORACLE_HOME/apex

• Step 3:- Connect to SQL*Plus as the SYS user and run the "apexins.sql" script, specifying the relevant table space names and image URL.

For Full development environment

SQL> CONN sys@pdb1 AS SYSDBA

SQL> -- @apexins.sql tablespace_apex tablespace_files tablespace_temp images

SQL> @apexins.sql APEX APEX TEMP /i/

For Run Time environment

SQL> @apxrtins.sql APEX APEX TEMP /i/

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.

When Oracle Application Express installs, it creates three new database accounts:

APEX_050000 - The account that owns the Oracle Application Express schema and metadata.

FLOWS_FILES - The account that owns the Oracle Application Express uploaded files.

APEX_PUBLIC_USER - The minimally privileged account is used for Oracle Application Express configuration with Oracle REST Data Services or Oracle HTTP Server and mod_plsql

• Step 4: Now, change the admin password by running the "apxchpwd.sql" scripts as the SYS user.

SQL> @apxchpwd.sql

• Step 6: Now we need to decide which gateway to use to access APEX. The Oracle recommendation is ORDS.

We have 3 options, we can choose any one out of the three to front APEX

• Oracle REST Data Services (ORDS) Configuration

• Embedded PL/SQL Gateway (EPG) Configuration

• Oracle HTTP Server (OHS) Configuration