3.3.3 Configuring Instance Settings

Control a variety of general settings for an Oracle Application Express development instance including configuring workspace provisioning behavior, storage, email, wallet information, report printing, Help menu, workspace size options, and application ID ranges.

Note:

To ensure the security and perfomance of your development environment, this functionality is not available in Application Express instances running in Oracle Cloud.

3.3.3.1 About Configuring Workspace Provisioning

The Instance administrator determines the amount of automation when provisioning (or creating) a workspace.

To determine how provisioning works, an Instance Administrator selects one of the following Provisioning Methods on the Instance Settings page:

  • Manual - An Instance administrator creates new workspaces and notifies the Workspace administrator regarding the Sign In credentials.

  • Request - Users request a workspace. Once an administrator approves the request, the user receives an email containing an email verification link. After the user clicks the email verification link, the workspace is created.

  • Automatic - Works similar to Request except requests are automatically approved with no administrator review required.

To enable users to request a workspace using a link on the Sign In page, the Instance administrator must choose either the Request or Automatic Provisioning Method. If the Provisioning Method is set to Manual, no link appears on the Sign In page.

Note:

An instance administrator must configure instance-level email in order for Oracle Application Express to send the emails required for the Request or Automatic Provisioning Methods.

3.3.3.2 Disabling Email Provisioning

Use Email Provisioning in conjunction with the Provisioning Method, Automatic, to disable workspace provisioning and send users a message.

Selecting Disabled for Email Provisioning enables you to display message to users that explains why workspace provisioning is disabled.

To disable email provisioning:

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

  5. In Message, enter a message that explains why email provisioning is disabled.
  6. Click Apply Changes.

3.3.3.3 Configuring Storage

Instance administrators can configure the following Storage options: require a new schema when requesting a workspace, auto extend tablespaces, automaticaly approve storage requests, or delete uploaded files in a specified number of days.

3.3.3.3.1 Requiring a New Schema

Control if a user requesting a workspace can select an existing schema or must request a new schema.

To require a new schema when creating a workspace:

  1. Sign 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. Click Apply Changes.

3.3.3.3.2 Enabling Auto Extend Tablespaces

Enable Auto Extend Tablespaces.

If Auto Extend Tablespaces is enabled, tablespaces provisioned with Oracle Application Express are created with a data file that is one tenth the requested size. The data file automatically extends up to the requested size. For example, if a user requests a 100 MB workspace, the initial size of the data file is 10 MB and automatically extends up to a maximum size of 100 MB.

To enable Auto Extend Tablespaces:

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

3.3.3.3.3 Enabling Bigfile Tablespaces

Enable support for bigfile tablespaces.

When a workspace is provisioned, Oracle Application Express creates the associated database user, tablespace, and data file. If Bigfile Tablespaces is enabled, tablespaces provisioned with Oracle Application Express are created as bigfile tablespaces. A bigfile tablespace is a tablespace with a single, but very large data file. Traditional smallfile tablespaces, in contrast, can contain multiple data files, but the files cannot be as large.

Tip:

Oracle does not recommend using bigfile tablespaces on platforms that do not support large file sizes and can limit tablespace capacity. Refer to your operating system specific documentation for information about maximum supported file sizes.

To enable bigfile tablespaces:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. For Bigfile Tablespaces, select Yes.
  6. Click Apply Changes.

See Also:

"Available Parameter Values" in Oracle Application Express API Reference to learn about the BIGFILE_TABLESPACES_ENABLED parameter

3.3.3.3.4 Enabling Encrypted Tablespaces

Enable support for encrypted tablespaces.

If Encrypted Tablespaces is enabled, tablespaces provisioned with Oracle Application Express are created as encrypted tablespaces using the Oracle database feature Transparent Data Encryption (TDE). TDE encrypts sensitive data stored in data files. To prevent unauthorized decryption, TDE stores the encryption keys in a security module external to the database.

To be able to exploit this feature in Application Express, an encryption wallet must be created and with a master encryption key set. Additionally, the encryption wallet must be open before provisioning a new Application Express workspace.

To enable Encrypted Tablespaces:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. For Encrypted Tablespaces, select Yes.
  6. Click Apply Changes.

See Also:

"Available Parameter Values" in Oracle Application Express API Reference to learn about the ENCRYPTED_TABLESPACES_ENABLED parameter

3.3.3.3.5 Enabling Automatic Approval of Storage Requests

Automatically enable the approval of storage requests up to the selected size.

To use this option, the workspace Provisioning Method must be set to Automatic. If the workspace Provisioning Method is set to Manual or Request then storage requests cannot be automatically approved.

