5 Installing Application Express and Configuring Embedded PL/SQL Gateway

5.4.1 Accessing the Installation Script

How you access the Oracle Application Express installation script depends upon whether you download the Oracle Application Express distribution from Oracle Technology Network (OTN), or install the version that ships with Oracle Database 12c Release 2 (12.2).

5.4.2 Running the Application Express Installation Script

To run the Oracle Application Express installation script:

1. 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
     

2. Disable any existing password complexity rules for the default profile. See "Configuring Password Protection" in Oracle Database Security Guide.

3. Select an installation option.

   Full development environment provides complete access to the Application Builder environment to develop applications. A Runtime environment enables users to run applications that cannot be modified.

   • Full development environment.

     Run apexins.sql passing the following four arguments in the order shown:

     @apexins.sql tablespace_apex tablespace_files tablespace_temp images
     

     Where:

     • 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:

     @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:

     @apxrtins.sql tablespace_apex tablespace_files tablespace_temp images
     

     Where:

     • 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 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.

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.

5.4.3 Creating or Updating Your Instance Administration Account

This section describes how to create or update your Instance Administrator account.

• What Is an Instance Administrator?

• About apxchpwd.sql

• Running apxchpwd.sql

5.4.4 Restarting Processes

After you install Oracle Application Express, you must restart the processes that you stopped before you began the installation.

5.5.1 Running the apex_epg_config.sql Configuration Script

You configure the Embedded PL/SQL Gateway by running the configuration script apex_epg_config.sql. Then, you unlock the ANONYMOUS account.

To run the apex_epg_config.sql configuration script:

1. Change your working directory to the apex directory where you unzipped the Oracle Application Express software.

2. 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
     

3. If you are configuring a PDB, enter the following statement:

   ALTER SESSION SET CONTAINER = <PDB_NAME>;
   

4. Run apex_epg_config.sql passing the file system path to the base directory where the Oracle Application Express software was unzipped as shown in the following example:

   • On Windows:

     @apex_epg_config.sql SYSTEM_DRIVE:\TEMP
     

   • On UNIX and Linux:

     @apex_epg_config.sql /tmp
     

5. Enter the following statement to unlock the ANONYMOUS account:

   ALTER USER ANONYMOUS ACCOUNT UNLOCK;
   

5.5.2 Updating the Images Directory When Upgrading from a Previous Release

If you are upgrading Oracle Application Express from a previous release, you must run the apex_epg_config.sql script to update the images directory.

To run the apex_epg_config.sql script:

1. Change your working directory to the apex directory where you unzipped the Oracle Application Express software.

2. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role:

   • 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
     

3. Run apex_epg_config.sql passing the file system path to the base directory where the Oracle Application Express software was unzipped as shown in the following example:

   • On Windows:

     @apex_epg_config.sql SYSTEM_DRIVE:\TEMP
     

   • On UNIX and Linux:

     @apex_epg_config.sql /tmp
     

   Tip:

   The above examples assume that you unzipped Oracle Application Express in a directory called TEMP on Windows and tmp on UNIX or Linux.

5.5.3 Verifying the Oracle XML DB Protocol Server Port

The Embedded PL/SQL Gateway runs in the Oracle XML DB Protocol Server in the Oracle database. You can determine if the Oracle XML DB Protocol Server is enabled by verifying the associated port number.

To verify the port number where the Oracle XML DB Protocol Server is running:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role:

   • 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
     

2. Enter the following statement to verify the port number:

   SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;
   

   If the port number returns 0, the Oracle XML DB Protocol Server is disabled.

3. To enable it, follow the instructions in the sect section, "Enabling Oracle XML DB Protocol Server."

5.5.4 Enabling Oracle XML DB Protocol Server

The Embedded PL/SQL Gateway runs in the Oracle XML DB Protocol Server in the Oracle database.

To enable Oracle XML DB Protocol Server:

1. 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
     

2. Enter a statement similar to the following:

   EXEC DBMS_XDB.SETHTTPPORT(port);
   

   For example:

   EXEC DBMS_XDB.SETHTTPPORT(8080);
   

5.5.5 Configuring Static File Support

Oracle Application Express enables application developers to include static files with their applications. Static files can be associated with a workspace, an application, a plug-in, or an application theme. When using the embedded PL/SQL Gateway as your web listener, the necessary configuration to support static files is performed as part of the embedded PL/SQL Gateway configuration.

5.5.6 About Configuring Embedded PL/SQL Gateway Behind a Reverse Proxy or Load Balancer

