Instance administrators use the settings under Manage Instance to manage and configure an Oracle Application Express instance.
Use the Feature Configuration page to configure application development and SQL Workshop option as well as control database monitoring.
See Also:
"Managing Component Availability"By default, developers can change and compile PL/SQL source code when browsing database procedures, packages, and functions in Object Browser. As an Instance administrator, you can control PL/SQL program unit editing for an entire instance by making a selection from Allow PL/SQL Program Unit Editing.
To disable PL/SQL program unit editing:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Feature Configuration.
Locate the Application Development section.
For Allow PL/SQL Program Unit Editing, select No.
Click Apply Changes.
See Also:
"Disabling PL/SQL Program Unit Editing for a Workspace" for information about disabling PL/SQL program unit editing for a specific workspaceWhen an Instance administrator creates a new workspace, Oracle Application Express automatically creates a demonstration application within the workspace.
To disable the creation of demonstration applications:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Feature Configuration.
Locate the Application Development section.
For Create demonstration objects in new workspaces, select No.
Click Apply Changes.
When an Instance administrator creates a new workspace, Oracle Application Express automatically creates Websheet objects within the workspace.
To disable the creation of Websheet objects:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Feature Configuration.
Locate the Application Development section.
For Create Websheet objects in new workspaces, select No.
Click Apply Changes.
As an Instance administrator, you can use the attributes under SQL Workshop to configure basic SQL Workshop behavior.
To configure SQL Workshop:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Feature Configuration.
Under SQL Workshop, enter the attributes described in Table 2-1.
Table 2-1 SQL Workshop Attributes
| Attribute | Description |
|---|---|
|
SQL Commands Maximum Inactivity in minutes |
Identify the maximum amount of time a transactional command in the SQL Command Processor waits before timing out. |
|
SQL Scripts Maximum Script Output Size in bytes |
Identify the maximum amount of output a single SQL script can generate. SQL scripts are run from the SQL Workshop. |
|
SQL Scripts Maximum Workspace Output Size in bytes |
Identify the maximum amount of space all scripts within a workspace may consume. SQL script results are the output generated when running SQL scripts from the Script Editor or from the SQL Scripts home page. |
|
SQL Scripts Maximum Script Size in bytes |
Identify the maximum size of a SQL script used within the SQL Workshop. |
|
Enable Transactional SQL Commands |
Select Yes to enable transactional SQL commands for the entire Oracle Application Express instance. Enabling this feature permits SQL Command Processor users to issue multiple SQL commands within the same physical database transaction. When you select Yes, an Autocommit check box appears on the SQL Command Processor page. By default, this option is set to No. |
Click Apply Changes.
Setting Enable Database Monitoring to Yes enables monitoring within SQL Workshop. Before you can access the Database Monitoring page, an Instance administrator must enable database monitoring.
See Also:
"Monitoring the Database" in Oracle Application Express SQL Workshop GuideTo enable database monitoring:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Feature Configuration.
Scroll down to Monitoring.
For Enable Database Monitoring, select Yes.
Click Apply Changes.
Note:
Only users having a database user account that has been granted a DBA role can access the Database Monitor page.Instance administrators can configure security settings, such as turning off cookies used to populate the login form in Application Express, controlling access to accounts, and setting up password policies.
Disabling Access Oracle Application Express Administration Services
Restricting Access to Oracle Application Express by Database Access Descriptor (DAD)
Instance administrators can control if a convenience cookie is sent to a user's computer whenever a developer or administrator logs in to a workspace from the Application Express Login page. By default, the Set Workspace Cookie option is set to Yes.
If selected, Oracle Application Express sends a persistent cookie that:
combines the last used workspace name and user name
has a lifetime of six months
is read to populate the Application Express Workspace Login form (but not the Oracle Application Express Administration Services Login form)
Note:
If your computer has received this cookie, you can physically remove it from its persistent location on disk using browser tools or system utilities. The cookie is namedORA_WWV_REMEMBER_UN. In older releases of Oracle Application Express, this cookie was named ORACLE_PLATFORM_REMEMBER_UN. It may exist for each Oracle Application Express service accessed having distinct hostname and path components.To prevent a cookie from being sent to the user's computer when logging in:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Locate the Security section.
For Set Workspace Cookie, select No.
Click Apply Changes.
Instance administrators can restrict user access to Oracle Application Express Administration Services. This prevents any user from logging in to Oracle Application Express Administration Services.
To disable user access to Oracle Application ExpressAdministration Services:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Locate the Security section.
For Disable Administrator Login, select Yes.
Click Apply Changes.
Setting this value and logging out prevents anyone from logging in to Oracle Application Express Administration Services.
To reverse this setting and enable administrator login:
Connect in SQL*Plus and connect to the database where Oracle Application Express is installed as SYS, for example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000;
Run the following statements:
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER('DISABLE_ADMIN_LOGIN', 'N');
commit;
END;
/
Developers and Workspace administrators log into the Oracle Application Express development environment to access the Application Builder, SQL Workshop, Team Development and Administration.
To restrict access to these applications, select Yes from Disable Workspace Login. This option effectively sets a Runtime Only environment while still allowing Instance administrators to log into Instance Administration. Selecting Yes in production environments prevents developers from changing applications or data.
See Also:
"Managing a Runtime Environment"To disable user access to the Internal workspace:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Locate the Security section.
From Disable Workspace Login, select Yes.
Selecting Yes prevents users from logging in to the Internal workspace.
Click Apply Changes.
Use the Allow Public File Upload attribute to control whether unauthenticated users can upload files in applications that provide file upload controls.
To control file upload:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Locate the Security section.
From Allow Public File Upload, select one of the following:
Yes enables unauthenticated users to upload files in applications in the Internal workspace.
No prevents unauthenticated users from uploading files in applications in the Internal workspace.
Click Apply Changes.
Instance administrators can restrict user access to an Oracle Application Express instance by creating a Runtime setting named RESTRICT_IP_RANGE.
To restrict user access by IP address:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Locate the Security section.
For Disable Administrator Login, select No.
In Restrict Access by IP Address, enter a comma-delimited list of IP addresses. Use an asterisk (*) to specify a wildcard.
You can enter IP addresses from one to four levels. For example:
141, 141.* ... 192.128.23.1 ...
Note:
When using wildcards, do not include additional numeric values after wildcard characters. For example,138.*.41.2.Click Apply Changes.
Secure Socktets Layer (SSL) is a protocol for managing the security of data transmitted on the Internet. For Web applications, SSL is implemented by using the HTTPS protocol. Oracle recommends that you run Oracle Application Express applications using SSL (HTTPS protocol) to prevent any sensitive data from being sent over an unencrypted (cleartext) communication channel.
You can configure both your Oracle Application Express instance and all related applications to require HTTPS by setting the Require HTTPS attribute to Yes on the Manage Service page.
Note:
If you set Require HTTPS to Yes, you will only be able to log in to an Oracle Application Express workspace or Oracle Application Express Administration Services over HTTPS.To require HTTPS for an Oracle Application Express instance:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Locate the Security section.
For Require HTTPS, select Yes.
Click Apply Changes.
To reverse the Require HTTPS instance-level requirement:
Connect in SQL*Plus or SQL Developer with the Application Express engine schema as the current schema, for example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000;
Run the following statements:
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER('REQUIRE_HTTPS', 'N');
commit;
end;
/
Use the Allow RESTful Access attribute to control whether developers can expose report regions as RESTful services.
See Also:
"Implementing Web Services" in Oracle Application Express Application Builder User's GuideTo enable RESTful Access:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Locate the RESTful Access section.
From Allow RESTful Access, select one of the following:
Yes enables developers to expose report regions as RESTful services.
No prevents developers from exposing report regions as RESTful services.
Click Apply Changes.
Use the attributes under Session Timeout for Oracle Application Express to reduce exposure to abandoned computers with an open Web browser at the application level.
To manage session settings for an Oracle Application Express instance:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Under Session Timeout For Application Express, specify the following attributes:
Maximum Session Length in Seconds - Enter a positive integer representing how many seconds a session can exist for Oracle Application Express applications (that is, Application Builder, SQL Workshop, and so on). Leave the value NULL to revert the value to the default of 28800 seconds (or 8 hours). This session duration may be superseded by the operation of the job that runs every eight hours which deletes sessions older than 24 hours.
Maximum Session Idle Time in Seconds - Enter a positive integer representing how many seconds a session may remain idle for Oracle Application Express applications (that is, Application Builder, SQL Workshop, and so on). Leave the value null to revert the value to the default of 1 hour (3600 seconds).
Click Apply Changes.
See Also:
"Session Timeout" in Oracle Application Express Application Builder User's GuideIt is possible to restrict regions of type URL and Web services for the entire Oracle Application Express instance. The Instance administrator defines excluded domains and regions of type URL. If a Web reference or region of type URL contains an excluded domain, an error displays informing the user that it is restricted.
To exclude a domain from regions of type URL and Web services:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
In Domain Must Not Contain, enter a colon-delimited list of excluded domains.
Click Apply Changes.
By default, no login controls are enabled across an Oracle Application Express instance. Instance administrators can enable login controls for all accounts in all workspaces across an entire development instance. Account login controls include:
Require user account expiration and locking
Set up a maximum number of failed login attempts
Set the lifetime of a password before prompted for a new one
If the Instance administrator does not enable login controls for an entire instance then each Workspace administrator can enable controls on a workspace-by-workspace basis. See "Enabling Account Login Controls for a Workspace".
Note that Account Login control affect applications that use the Application Express user account creation facilities and authentication against those accounts.
To enable login controls for all workspaces:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Scroll down to Account Login control.
Under Account Login Control:
Require User Account Expiration and Locking - Select Yes to enable this feature for all workspaces across an entire Oracle Application Express instance. This feature applies to end-user accounts created using the Application Express end-user account management interface.
Select No to relinquish control to each Workspace administrator.
Maximum Login Failures Allowed - Enter a number for the maximum number of consecutive unsuccessful authentication attempts allowed before a developer or administrator account is locked. If you do not specify a value in this field, the default value is 4.
This setting applies to Instance administrator and developer accounts. It does not apply to end user accounts.
The value you enter is used as the default for the workspace-level Maximum Login Failures Allowed preference, if the Workspace administrator does not specify a value. That preference is used for end-user accounts within the respective workspace.
Account Password Lifetime (days) - Enter a number for the maximum number of days a developer or administrator account password may be used before the account expires. If you do not specify a value in this field, a default value is 45 days.
This setting applies to accounts used to access the Application Express administration and development environment only. It does not apply to end-user accounts used by applications developed in Application Express.
The value you enter is used as the default workspace-level End User Account Lifetime preference, if the Workspace administrator specifies no value. That preference is used for end-user accounts within the respective workspace.
Click Apply Changes.
Tip:
This feature applies only to accounts created using the Application Express user creation and management facilities. It provides additional authentication security for applications. See "Managing Application Express Users".Instance administrators can enable password policies for:
All users across all workspaces (that is, Workspace administrators, developers, and end users).
Instance administrators can set up restrictions for all users, including password characters, lengths, words, and differences in consecutive passwords.
Users logging in to Oracle Application Express Administration Services
Turning on the strong password requirement for Oracle Application Express adds another layer of security to prevent hackers from determining an administrator's password. When this option is selected, passwords must meet these requirements:
consist of at least six characters
contain at least one lowercase alphabetic character, one uppercase alphabetic character, one numeric digit, and one punctuation character
cannot include the username
cannot include the word Internal
cannot contain any words shown in the Must Not Contain Workspace Name field in this section
To configure password policies:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
To set up a password policy for Workspace administrators, developers, and end users, scroll down to Workspace Password Policy and specify the attributes described in Table 2-2.
Table 2-2 Workspace Password Policy Attributes
| Attribute | Description |
|---|---|
|
Minimum Password Length |
Enter a number for the minimal character length for passwords. |
|
Minimum Password Differences |
Enter a positive integer or 0. When users change their password, the new password must differ from the old password by this number of characters. The old and new passwords are compared, character-by-character, for differences such that each difference in any position common to the old and new passwords counts toward the required minimum difference. |
|
Must Contain At Least One Alphabetic Character |
Select Yes to require that user passwords contain at least one alphabetic character. The Alphabetic Characters field lists the letters considered alphabetic characters. |
|
Must Contain At Least One Numeric Character |
Select Yes to require that user passwords contain at least one numeric character: 0,1,2,3,4,5,6,7,8, 9. |
|
Must Contain At Least One Punctuation Character |
Select Yes to require that user passwords contain at least one punctuation character. The Punctuation Characters field lists the symbols considered punctuation characters. |
|
Must Contain At Least One Upper Case Character |
Select Yes to require that user passwords contain at least one uppercase alphabetic character. |
|
Must Contain At Least One Lower Case Character |
Select Yes to require that passwords for users contain at least one lowercase alphabetic character. |
|
Must Not Contain Username |
Select Yes to prevent user passwords from containing the username, regardless of case. |
|
Must Not Contain Workspace Name. |
Select Yes to prevent user passwords from containing the workspace name, regardless of case. |
|
Must Not Contain |
Enter words, separated by colons, that may not be included in user passwords. These words may not appear in the password in any combination of uppercase or lowercase. This feature improves security by preventing the creation of some simple, easy-to-guess passwords based on words like hello, guest, welcome, and so on. |
|
Alphabetic Characters |
Enter new text or edit the existing text. This is the set of characters used in password validations involving alphabetic characters. |
|
Punctuation Characters |
Enter new text or edit the existing text. This is the set of characters used in password validations involving punctuation characters. |
Next, set up a password policy for service administrators.
Scroll down to the Service Administrator Password Policy and specify one of the following:
Use policy specified in Workspace Password Policy - Applies the password rules specified above in Workspace Password Policy to service administrator passwords.
Use default strong password policy - Applies the default strong password policy to service administrator passwords. To learn more, see item Help.
Click Apply Changes.
mod_plsql and the embedded PL/SQL gateway support a directive which enables you to name a PL/SQL function which will be called for each HTTP request. You can use this functionality to restrict the procedures that can be invoked through the embedded PL/SQL gateway or mod_plsql. The function returns TRUE if the named procedure in the current request is allowed and FALSE if it is not allowed. You can use this function to enforce access restrictions for Oracle Application Express on a per-database access descriptor (DAD) basis.
See Also:
Oracle Application Express Listener Installation GuideOracle Application Express ships with a request validation function named wwv_flow_epg_include_modules.authorize. This function specifies access restrictions appropriate for the standard DAD configured for Oracle Application Express.
During installation, the installer also creates a PL/SQL function in the Oracle Application Express product schema (APEX_040000). You can change and recompile this function to restrict access. The source code for this function is not wrapped and can be found in the Oracle Application Express product core directory in the file named wwv_flow_epg_include_local.sql. The source code is as follows
CREATE OR REPLACE FUNCTION
wwv_flow_epg_include_mod_local(
PROCEDURE_NAME IN VARCHAR2)
RETURN BOOLEAN
IS
BEGIN
RETURN FALSE; -- remove this statement when
you add procedure names to the "IN" list
IF UPPER(procedure_name) IN (
'') THEN
RETURN TRUE;
ELSE
RETURN FALSE;
END IF;
END wwv_flow_epg_include_mod_local;
/
To add names of procedures that should be allowed:
Remove or comment out the RETURN FALSE statement that immediately follows the BEGIN statement:
...
BEGIN
RETURN FALSE; -- remove this statement when
you add procedure names to the "IN" list
...
Add names to the clause representing procedure names that should be allowed to be invoked in HTTP requests. For example to allow procedures PROC1 and PROC2 the IN list you would write IN ('PROC1', 'PROC2').
After changing the source code of this function, alter the Oracle Application Express product schema (APEX_040000) and compile the function in that schema.
To alter the product schema, APEX_040000
Log in to SQL Command Line (SQL*Plus) as SYS.
Alter the product schema (APEX_040000) by entering the following command:
ALTER SESSION SET CURRENT_SCHEMA APEX_040000;
Compile the function wwv_flow_epg_include_local.sql.
The wwv_flow_epg_include_mod_local function is called by Oracle Application Express's request validation function which itself is called by the embedded PL/SQL gateway or mod_plsql. The Oracle Application Express function first evaluates the request and based on the procedure name, approves it, rejects it, or passes it to the local function, wwv_flow_epg_include_mod_local, which can evaluate the request using its own rules.
When you create new Database Access Descriptors for use with Oracle Application Express, the request validation function directive should be specified. Specifically, the function wwv_flow_epg_include_modules.authorize should be named in the directive PlsqlRequestValidationFunction in the Database Access Descriptor entry in dads.conf.
If you have no additional restrictions beyond those implemented in the wwv_flow_epg_include_modules.authorize function, there is no need to take any action with respect to the source code for the wwv_flow_epg_include_mod_local function.
The PL/SQL Request Validation Function directive is only available in Oracle Application Server 10g and Oracle HTTP Server 11g or later, as well as the embedded PL/SQL gateway in Oracle Database 11g or later. This directive is not available in Oracle HTTP Server Release 9.0.3.
In previous releases of Oracle Application Express, developers can use a URL as an argument in Oracle Application Express procedures that redirect to the defined URL. Examples include APEX_UTIL.COUNT_CLICK (p_url parameter) and WWV_FLOW_CUSTOM_AUTH_STD.LOGOUT (p_next_url parameter).
Instance administrators can define a list of authorized URLs. When a URL is provided as an argument to these procedures, it is verified internally against this list.
To manage the Authorized URLs list:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Security.
Click the Authorized URLs tab.
To add a new URL:
Click Create.
Authorized URL - Enter an authorized URL that can be used as the parameter value to certain Application Express procedures.
The entire authorized URL value will be compared with the URL parameter value in Oracle Application Express procedures. If there is an exact match up to and including the entire length of the Authorized URL value, then the URL parameter value will be permitted.
Description - Enter a description of the URL.
Click Apply Changes.
To edit an existing URL:
Click the Edit icon adjacent to the URL.
Edit the Authorized URL and Description fields.
Click Apply Changes.
To delete an existing URL:
Click the Edit icon adjacent to the URL.
Click Delete.
See Also:
Oracle Application Express API ReferenceInstance settings control Oracle Application Express configuration and apply to all workspaces within the current Oracle Application Express instance.
See Also:
"Creating Workspaces"Use the Self Service section of the Instance Setting page to determine how the process of provisioning (or creating) a workspace works for your Oracle Application Express development instance.
In Manual provision mode, an Instance administrator creates new workspaces and notifies the Workspace administrator of the login information. In Request or Email Verification provision modes, users request workspaces directly in a self-service fashion. In this scenario, users use a link on the login page to access a request form. After the workspace request has been granted, users are automatically emailed the appropriate login information.
To specify a provisioning mode:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
Under Self Service, select a provisioning status:
Manual - An Instance administrator manually creates new workspaces and notifies the Workspace administrator of the login information.
Request - Users request workspaces directly in a self-service fashion. Selecting this option displays a link on the Login page enabling users to request a workspace. When a user requests a workspace, each request is submitted to a queue for approval. When the request is approved, the user is sent an email containing login credentials (the workspace name, User ID, and password).
Email Verification - Works similar to Request except each user receives an initial email containing a verification link. Clicking this link validates the user's email address and then the request is processed. Then another email is sent to the user containing login credentials (that is, the workspace name, User ID, and password).
If you select Request or Email Verification in the previous step, enter a URL in Development Service URL (optional).
The value you enter is used in the email when the request is approved. This setting defines the URL for the service. If this setting is not present, the URL is derived from your environment.
Click Apply Changes.
Note:
To enable users to request a workspace using a link on the Login page, an Instance administrator must choose the provisioning status of Request or Email Verification as described in the previous procedure. If the provisioning status is set to Manual, no link appears on the login page.Use Email Provisioning to disables workspace provisioning when provisioning with Email Verification. Use the Message field to display a message to the user that explains why email provisioning is disabled.
To disable email provisioning:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
From Email Provisioning, select Disabled.
Selecting Disabled completely disables workspace provisioning when provisioning with Email Verification.
In Message, enter a message that explains why email provisioning is disabled.
Click Apply Changes.
Instance administrators can require a new schema when user's request a new workspace or auto extend tablespaces.
To require a new schema when creating a workspace:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
Scroll down to Storage.
From Require New Schema, select one of the following:
Yes - Requires users to request a new schema when they request a new workspace.
No - Enables users to select an existing schema when they request a new workspace.
Auto Extend Tablespaces, select Yes or No.
Click Apply Changes.
If Auto Extend Tablespaces is enabled, tablespaces provisioned with Oracle Application Expressare created with a data file that is one tenth the requested size. The data file will automatically extend up to the requested size. For example, if a user requests a 100 MB workspace, the initial size of the datafile will be 10 MB and it will automatically extend up to a maximum size of 100 MB.
To enable Auto Extend Tablespaces:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
Scroll down to Storage.
To enable Auto Extend Tablespaces, select Yes.
Click Apply Changes.
To enable Oracle Application Express to send mail, an Instance administrator must configure email settings
Additionally, if you are running Oracle Application Express with Oracle Database 11g release 1 (11.1), you need to enable outbound mail. In Oracle Database 11g release 1 (11.1), the ability to interact with network services is disabled by default. For more information, see "Enabling Network Services in Oracle Database 11g" for your configuration scenario in Oracle Application Express Installation Guide.
Tip:
You can configure Oracle Application Express to automatically email users their login credentials when a new workspace request has been approved. To learn more, see "Specifying a Provisioning Mode".To configure Oracle Application Express to send mail in a full development environment:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
Under Email, enter the following:
SMTP Host Address - Defines the server address of the SMTP server. By default on installation, this is set to localhost. If you are using another server as an SMTP relay, change this parameter to that server's address.
SMTP Host Port - Defines the port the SMTP server listens to for mail requests. The default setting is 25.
Administration Email Address - Defines the from address for administrative tasks that generate email, such as approving a provision request or resetting a password.
Notification Email Address - Enter the email address to receive notification email messages for new workspace requests and change workspace requests. If not specified, no workspace request notification email messages is sent.
Click Apply Changes.
To configure Oracle Application Express to send mail in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000
Run the following statement:
BEGIN APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE); END;
For a description of email parameters, see Table 2-3.
| Parameter Name | Description |
|---|---|
|
|
Defines the "from" address for administrative tasks that generate email, such as approving a provision request or resetting a password. Enter a valid email address, for example:
|
|
|
Defines the server address of the SMTP server. If you are using another server as an SMTP relay, change this parameter to that server's address. Default setting: localhost |
|
|
Defines the port the SMTP server listens to for mail requests. Default setting: 25 |
See Also:
"SET_PARAMETER Procedure" in Oracle Application Express API ReferenceTo determine email settings in runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000
Run the following statement:
SELECT
APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME)
FROM DUAL;
For a description of email parameters, see Table 2-3.
See Also:
"GET_PARAMETER Function" in Oracle Application Express API ReferenceSecure Sockets Layer (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. When SSL is enabled, https displays in the URL.
If you call a SSL-enabled URL (for example, by invoking a Web service), or create a region of type URL that is SSL-enabled, you must create a wallet. A wallet is a password-protected container that stores authentication and signing credentials (including private keys, certificates, and trusted certificates) needed by SSL.
To create a wallet:
The database administrator must create a wallet on the Oracle Application Express database instance. See "Using Oracle Wallet Manager" in Oracle Database Advanced Security Administrator's Guide.
The Instance administrator configures the Wallet section of the Instance Settings page to specify the file system path to the wallet and the wallet password (if required).
See Also:
"Working with SSL Enabled Web Services" in Oracle Application Express Application Builder User's Guide and "Using Oracle Wallet Manager" in Oracle Database Advanced Security Administrator's GuideTo specify wallet settings in a full development environment:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
Scroll down to Wallet.
In Wallet, enter the path on the file system where the wallet is located using the following format:
file:directory-path
If a password is required to open the wallet:
Enter a password in the Wallet Password field.
Select Check to confirm that you wish to change the wallet password.
Click Apply Changes.
To specify wallet settings in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000
Run the following statement:
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
END;
For a description of wallet parameters, see Table 2-4.
See Also:
"SET_PARAMETER Procedure" in Oracle Application Express Application Builder User's GuideTo determine wallet settings in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000
Run the following statement:
SELECT
APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME)
FROM DUAL;
For a description of wallet parameters, see Table 2-4.
See Also:
"GET_PARAMETER Function" in Oracle Application Express Application Builder User's GuideOracle Application Express provides several features so that end users can download and print reports in various formats, including PDF. To set up this functionality, different users must configure the following printing settings:
Site Level: Instance administrators must specify the level of functionality (Standard or Advanced) for an entire Oracle Application Express instance, as described in this section.
Application Level: Workspace administrators and developers can define Report Queries and Report Layouts. Report Queries and Report Layouts are stored under Shared Components and are not tied to a specific page.
Page/Region Level: Developers can edit the Report regions on specific pages to enable printing. This, in turn, enables end users to print regions as reports in various formats. See "Configuring Classic Report Region Print Attributes" in Oracle Application Express Application Builder User's Guide.
Tip:
If you are running Oracle Application Express with Oracle Database 11g Release 1 (11.1), you must enable network services to use report printing. See "Enabling Network Services in Oracle Database 11g" for your configuration scenario in Oracle Application Express Installation Guide.Configuring Report Printing in a Full Development Environment
Configuring Report Printing Settings in a Runtime Environment
Determining Report Printing Settings in a Runtime Environment
To configure the printing of reports in a full development environment:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
Scroll down to Report Printing:
For Printer Server:
Standard - This is the default setting. Standard Support enables you to print report regions and report queries using either the built-in templates provided with Oracle Application Express or other XSL-FO compatible formats you provide. This setting does not support RTF (rich text format).
Standard provides declarative formatting of report regions and report queries with basic control over page attributes, including orientation, size, column heading formats, page header, and page footer.
Advanced (requires Oracle BI Publisher) - This option requires a valid license of Oracle BI Publisher (also known as Oracle XML Publisher). Advanced Support provides you with all the capabilities of the Standard setting plus the ability to define RTF-based report layouts developed using the BI Publisher Word Template Builder.
See Also:
PDF Printing in Application Express to learn more about installing and configuring Oracle BI Publisher. Go to:http://www.oracle.com/technology/products/database/application_express/html/configure_printing.html
For Print Server Protocol, select the protocol that the print server uses.
For Print Server Host Address, specify the host address of the print server engine.
For Print Server Port, define the port of the print server engine. By default, this is set to 8888 when the report server is installed.
For Print Server Script, define the script that is the print server engine. The default setting is:
/xmlpserver/convert
Click Apply Changes.
To configure report printing settings in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000
Run the following statement:
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
END;
For a description of available parameters, see Table 2-5.
Table 2-5 Report Printing Parameters in Runtime Environment
| Parameter Name | Description |
|---|---|
|
|
Specify either standard support or advanced support. Advanced support requires an Oracle BI Publisher license. Valid values include:
|
|
|
Valid values include:
|
|
|
Specifies the host address of the print server converting engine, for example, |
|
|
Defines the port of the print server engine, for example |
|
|
Defines the script that is the print server engine, for example: /xmlpserver/convert |
See Also:
"SET_PARAMETER Procedure" in Oracle Application Express Application Builder User's GuideTo determine report printing settings in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_040000
Run the following statement:
SELECT
APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME)
FROM DUAL;
For a description of available parameters, see Table 2-5.
See Also:
"GET_PARAMETER Function" in Oracle Application Express Application Builder User's GuideInstance administrators can configure the workspace sizes available when users request:
a new workspace and schema
additional space for an existing workspace
To configure workspace size options:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Instance Settings.
Scroll down to New Workspace Request Size and Workspace Change Request Size. Specify the following:
Size in Megabytes - Edit the default numbers to change the size options.
Display - Select Yes for all the size options you want to appear in the select list for workspace size.
Default - Select the default value to appear in the storage field for workspace and change requests.
Click Apply Changes.
See Also:
"Enabling Auto Extend Tablespaces"Inactive workspaces consume valuable storage space and degrade system performance. By enabling Workspace Purge Settings, you can configure Oracle Application Express to purge inactive workspaces.
If a workspace is designated as inactive, a notification email is sent to each workspace administrator indicating that the workspace will be purged in a specific number of days. The workspace administrator can prevent the workspace from being purged by following an embedded link and following the online instructions.
See Also:
"Configuring Email", "Deleting Mail Log Entries", "Sending Email from an Application" in Oracle Application Express Application Builder User's GuideTo purge inactive workspaces:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Instance Settings, click Workspace Purge Settings.
The Workspace Purge Settings page appears.
From Enabled, select Yes to enable the workspace purge process. Select No to disable the workspace purge process.
From Language, select the language of the text of emails sent to workspace administrators of inactive workspaces. Note that only one language can be selected for each instance.
For Application Express Instance URL, enter the URL to the Oracle Application Express instance, inclusive of the DAD and trailing slash.
For Application Express Images URL, enter the URL to the Oracle Application Express images directory, inclusive of the trailing slash.
For Purge Administration Email Address, enter the email address (or From address) from which emails are sent to workspace administrators.
For Send Summary Email To, enter a list of email addresses separated by commas. Recipients will receive a daily email summary of the purge process.
For Days Until Purge, enter the number of days before a workspace is physically purged. For example, entering 10 means a workspace will be purged 10 days after it is added to the inactive list.
For Reminder Days in Advance, enter the number of days before the purge date to send a reminder email to workspace administrators. Reminder email criteria includes:
The workspace is on the inactive list
There has been no activity in the workspace
The workspace administrator has not chosen to follow the link in the email to prevent the workspace from being purged
For Days Inactive, enter the number of days of inactivity before a workspace is classified as inactive. Inactivity includes not logging into the workspace and the no runtime activity of any application in the workspace.
For Grace Period (Days), enter the number of days for the grace period. The grace period starts after workspace administrators click the link in the email to not have their workspace purged. If there is no activity during the grace period, the workspace will be added back to the list of inactive workspaces.
For Maximum Execution Time (Hours), enter the number limiting the number of hours that the purge process may execute per run of the workspace purge job.
For Maximum Number of Workspaces, enter the maximum number of workspaces to be purged per run of the workspace purge job.
For Maximum Number of Emails, enter the maximum number of reminder emails and workspace inactive emails to be send per run of the workspace purge job.
Click Apply Changes.
Instance administrators manage the theme repository for an entire Oracle Application Express instance. Only an Instance administrators can add or delete a theme from the repository.
When you create a public theme, you add it to the theme repository. Public themes are available when you create an application or when you create a theme for an existing application.
See Also:
"Managing Workspace Themes" in Oracle Application Express Application Builder User's GuideTo add a theme to the Theme repository:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Shared Components, click Public Themes.
The Public Themes page appears.
Select Create.
For Workspace, select a workspace and click Next.
For Application, select an application and click Next.
For Theme, select a theme and click Next.
For Name, specify the following:
Theme Number - Enter a number that uniquely identifies a theme within a workspace.
Theme Name - Enter a name for the workspace theme.
Description - Enter a description.
Click Next.
Click Create Public Theme.
To delete a public theme:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Shared Components, click Public Themes.
The Public Themes page appears.
Select the theme to be deleted.
Click Delete.
You cannot edit a public theme directly. To modify a public theme, you must create a new application using the theme, modify it, and then manually add it to the theme repository.
To modify a public theme:
Create an application using the theme you want to modify. See "Creating an Application" in Oracle Application Express Application Builder User's Guide.
Modify the theme. See "Editing a Theme" in Oracle Application Express Application Builder User's Guide.
Delete the existing public theme. See "Deleting a Public Theme".
Add the modified theme to the theme repository. See "Adding a Public Theme to the Theme Repository".
You export a theme in the same way you export any related application files. Exporting a public theme involves the following steps:
Create an application using the theme. See "Creating an Application" in Oracle Application Express Application Builder User's Guide.
Export the application. See "Exporting an Application" in Oracle Application Express Application Builder User's Guide.
Import the exported file into the target Oracle Application Express instance. See "Importing an Application or Page" in Oracle Application Express Application Builder User's Guide.
Install the exported file from the Export Repository. See "Installing Export Files" in Oracle Application Express Application Builder User's Guide.
A session is a logical construct that is used to establish persistence (or stateful behavior) across page views. Each session is assigned a unique ID, which the Application Express engine uses to store and retrieve an application's working set of data (or session state) before and after each page view. An automatic process clears sessions older than 24 hours every eight hours. Instance administrators can also purge them manually.
An Instance administrator can view session state statistics and purge the session state on the Session State page.
See Also:
"Managing Session State" in Oracle Application Express Application Builder User's GuideBefore purging sessions, Instance administrators can use the Recent Sessions page to first view a listing of recent sessions and then drill down on session details.
To purge sessions by age:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Meta Data, click Session State.
The Session State page appears.
Click Recent Sessions, with drill down to session details.
On the Recent Sessions page, you can:
Click a session number to view additional details.
Click Purge Sessions to delete the displayed sessions.
Using the Purge Session page, Instance administrators can purge sessions by age.
To view specific session details:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Meta Data, click Session State.
The Session State page appears.
Click Purge Sessions, by age.
On the Purge Sessions page, specify:
The maximum number of sessions to be purged
The age of sessions to be purged
To view a report of session statistics, click Count Sessions.
To purge the selected sessions, click Purge Sessions.
On the Session State Statistics page, Instance administrators can view statistics about current sessions before purging.
To view session state statistics:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Meta Data, click Session State.
The Session State page appears.
Select Session State Statistics.
Click Purge Sessions to delete the current sessions.
Instance administrators can manage email sent from applications by monitoring email messages in the mail queue and Mail Log.
To monitor messages in the mail queue:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Meta Data, click Mail Queue.
The Mail Queue page appears.
To send email messages, click Send All Mail.
To delete email messages, select the messages to be deleted and click Delete.
See Also:
"Configuring Email", "Deleting Mail Log Entries", "Sending Email from an Application" in Oracle Application Express Application Builder User's GuideInstance administrators can delete log entries.
The SQL Workshop logs maintain a history of recent commands and scripts run in the SQL Commands
To delete log files entries:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Logs and Files, click SQL Workshop logs.
Click one of the following:
Script File executions log entries
SQL Command Processor history entries
On the Clean up Logs page:
To delete entries by age, specify the age of the entries to be deleted and click Delete Entries.
To delete all entries, click Truncate Log.
See Also:
"Accessing a Command from Command History"in Oracle Application Express SQL Workshop GuidePage view activity logs track user activity for an application. Developers enable logging within their application using the Logging attribute on the Edit Application Definition page.
See Also:
"Editing the Application Definition" in Oracle Application Express Application Builder User's GuideThe Application Express engine uses two logs to track user activity. At any given time, one log is designated as current. For each rendered page view, the Application Express engine inserts one row into the log file. A log switch occurs at the interval listed on the Page View Activity Logs page. At that point, the Application Express engine removes all entries in the noncurrent log and designates it as current.
To truncate the activity logs manually:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Logs and Files, click Page View Activity Logs, with option to truncate.
The Page View Activity Logs page appears.
Click Truncate Logs.
Click either Truncate Log 1 or Truncate Log 2.
See Also:
"Viewing Workspace Dashboards"The Developer Activity Log tracks changes to applications within an individual workspace. Log entries older than one month are automatically deleted.
To delete Developer Activity Log entries:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Logs and Files, click Developer Activity Logs, with option to delete entries.
The Developer Activity Log page appears.
On the Developer Activity Log page, click Manage.
Specify the age of the entries to be deleted and click Delete Entries.
See Also:
"About the Developer Activity Dashboard" for information about the Developer Activity LogThe External Clicks Log counts clicks from an Oracle Application Express application to an external site. You can implement this functionality using the APEX_UTIL.COUNT_CLICK procedure.
To delete click counting log entries:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Logs and Files, click External Click Counting Log, with option to truncate.
The External Click Counting Log page appears.
On the External Click Counting Log page, click Manage.
Specify the age of the entries to be deleted and click Delete Entries.
See Also:
"COUNT_CLICK Procedure" in Oracle Application Express API ReferenceThe Oracle Application Express Mail Log records the message header information and send date of successfully sent mail message.
To truncate the mail log:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Logs and Files, click Mail Log.
The Mail Log page appears.
This page displays as an interactive report. To customize the report, use the Search bar at the top of the page. See "Customizing Interactive Reports" in Oracle Application Express Application Builder User's Guide.
On the Mail Log page, click Truncate.
See Also:
"Configuring Email"This table records authentication events by developers and administrators accessing the Oracle Application Express environment and by end users of Oracle Application Express applications that use the built-in login APIs available to developers. Log entries are aged out of the log tables and purged periodically.
To truncate the Login Access log:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Logs and Files, click Login Access Log.
The Login Access Log page appears.
Click Manage.
On the Manage Login Access Log page, click Delete Entries.
Instance administrators can view a page showing which translated languages have been installed within the current development instance.
To view the list of installed translations:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Manage Meta Data, click Installed Translations.
The Installed Translations page appears. This page displays a list of languages and indicates if the translations have been loaded.
See Also:
"Managing Application Globalization" in Oracle Application Express Application Builder User's GuideAn 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 and the APEX_INSTANCE_ADMIN API. To learn more, see "APEX_INSTANCE_ADMIN" in Oracle Application Express API Reference.
Tip:
Websheets are not supported in an Oracle Application Express runtime environment.To install an exported application into a runtime installation, you must:
Export the workspace from the Application Express instance where the application was developed as described in "Exporting and Importing a Workspace".
Use SQL*Plus to import your workspace in to the runtime environment:
Connect as APEX_040000, SYS, SYSTEM, or any schema to which the role APEX_ADMINISTRATOR_ROLE has been granted.
Run the workspace import file.
If the workspace export file was created with a version of Oracle Application Express lower than 3.2, you must connect as APEX_040000.
Export and then import your application using SQL*Plus in to the runtime environment. See "Exporting an Application and Related Files" in Oracle Application Express Application Builder User's Guide.
Instance administrators can communicate with all users in an Oracle Application Express instance by creating login and system messages. Typically, administrators use a login message in conjunction with a system message to communicate with all system users, such as regarding privacy notices or access restrictions.
A login message displays on the Oracle Application Express login page. Instance administrators can create a login message using the Login Message section of the Messages page.
To create a login message:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Messages, click Define Login Message.
In Message, enter a message. The message can contain any text and can optionally include HTML formatting.
Click Apply Changes.
To disable a login message:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Messages, click Define Login Message.
For Login Message, select No Message.
Click Apply Changes.
System messages display on the Workspace home page, Application Builder home page, Application home page, SQL Workshop home page, and the Oracle Application Express Utilities page.
Instance administrators can create a system message using the System Message section of the Messages page.
Tip:
You can also access the Set System Message page by clicking Edit System Message icon on the Instance Administration home page.To create a system message:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Messages, click Define System Message.
For System Message, select Custom Message.
In Message, enter a message. The message can contain any text and can optionally include HTML formatting.
Click Apply Changes.
To disable a system message:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Messages, click Define System Message.
For System Message, select No Message.
Click Apply Changes.
The Site-Specific Tasks list is a list of links that appears on the Workspace home page or login page. If links are defined, a Site-Specific Tasks region appears. If no Site-Specific Tasks are defined, the region does not display. This feature enables Instance administrators to customize the Workspace home page for an entire development instance. Typical uses for the Site-Specific Tasks list include links to training, discussion forums, and user feedback applications.
To add a new task to a Site-Specific Tasks list:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Messages, click Site-Specific Tasks.
The Site-Specific Tasks page appears.
To create a new link, click Create.
On the Create/Edit Site-Specific Tasks page, you can specify the following:
Display Sequence - Indicate the relative order of this task within the list.
Display Location - Indicate the page on which the task should display (that is, the Workspace Login page or Workspace home page).
Task Name - Enter a name for this task.
Tasks Link - Enter the link target for this task using either a relative URL (for example, using f?p syntax) or an absolute URL (such as http://otn.oracle.com).
Displayed - Select Yes to display the task link.
Click Create.
See Also:
"Using f?p Syntax to Link Pages" in Oracle Application Express Application Builder User's GuideTo edit an existing task:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Messages, click Site-Specific Tasks.
The Site-Specific Tasks page appears.
Select the task name.
On the Create/Edit Site-Specific Tasks page, edit the appropriate attributes.
Click Apply Changes.
To delete an existing task:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Instance.
Under Messages, click Site-Specific Tasks.
The Site-Specific Tasks page appears.
Select the task name.
Click Delete.