In order to run, Oracle Application Express must have access to a Web listener. To use Oracle REST Data Services with Oracle Application Express, you must first install Oracle Application Express and then install Oracle REST Data Services. These instructions apply to both new and upgrade installations.
Performing Pre-installation Tasks for Oracle Application Express
Installing Translated Versions of Oracle Application Express
Creating a Workspace and Adding Oracle Application Express Users
Performing Post Installation Tasks for Upgrade Installations
Converting Between Runtime and Full Development Environments
See Also:
"Web Listener Requirements" and "About Configuring Oracle REST Data Services with Oracle Application Express" in Oracle Application Express Application Builder User's Guide and "Configuring Report Printing in a Full Development Environment" in Oracle Application Express Administration GuideOracle Application Express release 5.0 requires an Oracle Database Release 11.1.0.7 or later, including Enterprise Edition and Express Edition (Oracle Database XE).
Oracle Application Express release 5.0 requires Oracle REST Data Services release 2.0 or later.
Tip:
If you are currently running Oracle REST Data Services 3.0 to 3.0.2, you should upgrade to the latest version of Oracle REST Data Services, available for download from OTN.If you are already running Oracle Application Express, then check the Oracle Application Express page on the Oracle Technology Network for information about patch set releases or later releases of Oracle Application Express:
http://www.oracle.com/technetwork/developer-tools/apex/downloads/index.html
Before installing Oracle Application Express, Oracle recommends that you complete the following steps:
Review and satisfy all Oracle Application Express installation requirements. See "Oracle Application Express Installation Requirements."
If you are actively using Oracle Application Express and upgrading the current installation then shut down with normal or immediate priority the Oracle Database instances where you plan to install Oracle Application Express. On Oracle Real Application Clusters (Oracle RAC) systems, shut down all instances on each node.
An alternative to shutting down the database is to prevent all users from accessing Oracle Application Express when upgrading your installation from a previous release of Oracle Application Express. Oracle only recommends this option in high availability production environments where planned outages are not available. For all other scenarios, the database should be shut down.
To disable access to Oracle Application Express when an existing installation is using Oracle REST Data Services, shut down the appropriate application server where Oracle REST Data Services is deployed.
Once you have prevented access from Oracle Application Express users, you should log in to SQL*Plus as SYS, connecting to the database where Oracle Application Express is installed, and query V$SESSION to ensure there are no long running sessions which would interfere with the upgrade process.
Back up the Oracle Database installation.
Oracle recommends that you create a backup of the current Oracle Database installation before you install Oracle Application Express. You can use Oracle Database Recovery Manager, which is included in the Oracle Database installation, to perform the backup.
Start the Oracle Database instance that contains the target database.
After backing up the system, you must start the Oracle instance that contains the target Oracle Database. Do not start other processes such as a Web listener. However, if you are performing a remote installation, make sure the Web listener for the remote database has started.
How you install Oracle Application Express depends upon how you access the installation script and the type of database you into which you are installing.
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).
To download the script from the Oracle Application Express download page:
For installations where the development will be in English only, download the file apex_5.0_en.zip from the Oracle Application Express download page. If the development will include languages other than English, download apex_5.0.zip from the Oracle Application Express download page. See:
http://www.oracle.com/technetwork/developer-tools/apex/downloads/index.html
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_5.0_en.zip as follows, preserving directory names:
UNIX and Linux: $ unzip apex_5.0_en.zip
Windows: Double click the file apex_5.0_en.zip in Windows Explorer
If multiple languages, unzip apex_5.0.zip as follows, preserving directory names:
UNIX and Linux: $ unzip apex_5.0.zip
Windows: Double click the file apex_5.0.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 toC:\TEMP.Change your working directory to apex.
Run the installation script. Go to the next section, "Running the Application Express Installation Script."
To access the script shipping with Oracle Database 12c Release 2 (12.2):
Change your working directory to $ORACLE_HOME/apex.
Run the installation script. Go to the next section, "Running the Application Express Installation Script."
To run the Oracle Application Express installation script:
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. See "Configuring Password Protection" in Oracle Database Security Guide.
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 exampleC:\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/
See Also:
Oracle Database PL/SQL Language Reference for more information about SQL*PlusWhen 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.
When you complete the required step to configure RESTful Web services, 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.
See Also:
Oracle Application Express must be installed from a writable directory on the file system. See "Reviewing a Log of an Installation Session."This section describes how to create or update your Instance Administrator account.
Tip:
Skip this section if you are upgrading from a previous release of Oracle Application Express. In an upgrade scenario, the Instance Administrator account and password is preserved and carried over from the prior release.Instance administrators are superusers that are responsible for managing an entire Oracle Application Express instance, including managing workspace provisioning, configuring features and instance settings, and managing security. To perform these tasks, an Instance administrator signs in to the Oracle Application Express Administration Services application.
See Also:
"Oracle Application Express Administration Services" in Oracle Application Express Administration GuideRunning the apxchpwd.sql script enables you to create or update your Instance Administrator account. You must run the apxchpwd.sql script in the following scenarios:
New Oracle Application Express installations - Run apxchpwd.sql to create an Instance Administrator account and password.
Converting of a runtime environment to a development environment - Run apxchpwd.sql to change the Instance Administrator account password.
Changing Your Instance Administrator Password -Run apxchpwd.sql to change the password for an existing Instance Administrator account.
Unlocking Your Instance Administrator Account - Run apxchpwd.sql to unlock an existing Instance Administrator account.
Tip:
You do not need to runapxchpwd.sql when upgrading from a previous release of Oracle Application Express. In an upgrade scenario, the Instance Administrator account password is preserved and carried over from the prior release.To create or update your Instance Administrator account:
Change your working directory to the apex directory where you unzipped the installation software.
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
Run apxchpwd.sql. For example:
@apxchpwd.sql
Follow the on-screen instructions. You will be prompted provide a username, password, and email address. If the account username does not exist, it will be created for you.
See Also:
Oracle Database PL/SQL Language Reference for more information about SQL*PlusAfter you install Oracle Application Express, you must restart the processes that you stopped before you began the installation.
It is important to correctly configure the APEX_PUBLIC_USER account to enable proper operation of Oracle Application Express.
The APEX_PUBLIC_USER account is created with a random password in a new installation of Oracle Application Express. You must change the password for this account before configuring the database access descriptor (DAD) in a new installation.
Tip:
If you are upgrading from a prior release of Oracle Application Express, this step is unnecessary.To unlock the APEX_PUBLIC_USER account:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. If Oracle Application Express is installed in the CDB, ensure you connect to CDB$ROOT. 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
Run the following statement:
ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK
Tip:
If you are upgrading from a prior release of Oracle Application Express, this step is unnecessary.To change the password for the APEX_PUBLIC_USER account:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. If Oracle Application Express is installed in the CDB, ensure you connect to CDB$ROOT. 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
Run the following statement:
ALTER USER APEX_PUBLIC_USER IDENTIFIED BY new_password
Where new_password is the new password you are setting for APEX_PUBLIC_USER. You will use this password when creating the DAD in the sections that follow.
In the default profile in Oracle Database 11g, the parameter PASSWORD_LIFE_TIME is set to 180. If you are using Oracle Database 11g with Oracle Application Express, this causes the password for APEX_PUBLIC_USER to expire in 180 days. As a result, your Oracle Application Express instance will become unusable until you change the password.
To prevent this behavior, create another profile in which the PASSWORD_LIFE_TIME parameter is set to unlimited and alter the APEX_PUBLIC_USER account and assign it to the new profile.
See Also:
Oracle Database Security Guide for information on creating profiles and assigning them to database usersThis section describes how to download and install Oracle REST Data Services.
Tip:
By default, the context root for accessing Oracle Application Express through Oracle REST Data Services is/ords. If you wish to have a context root of /apex for accessing Oracle Application Express, rename the ords.war file to apex.war before installing Oracle REST Data Services. See "Installing Oracle REST Data Services" in REST Data Services Installation, Configuration, and Development Guide.To download Oracle REST Data Services:
Download the latest release of Oracle REST Data Services from the following site:
http://www.oracle.com/technetwork/developer-tools/rest-data-services/downloads/index.html
Note that the version.number in the file name reflects the current release number.
Unzip the downloaded zip file into a directory (or folder) of your choice:
Copy the images directory, apex/images, from the Oracle Application Express software ZIP to a location on the file system where Oracle REST Data Services is installed.
See REST Data Services Installation, Configuration, and Development Guide and follow and complete all installation and configuration steps.
For Oracle Database 12c multitenant architecture, ensure that you configure the connection using the service name of the specific pluggable database (PDB) you want to access. Do not use the service name of the CDB$ROOT unless you are configuring Oracle REST Data Services to address PDBs through the URL. See REST Data Services Installation, Configuration, and Development Guide for more information.
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 Oracle REST Data Services as your web listener, static files are served using RESTful service module built into Oracle Application Express. Therefore, you must configure RESTful Services in new installations and in upgrade installations when RESTful Services were not configured in a previous release.
When configuring Oracle Application Express, Oracle recommends setting the parameter security.requestValidationFunction to wwv_flow_epg_include_modules.authorize. This activates the white list of callable procedures which ships with Oracle Application Express and prohibits calls to other procedures.
See Also:
"About Configuring Oracle REST Data Services with Oracle Application Express" in Oracle Application Express Application Builder User's GuideIf you were previously using the Embedded PL/SQL Gateway and now want to use Oracle REST Data Services, you need to disable the Oracle XML DB Protocol Server.
To disable Oracle XML DB Protocol Server:
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
Run the following command:
EXEC DBMS_XDB.SETHTTPPORT(0);
When Oracle Application Express is running behind a reverse proxy or load balancer, it is important to communicate the original HTTP hostname and protocol as seen by the user's browser to the Application Express engine. The Application Express engine uses this information to generate valid URLs in HTML responses and HTTP redirects that the user's browser can successfully follow. The exact configuration steps depend on your Java EE application server. For example, for Oracle WebLogic Server, this is accomplished using Oracle WebLogic Server Proxy Plug-Ins. To learn more, see your Java EE application server documentation.
This section describes how to configure RESTful Services in a new installation.
In a new installation of Oracle Application Express, you configure RESTful Services by running the configuration script apex_rest_config.sql. Once configured, the instance administrator can control the availability of the feature. If the instance administrator has disabled RESTful Services for this Application Express instance, RESTful Services are not available for this instance and the RESTful Services icon does not display. See "Controlling RESTful Services for an Instance" in Oracle Application Express Administration Guide.
Note:
RESTful Services requires Oracle REST Data Services 2.0 or later. The configuration of RESTful Services is required when upgrading to Oracle Application Express release 5.0 and RESTful Services were not configured in a previous release.To configure RESTful Services in Oracle Application Express:
Change your working directory to the apex directory where you unzipped the installation software.
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
Run apex_rest_config.sql. For example:
@apex_rest_config.sql
When Prompted, enter a password for the APEX_LISTENER and APEX_REST_PUBLIC_USER accounts.
When configuring RESTful Services in Oracle Application Express, it creates two new database accounts.
APEX_LISTENER - The account used to query RESTful Services definitions stored in Oracle Application Express.
APEX_REST_PUBLIC_USER - The account used when calling RESTful Services definitions stored in Oracle Application Express.
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.
Tip:
To run the examples described in this section, the compatible initialization parameter of the database must be set to at least 11.1.0.0.0. By default a 11g or 12c database will already have the parameter set properly, but a database upgraded to 11g or 12c from a prior version may not. See "Creating and Configuring an Oracle Database" in Oracle Database Administrator's Guide for information about changing database initialization parameters.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;
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;
/
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."
Oracle highly recommends you configure and use Secure Sockets Layer (SSL) to ensure that passwords and other sensitive data are not transmitted in clear text in HTTP requests. Without the use of SSL, passwords could potentially be exposed, compromising security.
SSL is an industry standard protocol that uses RSA public key cryptography in conjunction with symmetric key cryptography to provide authentication, encryption, and data integrity.
See Also:
"Configuring HTTP Protocol Attributes" in Oracle Application Express Administration GuideThis section explains how to specify the number of concurrently running 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.
This section describes three ways to view the number of JOB_QUEUE_PROCESSES:
After installing or upgrading Oracle Application Express, you can view the number of JOB_QUEUE_PROCESSES in the installation log files. See "Reviewing a Log of an Installation Session."
You can view the number of JOB_QUEUE_PROCESSES on the About Application Express page.
To view the About Application Express page:
Sign in to Oracle Application Express. See "Signing In to Your Workspace."
Locate the Help menu at the top of the page.
From the Help menu, select About.
The About Application Express page appears. The current number JOB_QUEUE_PROCESSES displays at the bottom of the page.
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:
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
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.
The Oracle Application Express interface is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. A single instance of Oracle Application Express can be installed with one or more of these translated versions. Developers can choose to run the Application Express development environment in any of the installed languages by simply selecting the language from the Application Builder log in screen or home page.
In order to install other languages you must use the apex_5.0.zip file which contains the extra files referenced below. If you previously downloaded apex_5.0_en.zip, then you do not need to re-install Oracle Application Express. Simply download apex_5.0.zip and unzip the file into the same directory where you unzipped apex_5.0_en.zip.
The translated version of Oracle Application Express should be loaded into a database that has a character set that supports the specific language. If you attempt to install a translated version of Oracle Application Express into a database that does not support the character encoding of the language, the installation may fail or the translated Oracle Application Express instance may appear corrupt when run. The database character set AL32UTF8 supports all the translated versions of Oracle Application Express.
You can manually install translated versions of Oracle Application Express using SQL*Plus. The installation files are encoded in AL32UTF8.
Note:
Regardless of the target database character set, to install a translated version of Oracle Application Express, you must set the character set value of theNLS_LANG environment variable to AL32UTF8 before starting SQL*Plus.The following examples illustrate valid NLS_LANG settings for loading Oracle Application Express translations:
American_America.AL32UTF8 Japanese_Japan.AL32UTF8
This section describes installing translated versions of Oracle Application Express.
About Installing Translated Versions of Oracle Application Express
Installing a Translated Version 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).
To install a translated version of Oracle Application Express:
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
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
Execute the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_050000;
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).
Before you can develop or install applications, you must create a workspace, add Oracle Application Express users and sign in to your workspace.
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.
See Also:
"Creating Workspaces" and "Managing Workspace and Change Requests" in Oracle Application Express Administration GuideTo 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:
In a Web browser, navigate to the Oracle Application Express Administration Services application.
Tip:
By default, the context root for accessing Oracle Application Express through Oracle REST Data Services is/ords. If you wish to have a context root of /apex for accessing Oracle Application Express, rename the ords.war file to apex.war before installing Oracle REST Data Services. See "Installing Oracle REST Data Services" in REST Data Services Installation, Configuration, and Development Guide.Because your setup uses Oracle REST Data Services go to:
http://hostname:port/apex/apex_admin
Where:
hostname is the name of the system where Oracle REST Data Services is installed.
port is the port number assigned when configuring Oracle REST Data Services. In a default installation, this number is 8080. To learn more, see REST Data Services Installation, Configuration, and Development Guide.
apex is the service name defined when configuring Oracle REST Data Services.
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.
See Also:
"Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.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:
Access Oracle Application Express Administration Services. See "Accessing Oracle Application Express Administration Services."
Oracle Application Express Administration Services appears. Next, create a workspace.
Click Manage Workspaces.
Under Workspace Actions, click Create Workspace.
The Create Workspace Wizard appears.
For Identify Workspace, enter the following:
Workspace Name - Enter a unique workspace name.
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.
Workspace Description - Enter a workspace description.
Click Next.
For Identify Schema, specify whether you are re-using an existing schema or creating a new one.
If you are using an existing schema:
For Re-use existing schema, select Yes.
Select a schema from the list.
Click Next.
If you are creating a new schema:
For Re-use existing schema, select No.
Enter a schema name and password.
Specify a space quota.
Click Next.
For Identify Administrator, enter the Workspace administrator information and click Next.
Confirm your selections and click Create Workspace.
See Also:
"Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.To create an Oracle Application Express user account:
Access Oracle Application Express Administration Services. See "Accessing Oracle Application Express Administration Services."
Oracle Application Express Administration Services appears.
Click the Manage Workspaces icon.
Click Manage Developers and Users.
Click Create User.
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.Under Account Privileges:
Workspace - Select a workspace from the list.
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.
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.
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.
Application Builder Access - Determines whether a developer has access to the Application Builder.
SQL Workshop Access - Determines whether a developer has access to the SQL Workshop.
Team Development Access - Determines whether a developer has access to the Team Development.
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.
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.
Click Create User or Create and Create Another.
Use your credentials (that is, your workspace name, user name and password) to sign in to the workspace.
To sign in to your workspace:
In a Web browser, navigate to the Oracle Application Express Sign In page.
Because your setup uses Oracle REST Data Services, go to:
http://hostname:port/apex/
Where:
hostname is the name of the system where Oracle REST Data Services is installed.
port is the port number assigned when configuring Oracle REST Data Services. In a default installation, this number is 8080. To learn more, see REST Data Services Installation, Configuration, and Development Guide.
apex is the service name defined when configuring Oracle REST Data Services.
The Sign In page appears.
On the Sign In page, enter:
Workspace - Enter the name of your workspace.
Username - Enter your user name.
Password - Enter your case-sensitive password.
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.
See Also:
See "Creating Workspaces" and "Managing Workspace and Change Requests" in Oracle Application Express Administration GuideOnce you have verified that your upgrade installation was successful and all upgraded applications function properly, you should remove schemas from 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.
To verify if a prior installation exists:
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
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.
To remove schemas from prior installations:
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
Execute a statement similar to the following example:
DROP USER APEX_040200 CASCADE;
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:
Change your working directory to the apex directory where you unzipped the installation software.
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
Execute a statement similar to the following:
EXEC DBMS_NETWORK_ACL_ADMIN.DELETE_PRIVILEGE('power_users.xml', 'FLOWS_030000');
Performance of web applications heavily depends on their size and how often a browser has to request static content like images, CSS and JavaScript files. To improve performance, most web servers support on-the-fly HTTP response compression and provide settings that enable you to configure on how long browsers can cache a file before requesting it again. The HTTP response compression is usually implemented using gzip encoding, while browser file caching is enabled by issuing Cache-Control HTTP response header.
Please see your web server documentation to learn how to enable response compression and browser file caching. For optimal performance of the Oracle Application Express development environment and Oracle Application Express applications, Oracle recommends enabling gzip compression of files in the virtual images directory (for example, /i/) and responses from the database access descriptor as well as allowing browsers to cache files from the virtual images directory for at least 12 hours.
This section describes how to convert between runtime and full development environments.
Converting a Runtime Environment to a Full Development Environment
Converting a Full Development Environment to a Runtime Environment
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.
See Also:
"About the Oracle Application Express Runtime Environment" and "Installing Exported Applications into a Runtime Environment" in Oracle Application Express Administration GuideTo convert an Oracle Application Express runtime environment to a full development environment:
Change your working directory to the apex directory where you unzipped the installation software.
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
Run apxdvins.sql. For example:
@apxdvins.sql
Follow the instructions in "Creating or Updating Your Instance Administration Account."
See Also:
Oracle Database PL/SQL Language Reference for more information about SQL*PlusTip:
Before converting a full development environment to a runtime environment, export all Websheet applications. When you convert a development environment to runtime, existing Websheet data grids and reports will be deleted from all workspaces. Converting the environment back to a full development environment will not restore these Websheet data grids or reports.To convert an Oracle Application Express full development environment to a runtime environment:
Change your working directory to the apex directory where you unzipped the installation software.
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
Run apxdevrm.sql. For example:
@apxdevrm.sql
See Also:
Oracle Database PL/SQL Language Reference for more information about SQL*Plus