If Oracle Application Express will be running behind a reverse proxy or load balancer, you set the CGI environment variables PROTOCOL and HTTP_HOST. For Embedded PL/SQL Gateway, you must call the following PL/SQL block:

1. Change your working directory to the apex directory where you unzipped the installation software.

2. 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
     

3. Execute the following PL/SQL block:

   BEGIN
    DBMS_EPG.set_dad_attribute (
    dad_name => 'APEX',
    attr_name => 'cgi-environment-list',
    attr_value => 'REQUEST_PROTOCOL=https');
    DBMS_EPG.set_dad_attribute (
    dad_name => 'APEX',
    attr_name => 'cgi-environment-list',
    attr_value => 'HTTP_HOST=external-name:external-port');
    commit;
   END;
   /
   

To learn more, see your Java EE application servers documentation.

5.6.1 When and Why Network Services Must be Enabled

By default, the ability to interact with network services is disabled in Oracle Database 11g Release 1 or 2 or later. Therefore, if you are running Oracle Application Express with Oracle Database 11g Release 1 or 2 or later, you must use the new DBMS_NETWORK_ACL_ADMIN package to grant connect privileges to any host for the APEX_050000 database user. Failing to grant these privileges results in issues with:

• Sending outbound mail in Oracle Application Express.

  Users can call methods from the APEX_MAIL package, but issues arise when sending outbound email.

• Using Web services in Oracle Application Express.

• PDF report printing.

5.6.2 Granting Connect Privileges Prior to Oracle Database 12c

The following example demonstrates how to grant connect privileges to any host for the APEX_050000 database user. This example assumes you connected to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role.

DECLARE
  ACL_PATH  VARCHAR2(4000);
BEGIN
  -- Look for the ACL currently assigned to '*' and give APEX_050000
  -- the "connect" privilege if APEX_050000 does not have the privilege yet.
 
  SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
   WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
 
  IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_050000',
     'connect') IS NULL THEN
      DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH,
     'APEX_050000', TRUE, 'connect');
  END IF;
 
EXCEPTION
  -- When no ACL has been assigned to '*'.
  WHEN NO_DATA_FOUND THEN
  DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('power_users.xml',
    'ACL that lets power users to connect to everywhere',
    'APEX_050000', TRUE, 'connect');
  DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('power_users.xml','*');
END;
/
COMMIT;

The following example demonstrates how to provide less privileged access to local network resources. This example enables access to servers on the local host only, such as email and report servers.

DECLARE
  ACL_PATH  VARCHAR2(4000);
BEGIN
  -- Look for the ACL currently assigned to 'localhost' and give APEX_050000
  -- the "connect" privilege if APEX_050000 does not have the privilege yet.
  SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
   WHERE HOST = 'localhost' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
   
  IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_050000',
     'connect') IS NULL THEN
      DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH,
     'APEX_050000', TRUE, 'connect');
  END IF;
  
EXCEPTION
  -- When no ACL has been assigned to 'localhost'.
  WHEN NO_DATA_FOUND THEN
  DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('local-access-users.xml',
    'ACL that lets users to connect to localhost',
    'APEX_050000', TRUE, 'connect');
  DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('local-access-users.xml','localhost');
END;
/
COMMIT;

5.6.3 Granting Connect Privileges in Oracle Database 12c

Procedures CREATE_ACL, ASSIGN_ACL, ADD_PRIVILEGE and CHECK_PRIVILEGE in DBMS_NETWORK_ACL_ADMIN are deprecated in Oracle Database 12c. Oracle recommends using APPEND_HOST_ACE instead. The following example demonstrates how to grant connect privileges to any host for the APEX_050000 database user. This example assumes you connected to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role.

BEGIN
    DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE(
        host => '*',
        ace => xs$ace_type(privilege_list => xs$name_list('connect'),
                           principal_name => 'apex_050000',
                           principal_type => xs_acl.ptype_db));
END;
/

The following example demonstrates how to provide less privileged access to local network resources. This example enables access to servers on the local host only, such as email and report servers.

BEGIN
    DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE(
        host => 'localhost',
        ace => xs$ace_type(privilege_list => xs$name_list('connect'),
                           principal_name => 'apex_050000',
                           principal_type => xs_acl.ptype_db));
END;
/

5.6.4 Troubleshooting an Invalid ACL Error

If you receive an ORA-44416: Invalid ACL error after running the previous script, use the following query to identify the invalid ACL:

REM Show the dangling references to dropped users in the ACL that is assigned
REM to '*'.