To automatically enable the approve storage requests:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. For Automatically Approve Requests, select a value.
  6. Click Apply Changes.

3.3.3.3.6 Deleting Uploaded Files

Specify the number of days after which Oracle Application Express automatically deletes uploaded files. 

Use Delete Uploaded Files After (days) to specify the number of days after which Oracle Application Express automatically deletes uploaded files. Note this automatic deletion process applies to all workspaces in an Oracle Application Express instance. The types of files that are deleted include:

  • Application Export

  • CSS Export

  • Images Export

  • Page Export

  • Plug-in

  • Script Export

  • Spreadsheet / Text Data Import

  • Static Files Export

  • Themes

  • User Interface Defaults

  • Workspace Export

  • XML Data Import

To configure when export and import files are deleted:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. In Delete Uploaded Files After (days), enter the number of days after which Oracle Application Express deletes uploaded files.

    Enter a positive, whole number. If this setting is null, then no files are automatically deleted.

  6. Click Apply Changes.

Tip:

To view a summary of deleted files, see the Automatic File Delete Log. See "Monitoring Activity Across a Development Instance"

3.3.3.4 Configuring Email

To enable Oracle Application Express to send mail, an instance administrator must configure instance-level email settings.

Tip:

You can configure Oracle Application Express to automatically email users their login credentials when a new workspace request has been approved. See "About Specifying How Workspaces Are Created" and "Selecting a Workspace Provisioning Mode."

3.3.3.4.1 About Enabling Network Services

You must enable network services in Oracle Database 11g or later versions to send outbound mail, use Web services, or use PDF report printing in Oracle Application Express.

Enabling network services enables support for sending outbound mail in Oracle Application Express, use of Web services in Oracle Application Express, and PDF report printing.

By default, the ability to interact with network services is disabled in Oracle Database 11g Release 2 or later. Therefore, if you are running Oracle Application Express with Oracle Database 11g Release 2 or later, you must use the new DBMS_NETWORK_ACL_ADMIN package to grant connect privileges to any host for the APEX_200200 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.

See Also:

"Installing and Configuring Application Express and Oracle REST Data Services" in Oracle Application Express Installation Guide

3.3.3.4.2 Configuring Email in a Full Development Environment

An Instance administrator must configure Oracle Application Express to send mail in a full development environment.

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

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Scroll down to Storage.
  5. Under Email, edit the following:
    1. Application Express Instance URL - Specify the URL to this Application Express instance, including the trailing slash after the Database Access Descriptor or Context Root. This setting is used for system-generated emails. For example:

      https://www.example.com/apex/

    2. Application Express Images URL - Specify the full URL to the images directory of this Application Express instance, including the trailing slash after the images directory. This setting is used for system-generated emails..

      https://www.example.com/i/

    3. 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.
    4. SMTP Host Port - Defines the port the SMTP server listens to for mail requests. The default setting is 25.
    5. SMTP Authentication Username - If you enter a username, Oracle Application Express authenticates against it when sending emails. Prior to Oracle Database 11g Release 2 (11.2.0.2), only the SMTP authentication scheme "LOGIN" is supported. On newer database versions, all authentication schemes of UTL_SMTP are supported.
    6. SMTP Authentication Password - If you enter a password, Oracle Application Express authenticates against it when sending emails. Prior to Oracle Database 11g Release 2, Release 11.2.0.2, only the SMTP authentication scheme "LOGIN" is supported. On newer database versions, all authentication schemes of UTL_SMTP are supported.
    7. Use SSL/TLS - Beginning with Oracle Database 11g Release 2, Release 11.2.0.2, Application Express supports secure SMTP connections.

      Options include:

      • Yes - A secure connection with SSL/TLS is made before SMTP communication.

      • After connection is established - Oracle Application Express sends the SMTP command STARTTLS immediately after the connection is opened.

      • No - A non-secure connection is opened.

    8. Default Email From Address - Defines the from address for tasks that generate email, such as approving a provision request or resetting a password.
    9. Maximum Emails per Workspace - Defines the number of email messages that can be sent with the APEX_MAIL API per workspace per 24 hour period.
  6. Click Apply Changes.

3.3.3.4.3 Configuring Email in a Runtime Environment

An Instance administrator must configure Oracle Application Express to send mail 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
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
  2. Run the following statement:
    BEGIN
       APEX_INSTANCE_ADMIN.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
       COMMIT;
    END;

    Tip:

    For a description of email parameters, see "Configuring Email in a Full Development Environment."

  3. Once all parameters have been configured, validate the configuration:
    BEGIN
        APEX_INSTANCE_ADMIN.VALIDATE_EMAIL_CONFIG;
    END;

