Previous
Previous 		 Next
Next

Configuring Instance Settings

Instance settings control Oracle Application Express configuration and apply to all workspaces within the current Oracle Application Express instance.

Topics:


See Also:

"Creating Workspaces"

Enabling Self Service Workspace Provisioning

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:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

  4. 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).

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

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


See Also:

"Disabling Email Provisioning", "Configuring Email", and "Managing Workspace and Change Requests"

Disabling Email Provisioning

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:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

  4. From Email Provisioning, select Disabled.

    Selecting Disabled completely disables workspace provisioning when provisioning with Email Verification.

  5. In Message, enter a message that explains why email provisioning is disabled.

  6. Click Apply Changes.

Configuring Storage Settings

Instance administrators can require a new schema when user's request a new workspace or auto extend tablespaces.

Requiring a New Schema

To require a new schema when creating a workspace:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

  4. Scroll down to Storage.

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

  6. Auto Extend Tablespaces, select Yes or No.

  7. Click Apply Changes.

Enabling Auto Extend Tablespaces

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:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

  4. Scroll down to Storage.

  5. To enable Auto Extend Tablespaces, select Yes.

  6. Click Apply Changes.

Configuring Email

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

Topics:


See Also:

"Managing the Mail Queue" and "APEX_MAIL" in Oracle Application Express API Reference

Configuring Email in a Full Development Environment

To configure Oracle Application Express to send mail in a full development environment:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

  4. Under Email, enter the following:

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

    2. SMTP Host Port - Defines the port the SMTP server listens to for mail requests. The default setting is 25.

    3. Administration Email Address - Defines the from address for administrative tasks that generate email, such as approving a provision request or resetting a password.

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

  5. Click Apply Changes.

Configuring Email in a Runtime Environment

To configure Oracle Application Express to send mail in a runtime environment:

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

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba

    • On UNIX and Linux:

      $ sqlplus /nolog
connect sys as sysdba

    When prompted enter the appropriate password.

  2. Run the following statement:

    ALTER SESSION SET CURRENT_SCHEMA = APEX_040000

  3. Run the following statement:

    BEGIN
   APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
END;

    For a description of email parameters, see Table: Email Parameters.

    Email Parameters

    Parameter Name Description

    SMTP_FROM

    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:

    someone@somewhere.com

    SMTP_HOST_ADDRESS

    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

    SMTP_HOST_PORT

    Defines the port the SMTP server listens to for mail requests.

    Default setting:

    25


See Also:

"SET_PARAMETER Procedure" in Oracle Application Express API Reference

Determining Email Settings in a Runtime Environment

To determine email settings in runtime environment:

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

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba

    • On UNIX and Linux:

      $ sqlplus /nolog
connect sys as sysdba

    When prompted enter the appropriate password.

  2. Run the following statement:

    ALTER SESSION SET CURRENT_SCHEMA = APEX_040000

  3. Run the following statement:

    SELECT 
APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME)
FROM DUAL;

    For a description of email parameters, see Table: Email Parameters.


See Also:

"GET_PARAMETER Function" in Oracle Application Express API Reference

Configuring Wallet Information

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

Topics:

Creating a Wallet

To create a wallet:

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

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

Configuring a Wallet in a Full Development Environment

To specify wallet settings in a full development environment:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

  4. Scroll down to Wallet.

  5. In Wallet, enter the path on the file system where the wallet is located using the following format:

    file:directory-path

  6. If a password is required to open the wallet:

    1. Enter a password in the Wallet Password field.

    2. Select Check to confirm that you wish to change the wallet password.

  7. Click Apply Changes.

Configuring a Wallet in a Runtime Environment

To specify wallet settings in a runtime environment:

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

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba

    • On UNIX and Linux:

      $ sqlplus /nolog
connect sys as sysdba

    When prompted enter the appropriate password.

  2. Run the following statement:

    ALTER SESSION SET CURRENT_SCHEMA = APEX_040000

  3. Run the following statement:

    BEGIN 
    APEX_INSTANCE_ADMIN.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
END;

    For a description of wallet parameters, see Table: Wallet Parameters.

    Wallet Parameters

    Parameter Name Description

    WALLET_PATH

    The path to the wallet on the file system, for example:

    file:/home/<username>/wallets

    WALLET_PWD

    The password associated with the wallet.


See Also:

"SET_PARAMETER Procedure" in Oracle Application Express Application Builder User's Guide

Determining Wallet Settings in a Runtime Environment

To determine wallet settings in a runtime environment:

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

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba

    • On UNIX and Linux:

      $ sqlplus /nolog
connect sys as sysdba

    When prompted enter the appropriate password.

  2. Run the following statement:

    ALTER SESSION SET CURRENT_SCHEMA = APEX_040000

  3. Run the following statement:

    SELECT 
APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME) 
FROM DUAL;

    For a description of wallet parameters, see Table: Wallet Parameters.


See Also:

"GET_PARAMETER Function" in Oracle Application Express Application Builder User's Guide

Configuring Report Printing

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

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

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

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

Topics:

Configuring Report Printing in a Full Development Environment

To configure the printing of reports in a full development environment:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

  4. Scroll down to Report Printing:

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

  6. For Print Server Protocol, select the protocol that the print server uses.

  7. For Print Server Host Address, specify the host address of the print server engine.

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

  9. For Print Server Script, define the script that is the print server engine. The default setting is:

    /xmlpserver/convert

  10. Click Apply Changes.

Configuring Report Printing Settings in a Runtime Environment

To configure report printing settings in a runtime environment:

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

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba

    • On UNIX and Linux:

      $ sqlplus /nolog
connect sys as sysdba

    When prompted enter the appropriate password.

  2. Run the following statement:

    ALTER SESSION SET CURRENT_SCHEMA = APEX_040000

  3. Run the following statement:

    BEGIN
    APEX_INSTANCE_ADMIN.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
END;

    For a description of available parameters, see Table: Report Printing Parameters in Runtime Environment.

    Report Printing Parameters in Runtime Environment

    Parameter Name Description

    PRINT_BIB_LICENSED

    Specify either standard support or advanced support. Advanced support requires an Oracle BI Publisher license. Valid values include:

    • STANDARD

    • ADVANCED

    PRINT_SVR_PROTOCOL

    Valid values include:

    • http

    • https

    PRINT_SVR_HOST

    Specifies the host address of the print server converting engine, for example, localhost. Enter the appropriate host address if the print server is installed at another location.

    PRINT_SVR_PORT

    Defines the port of the print server engine, for example 8888. Value must be a positive integer.

    PRINT_SVR_SCRIPT

    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 Guide

Determining Report Printing Settings in a Runtime Environment

To determine report printing settings in a runtime environment:

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

    • On Windows:

      SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba

    • On UNIX and Linux:

      $ sqlplus /nolog
connect sys as sysdba

    When prompted enter the appropriate password.

  2. Run the following statement:

    ALTER SESSION SET CURRENT_SCHEMA = APEX_040000

  3. Run the following statement:

    SELECT 
APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME)
FROM DUAL;

    For a description of available parameters, see Table: Report Printing Parameters in Runtime Environment.


See Also:

"GET_PARAMETER Function" in Oracle Application Express Application Builder User's Guide

Configuring Workspace Size Options for Requests

Instance administrators can configure the workspace sizes available when users request:

To configure workspace size options:

  1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".

  2. Click Manage Instance.

  3. Under Instance Settings, click Instance Settings.

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

  5. Click Apply Changes.


See Also:

"Enabling Auto Extend Tablespaces"


Previous
Previous 		 Next
Next