SELECT ACL, PRINCIPAL
  FROM DBA_NETWORK_ACLS NACL, XDS_ACE ACE
 WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL AND
       NACL.ACLID = ACE.ACLID AND
       NOT EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);

Next, run the following code to fix the ACL:

DECLARE
  ACL_ID   RAW(16);
  CNT      NUMBER;
BEGIN
  -- Look for the object ID of the ACL currently assigned to '*'
  SELECT ACLID INTO ACL_ID FROM DBA_NETWORK_ACLS
   WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;

  -- If just some users referenced in the ACL are invalid, remove just those
  -- users in the ACL. Otherwise, drop the ACL completely.
  SELECT COUNT(PRINCIPAL) INTO CNT FROM XDS_ACE
   WHERE ACLID = ACL_ID AND
         EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);

  IF (CNT > 0) THEN

    FOR R IN (SELECT PRINCIPAL FROM XDS_ACE
               WHERE ACLID = ACL_ID AND
                     NOT EXISTS (SELECT NULL FROM ALL_USERS
                                  WHERE USERNAME = PRINCIPAL)) LOOP
      UPDATE XDB.XDB$ACL
         SET OBJECT_VALUE =
               DELETEXML(OBJECT_VALUE,
                         '/ACL/ACE[PRINCIPAL="'||R.PRINCIPAL||'"]')
       WHERE OBJECT_ID = ACL_ID;
    END LOOP;

  ELSE
    DELETE FROM XDB.XDB$ACL WHERE OBJECT_ID = ACL_ID;
  END IF;

END;
/

REM commit the changes.

COMMIT;

Once the ACL has been fixed, you must run the first script in this section to apply the ACL to the APEX_050000 user. See "Granting Connect Privileges Prior to Oracle Database 12c."

5.8.1 About Managing the Number of Concurrent Jobs

JOB_QUEUE_PROCESSES determine the maximum number of concurrently running jobs. In Oracle Application Express transactional support and SQL scripts require jobs. If JOB_QUEUE_PROCESSES is not enabled and working properly, you cannot successfully execute a script.

5.8.2 Viewing the Number of JOB_QUEUE_PROCESSES

This section describes three ways to view the number of JOB_QUEUE_PROCESSES:

• Viewing JOB_QUEUE_PROCESSES in the Installation Log File

• Viewing JOB_QUEUE_PROCESSES in Oracle Application Express

• Viewing JOB_QUEUE_PROCESSES from SQL*Plus

SELECT VALUE FROM v$parameter WHERE NAME = 'job_queue_processes'

5.8.3 Changing the Number of JOB_QUEUE_PROCESSES

You can change the number of JOB_QUEUE_PROCESSES by running a SQL statement in SQL*Plus:

To update the number of JOB_QUEUE_PROCESSES:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role:

   • 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
     

2. In SQL*Plus run the following SQL statement:

   ALTER SYSTEM SET JOB_QUEUE_PROCESSES = <number>
   

   For example, running the statement ALTER SYSTEM SET JOB_QUEUE_PROCESSES = 20 sets JOB_QUEUE_PROCESSES to 20.

5.10.1 About Installing Translated Versions of Oracle Application Express

Whether you are installing for the first time or upgrading from a previous release, you must run the load_lang.sql script to run a translated version of Oracle Application Express.

The installation scripts are located in subdirectories identified by a language code in the unzipped distribution apex/builder. For example, the German version is located in apex/builder/de and the Japanese version is located in apex/builder/ja. Within each directory, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).

5.10.2 Installing a Translated Version of Oracle Application Express

To install a translated version of Oracle Application Express:

1. Set the NLS_LANG environment variable, making sure that the character set is AL32UTF8. For example:

   • Bourne or Korn shell:

     NLS_LANG=American_America.AL32UTF8
     export NLS_LANG
     

   • C shell:

     setenv NLS_LANG American_America.AL32UTF8
     

   • For Windows based systems:

     set NLS_LANG=American_America.AL32UTF8
     

2. Navigate to the directory under apex/builder based on the language you need to install. For example for German, navigate to apex/builder/de. 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
     

3. Execute the following statement:

   ALTER SESSION SET CURRENT_SCHEMA = APEX_050000;
   

4. Execute the appropriate language specific script. For example:

   @load_lang.sql
   

   Where lang is the specific language (for example, load_de.sql for German or load_ja.sql for Japanese).

5.12.1 About Workspaces and Users

You access the Oracle Application Express home page by logging in to a workspace using a JavaScript enabled Web browser. To learn more, see "Browser Requirements."