See Also:

"SET_PARAMETER Procedure" in Oracle Application Express API Reference

3.3.3.4.4 Determining Email Settings in a Runtime Environment

Determine email settings in 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
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
  2. Run the following statement:
    SELECT 
    APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME)
    FROM DUAL;
    

    Tip:

    For a description of email parameters, see "Configuring Email in a Full Development Environment."

See Also:

"GET_PARAMETER Function" in Oracle Application Express API Reference

3.3.3.5 Configuring Wallet Information

Configure wallet information (which store authentication and signing credentials) for an Oracle Application Express instance.

3.3.3.5.1 About SSL and Wallet Creation

A wallet is a password-protected container that stores authentication and signing credentials (including private keys, certificates, and trusted certificates) needed by SSL.

Secure Sockets Layer (SSL) is an industry standard protocol that uses RSA public key cryptography with symmetric key cryptography to provide authentication, encryption, and data integrity. When SSL is enabled, https displays in the URL.

You must create a wallet if you:

  • Call a SSL-enabled URL (for example, by invoking a Web service).

  • Create a region of type URL that is SSL-enabled.

  • Configure secure SMTP, by setting the Use SSL/TLS attribute to Yes.

  • Have applications with LDAP authentication schemes that are configured to use SSL with Authentication.

Overview of Creating a Wallet

To create a wallet:

  1. The database administrator must create a wallet on the Oracle Application Express database instance.

  2. The instance administrator configures the Wallet attributes on the Instance Settings page to specify the file system path to the wallet and the wallet password (if required).

See Also:

3.3.3.5.2 Configuring a Wallet in a Full Development Environment

Configure wallet settings a full development environment on the Instance Settings page.

To specify wallet settings in a full development environment:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Click Wallet.
  5. Under Wallet:
    1. Wallet Path - Enter the path on the file system where the wallet is located using the following format:
      file:directory-path

      See field-level Help for examples.

    2. Password - Enter the password needed to open the wallet. Select Check to confirm that you wish to change the wallet password to indicate that you have changed the password.
  6. Click Apply Changes.

3.3.3.5.3 Configuring a Wallet in a Runtime Environment

Configure wallet settings a runtime environment by starting SQL*Plus and running the following SQL statements.

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
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
  2. Run the following statement:
    BEGIN
        APEX_INSTANCE_ADMIN.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
        COMMIT;
    END;

    See the table that follows for a description of wallet parameters.

    Table 3-3 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 API Reference

3.3.3.5.4 Determining Wallet Settings in a Runtime Environment

Configure wallet settings in a runtime environment by starting SQL*Plus and running the following SQL statements.

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
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
  2. Run the following statement:
    SELECT 
    APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME) 
    FROM DUAL;
    

    For a description of wallet parameters, see Table 3-3.

See Also:

"GET_PARAMETER Function" in Oracle Application Express API Reference

3.3.3.6 Configuring Report Printing for an Instance

Enable end users to download and print reports in various formats, including PDF.

3.3.3.6.1 About Configuring Report Printing

Enable report printing by configuring printing settings at the instance level, application level, and page and region level.

To set up report printing functionality, you must configure the following printing settings:

  1. Instance Level: For full development environments, instance administrators must select a Print Server under Instance Settings, Report Printer. In runtime environments, 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: Developers can specify a Print Server at the application-level by editing the Print Server Type attribute on the Application Definition page. Alternatively, 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 enables end users to print regions as reports in various formats.

See Also:

"Printing Report Regions" in Oracle Application Express App Builder User’s Guide

3.3.3.6.2 Configuring Report Printing in a Full Development Environment

Configure the print server type for an instance by editing the Print Server Type attribute on the Instance Settings page.

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

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Click Report Printing.
  5. For Printer Server, select an option:
    • External (Apache FOP) - Select this option if you are using Apache FOP on an external J2EE server. This option enables you to use the basic printing functionality, which includes creating report queries and printing report regions using the default templates provided in Application Express and using your own customized XSL-FO templates.
    • Oracle BI Publisher - This option requires a valid license of Oracle BI Publisher (also known as Oracle XML Publisher). This option enables you to take report query results and convert them from XML to RTF format using Oracle BI Publisher. Select this option to upload your own customized RTF or XSL-FO templates for printing reports within Application Express.
    • APEX Office Print - Select this option if you are using APEX Office Print. This option enables you to use the basic printing functionality, which includes creating report queries and printing report regions using the default templates provided in Application Express.
    What appears next depends upon the selected Print Server.
  6. For External (Apache FOP) or Oracle BI Publisher, specify the following:
    1. Protocol - Select whether the print server uses HTTP or HTTPS protocol.
    2. Host Address - Specify the host address of the print server converting engine. By default, this is set to localhost.
    3. Port - Specify the host address of the print server converting engine. The default setting is 8888.
    4. Script - Defines the script that is the print server engine. The default setting is:
      /xmlpserver/convert
      
  7. For APEX Office Print, specify the following:
    1. Protocol - Select whether the print server uses HTTP or HTTPS protocol.
    2. Host Address - Specify the host address of the print server converting engine. By default, this is set to localhost.
    3. Port - Specify the host address of the print server converting engine. The default setting is 8888.
    4. Script - Defines the script that is the print server engine.
    5. API Key - If you are using APEX Office Print Cloud Server, enter the Print Server API Key. Do not enter an API Key if you running APEX Office Print locally.
  8. Print Timeout - Enter the number of seconds. This option defines the transfer timeout for communicating with the print server in seconds.
  9. Click Apply Changes.