A workspace enables multiple users to work within the same Oracle Application Express installation while keeping their objects, data, and applications private. Each workspace has a unique ID and name. An instance administrator can create a workspace manually within Oracle Application Express Administration Services or have users submit requests. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance.

5.12.2 Accessing Oracle Application Express Administration Services

To manually create a workspace and user accounts, you sign in to a separate application for managing an entire Oracle Application Express instance called Oracle Application Express Administration Services. You sign in to Oracle Application Express Administration Services using the ADMIN account and password created or reset during the installation process.

To access Oracle Application Express Administration Services:

1. In a Web browser, navigate to the Oracle Application Express Administration Services application.

   Because your setup uses Embedded PL/SQL Gateway, go to:

   http://hostname:port/apex/apex_admin
   

   Where:

   hostname is the name of the system where Oracle XML DB Protocol server is installed.

   port is the port number assigned to HTTP on the Oracle XML DB Protocol server. In a default installation, this number is 8080. If you are using the Oracle Database 12c multitenant architecture, then each pluggable database (PDB) will have a distinct port number.

   apex is the database access descriptor (DAD) defined in the configuration file.

2. On the Sign In page:

   • Username - Enter admin.

   • Password - Enter the Oracle Application Express administrator account password you specified in "Creating or Updating Your Instance Administration Account."

   • Click Sign In to Administration.

   Note that, depending on your setup, you might be required to change your password when you log in for the first time.

5.12.3 Creating a Workspace Manually

To manually create a workspace you sign in to a separate application called Oracle Application Express Administration Services. You sign in to Oracle Application Express Administration Services using the ADMIN account and password created or reset during the installation process.

To create an Oracle Application Express workspace manually:

1. Access Oracle Application Express Administration Services. See "Accessing Oracle Application Express Administration Services."

   Oracle Application Express Administration Services appears. Next, create a workspace.

2. Click Manage Workspaces.

3. Under Workspace Actions, click Create Workspace.

   The Create Workspace Wizard appears.

4. For Identify Workspace, enter the following:

   1. Workspace Name - Enter a unique workspace name.

   2. Workspace ID - Leave Workspace ID blank to have the new Workspace ID automatically generated. A Workspace ID must be a positive integer greater than 100000.

   3. Workspace Description - Enter a workspace description.

   4. Click Next.

5. For Identify Schema, specify whether you are re-using an existing schema or creating a new one.

   If you are using an existing schema:

   1. For Re-use existing schema, select Yes.

   2. Select a schema from the list.

   3. Click Next.

   If you are creating a new schema:

   1. For Re-use existing schema, select No.

   2. Enter a schema name and password.

   3. Specify a space quota.

   4. Click Next.

6. For Identify Administrator, enter the Workspace administrator information and click Next.

7. Confirm your selections and click Create Workspace.

5.12.4 Creating Oracle Application Express Users

To create an Oracle Application Express user account:

1. Access Oracle Application Express Administration Services. See "Accessing Oracle Application Express Administration Services."

   Oracle Application Express Administration Services appears.

2. Click the Manage Workspaces icon.

3. Click Manage Developers and Users.

4. Click Create User.

5. Under User Attributes, enter the appropriate information. Fields marked with an asterisk are required.

   Tip:

   To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark.

6. Under Account Privileges:

   1. Workspace - Select a workspace from the list.

   2. Default Schemas - Specify the default schema used for data browsing, application creation, and SQL script execution.

      When using workspaces that have more than one schema available, this schema is the default. This setting does not control security, only the user's preference.

   3. User is an administrator - Specify if this user should have workspace administrator privileges.

      Administrators are given access to all components. Additionally, they can manage user accounts, groups, and development services. Components may not be available if they are switched off by Instance Administrators.

   4. User is a developer - Specify if this user should have developer privileges.

      Developers must have access to either Application Builder, SQL Workshop, or both. These components may not be available if they are switched off by the Instance Administrator.

   5. Application Builder Access - Determines whether a developer has access to the Application Builder.

   6. SQL Workshop Access - Determines whether a developer has access to the SQL Workshop.

   7. Team Development Access - Determines whether a developer has access to the Team Development.

   8. Set Account Availability - Select Locked to prevent the account from being used. Select Unlocked to allow the account to be used.

      If the user has exceeded the maximum log in failures allowed, specified in Workspace Preferences, then their account will be locked automatically.

7. Under Password:

   • Password - Enter a case sensitive password.

   • Confirm Password - Enter the password again.

   • Require Change of Password On First Use - Select No to allow the user to use the same password until it expires. Select Yes to require the user to change the password immediately when logging in the first time.

8. Click Create User or Create and Create Another.

5.12.5 Signing In to Your Workspace

Use your credentials (that is, your workspace name, user name and password) to sign in to the workspace.

To sign in to your workspace:

1. In a Web browser, navigate to the Oracle Application Express Sign In page.

   Because your setup uses Embedded PL/SQL Gateway, go to:

   http://hostname:port/apex/
   

   Where:

   • hostname is the name of the system where Oracle XML DB Protocol server is installed.

   • port is the port number assigned to HTTP on the Oracle XML DB Protocol server. In a default installation, this number is 8080. If you are using the Oracle Database 12c multitenant architecture, then each pluggable database (PDB) will have a distinct port number.

   • apex is the database access descriptor (DAD) defined in the configuration file.

   The Sign In page appears.

2. On the Sign In page, enter:

   • Workspace - Enter the name of your workspace.

   • Username - Enter your user name.

   • Password - Enter your case-sensitive password.

3. Click Sign In.

   Note that, depending on your setup, you might be required to change your password when you log in for the first time.

5.13.1 About Removing Prior Oracle Application Express Installations

The database users associated with schemas from prior installations are privileged users and should be removed when they are no longer necessary. Removing schemas from a prior installation is a two step process. First you verify if a prior installation exists and then you remove the schemas.

5.13.2 Verifying if a Prior Installation Exists

To verify if a prior installation exists:

1. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. 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 
     

2. Run the following query:

   SELECT username  FROM dba_users  WHERE (  username LIKE 'FLOWS\_______' ESCAPE '\'       OR username LIKE 'APEX\_______' ESCAPE '\' )   AND username NOT IN ( SELECT schema                           FROM dba_registry                          WHERE comp_id = 'APEX' );
   

If the results contain entries in the form FLOWS_XXXXXX or APEX_XXXXXX where XXXXXX represents six numbers, those entries are candidates for removal.

5.13.3 Removing Schemas from Prior Installations

To remove schemas from prior installations:

1. 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
     

2. Execute a statement similar to the following example:

   DROP USER APEX_040200 CASCADE;
   

5.13.4 Fixing Invalid ACL in Oracle Database 11g or Later

After following the instructions in"About Removing Prior Oracle Application Express Installations", you may need to fix an invalid ACL if you are running Oracle Database 11g or later and you enabled network services for the prior Oracle Application Express schema.

To fix an invalid ACL:

1. Change your working directory to the apex directory where you unzipped the installation software.

2. 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
     

3. Execute a statement similar to the following:

   EXEC DBMS_NETWORK_ACL_ADMIN.DELETE_PRIVILEGE('power_users.xml', 'FLOWS_030000');
   

5.15.1 About Runtime and Full Development Environments

An Oracle Application Express runtime environment enables users to run a production application without supporting the ability to change or edit the application. It includes only the packages necessary to run your applications, making it a more hardened environment. It does not provide a web interface for administration.

You administer an Oracle Application Express runtime environment using SQL*Plus or SQL Developer and the APEX_INSTANCE_ADMIN API.

5.15.2 Converting a Runtime Environment to a Full Development Environment in a non-CDB or Locally in a PDB

To convert an Oracle Application Express runtime environment to a full development environment in a non-CDB or locally in a PDB:

1. Change your working directory to the apex directory where you unzipped the installation software.

2. 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
     

3. Run apxdvins.sql. For example:

   @apxdvins.sql
   

4. Follow the instructions in "Creating or Updating Your Instance Administration Account."

5.15.3 Converting a Full Development Environment to a Runtime Environment in a non-CDB or Locally in a PDB

To convert an Oracle Application Express full development environment to a runtime environment in a non-CDB or locally in a PDB:

1. Change your working directory to the apex directory where you unzipped the installation software.

2. 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
     

3. Run apxdevrm.sql. For example:

   @apxdevrm.sql
   

5.15.4 Converting a Runtime Environment to a Full Development Environment in a CDB

To convert an Oracle Application Express runtime environment to a full development environment in a CDB:

1. Change your working directory to the apex directory where you unzipped the installation software.

2. 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
     

3. Run apxdvins_con.sql. For example:

   @apxdvins_con.sql
   

4. Follow the instructions in "Creating or Updating Your Instance Administration Account."

5.15.5 Converting a Full Development Environment to a Runtime Environment in a CDB

To convert an Oracle Application Express full development environment to a runtime environment in a CDB:

1. Change your working directory to the apex directory where you unzipped the installation software.

2. 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
     

3. Run apxdevrm_con.sql. For example:

   @apxdevrm_con.sql