Tip:

You can override the Print Server Type instance-level setting at the application-level by editing the Print Server Type attribute on the Application Definition page.

See Also:

3.3.3.6.3 Configuring Report Printing Settings in a Runtime Environment

Configure report printing settings in a runtime environment by starting SQL*Plus and running the following SQL statements.

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
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
  2. Run the following statement:
    BEGIN
        APEX_INSTANCE_ADMIN.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
        COMMIT;
    END;
    

    For a description of available parameters, see Table 3-4.

    Table 3-4 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

    • APEX_LISTENER

    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_PROTOCOL

    Valid values include:

    • http

    • https

    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 API Reference

3.3.3.6.4 Determining Report Printing Settings in a Runtime Environment

Determine 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
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
    • On UNIX and Linux:

      $ sqlplus /nolog
      SQL> CONNECT SYS as SYSDBA
      Enter password: SYS_password
      
  2. Run the following statement:
    SELECT 
    APEX_INSTANCE_ADMIN.GET_PARAMETER(PARAMETER_NAME)
    FROM DUAL;
    

See Also:

3.3.3.7 Configuring the Help Menu

Configure the target URL of the Help menu that displays in the upper right corner of the Oracle Application Express development environment.

By default, the Help menu in Oracle Application Express points to the current Oracle Application Express online documentation library. You can change the target URL under Instance Settings, Help.

To configure the Help menu:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Click Help.
  5. In Help URL, edit the URL.
    The URL defined here displays when users click the Help link from within Oracle Application Express.
  6. Click Apply Changes.

See Also:

"Using Oracle Application Express Documentation" in Oracle Application Express App Builder User’s Guide

3.3.3.8 Configuring Workspace Size Requests

Configure the size options available to users when they request a new workspace and schema or request additional storage for an existing workspace.

To configure workspace size options:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Under New Workspace Request Size, specify the following:
    1. Size in Megabytes - Edit the default numbers to change the size options.
    2. Display - Select Yes for all the size options you want to appear in the select list for workspace size.
    3. Default - Select the default value to appear in the storage field for workspace and change requests.
  5. Under Workspace Change Request Size, specify the following:
    1. Size in Megabytes - Edit the default numbers to change the size options.
    2. Display - Select Yes for all the size options you want to appear in the select list for workspace size.
    3. Default - Select the default value to appear in the storage field for workspace and change requests.
  6. Click Apply Changes.

3.3.3.9 Managing Application ID Range

Control the range for IDs of new database applications and Websheet applications.

You can separate ID ranges in large multi-instance installations to easily move workspaces between the instances and still keep their application IDs. To enable ID ranges, you must specify at least an ID Minimum.

To configure the application ID ranges:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Click Application ID Range and specify the following:
    • ID Minimum - Enter the lower range for database and Websheet application IDs.

    • ID Maximum - Enter the maximum range for database and Websheet application IDs.

  5. Click Apply Changes.

3.3.3.10 Configuring Background Jobs

Configure the Background Job Class and the Minimum Execution Cadence settings.

To configure Background Jobs settings:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Instance Settings.
  4. Click Application ID Range, specify the following:
    • Background Job Class - Identify the DBMS_SCHEDULER job class for Automation, REST Data Source Synchronization, and Report Notification jobs to run in. This attribute enables you to assign Data Loading jobs to a specific Resource Manager Consumer group. If not set, the job class SYS.DEFAULT_JOB_CLASS will be used. To view an example, see item Help.

    • Minimum Execution Cadence (Minutes) - Identify the minimal execution cadence (in minutes) for Automation and REST Data Source Synchronization jobs.

  5. Click Apply Changes.

Note:

"Job Classes" in Oracle Database Administrator’s Guide