3.3 Managing Feature Configuration

Use the Feature Configuration page to configure the Application Development settings, Application Installation Options, SQL Workshop functionality, database and activity monitoring, RESTful service, service requests, and Team Development.

3.3.1 Configuring Application Development Settings

Configure Application Development settings including: Allow PL/SQL Program Unit Editing, Create demonstration objects in new workspaces, and Number of backups per application.

3.3.1.1 Disabling PL/SQL Program Unit Editing for an Instance

Control if PL/SQL program unit editing is available in an instance.

By default, developers can change and compile PL/SQL source code when browsing database procedures, packages, and functions in Object Browser. Instance administrators can control if PL/SQL program unit editing is available on an Oracle APEX instance.

To disable PL/SQL program unit editing:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Application Development section.
  5. For Allow PL/SQL Program Unit Editing, select No.
  6. Click Apply Changes.

3.3.1.2 Enabling the Creation of Demonstration Objects in New Workspaces

Enable the creation of demonstration applications and demonstration database objects when creating new workspaces.

When creating a new workspace, an Instance administrators can create demonstration objects by enabling the Create demonstration objects in new workspaces attribute. Setting this attribute to Yes creates demonstration applications and demonstration database objects in new workspaces.

To enable the creation of demonstration database objects in a new workspace:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Application Development section.
  5. For Create demonstration objects in new workspaces, select Yes to include demonstration applications and demonstration database objects when creating new workspace. To disable the creation of demonstration applications, select No
  6. Click Apply Changes.

3.3.1.3 Configuring the Number of Application Backups

Configure the number of application backups.

Backups provide a simple means for developers to recover applications that may have been unexpectedly modified or deleted. Older backups are deleted during daily maintenance to make room for new ones. A value of null or zero (0) disables the automated backup feature. No more than 30 backups are kept per application.

To configure the number of application backups:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Application Development section.
  5. For Number of backups per application, enter the maximum number of backups to keep per application. Enter a value of null or zero (0) to disable automated backup.
  6. Click Apply Changes.

See Also:

3.3.2 Configuring SQL Workshop

Configure basic SQL Workshop behavior for an instance.

Instance administrators can configure SQL Workshop behavior for an instance.

To configure SQL Workshop:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the SQL Workshop section.
  5. Under SQL Workshop, configure the following attributes described in the following table:
    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. Run SQL scripts in 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 SQL command processor.

    SQL Scripts Maximum Script Size in bytes

    Identify the maximum size of a SQL script used within the SQL Workshop.

    Enable Transactional SQL Commands

    Enable Transactional SQL Commands for the entire instance. Enabling this feature permits users of SQL Commands to issue multiple SQL commands within the same physical database transaction. Select Yes or No.

    Maximum File size for Data Loading in bytess

    Provide the overall maximum file size for SQL Workshop Data Loading. Note that smaller limits exist for XML and XSLX files as well as for JSON files on Oracle Database 11.2 and 12.1. This setting configures the overall file size limitation for all file types.

    Data Loading Job Class

    Identify the DBMS_SCHEDULER Job Class for SQL Workshop Data Loading jobs. This setting enables you to assign Data Loading jobs to a specific Resource Manager Consumer group. If not set, the job class SYS.DEFAULT_JOB_CLASS is used.

    To see an example, see field-level Help. For more information on job classes, see the Oracle Database Administrator’s Guide.

  6. Click Apply Changes.

See Also:

3.3.3 Configuring Monitoring

Configure monitoring including: Database Monitoring (SQL Workshop), Application Activity Logging, Web Service Activity Logging, and Web Service Activity Logging.

3.3.3.1 Enabling Database Monitoring

Enabling database monitoring in SQL Workshop.

Before you can access the Database Monitoring page in SQL Workshop, an Instance administrator must enable database monitoring. See Monitoring the Database in Oracle APEX SQL Workshop Guide

Note:

Only users having a database user account that has been granted a DBA role can access the Database Monitor page.

Setting Enable Database Monitoring to Yes enables monitoring within SQL Workshop.

To enable database monitoring:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Monitoring section.
  5. For Enable Database Monitoring, select Yes.
  6. Click Apply Changes.

3.3.3.2 Enabling Application Activity Logging

Configure application activity logging for all applications on the instance.

To configure application activity logging:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Monitoring section.
  5. For Application Activity Logging, select one of the following:
    • Use Application Settings (default) - Use the Logging attribute of each application to determine if activity is logged.

    • Never - Disable activity logging for all applications in the instance.

    • Always - Enable activity logging for all applications in the instance.

  6. Click Apply Changes.

3.3.3.3 Enabling Web Service Activity Logging

Configure web service activity logging for all workspaces on the instance.

Note:

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

To configuring web service activity logging:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Monitoring section.
  5. For Web Service Activity Logging, select one of the following:
    • Use Application Settings (default) - Use the Web Service Logging attribute of each workspace to determine if activity is logged.

    • Never - Disable web service activity logging for all workspaces in the instance.

    • Always - Enable web service activity logging for all workspaces in the instance.

  6. Click Apply Changes.

3.3.3.4 Enabling Application Tracing

Control application tracing at the instance-level.

Note:

To ensure the security and performance of your development environment, this functionality is not available in Oracle APEX instances running in Oracle Cloud.
Instance administrators can control whether developers or users can generate database trace files simply by specifying &p_trace=YES on the URL when displaying a page. The ability to generate a trace file is already controlled if Debug is enabled for the application.

To configure application tracing

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Scroll down to Monitoring.
  5. From Enable Application Tracing, select one of the following:
    • Yes - Any application which has Debug enabled can also generate a server-side database trace file for a page using &p_trace=YES on the URL.

    • No - Tracing cannot be enabled for any application on the instance. If someone attempts to run an application with &p_trace=YES in the URL, the page renders but the request to generate the SQL trace file is silently ignored.

  6. Click Apply Changes.

See Also:

3.3.4 Enabling RESTful Services for an Instance

Controls the ability to create and access RESTful Services mapped to SQL and PL/SQL.

To enable RESTful Services:

  1. Sign in to APEX Administration Services.
  2. Click Sign in to Oracle APEX.
  3. Click Manage Instance.
  4. Under Instance Settings, click Feature Configuration.
  5. Locate the REST section.
  6. Under REST, edit the following attributes:
    Attribute Description

    Enable RESTful Services

    Controls the ability to create and access RESTful Services mapped to SQL and PL/SQL.

    Swagger UI URL

    Defines a URL pointing to the SWAGGER UI 2.0+ server used by the ORDS REST Workshop when generating documentation for a module. If a URL is specified, the URI to the web service's swagger documentation is passed to the Swagger UI server. If a there is no URL specified, raw JSON is produced.

    Note: In order to generate the documentation the Swagger UI server must be able to reach the referenced web service URI. When using a third party Swagger UI service, review its privacy policy to understand how information it collects may be used and shared.

  7. Click Apply Changes.

3.3.5 Enabling Service Requests

Determine if workspace administrators to make service requests from Workspace Administration.

Note:

To ensure the security and performance of your development environment, this functionality is not available in Oracle APEX instances running in Oracle Cloud.
Service Requests include the ability to request a new schema, request storage, or request termination of their workspace.

To enable service requests:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Workspace Administration section.
  5. For Enable Service Requests, select Yes.
  6. Click Apply Changes.

See Also:

Managing Requests

3.3.6 Configuring Team Development for New Workspaces

Configure the following Team Development settings for new workspaces: Enable Issue File Repository, Maximum Issue File Size, Enable Feedback File Repository, and Maximum Feedback File Size.

These attributes only impact Team Development when creating new workspaces. These settings do not affect existing workspaces.

To configure Team Development settings for new workspaces:

  1. Sign in to APEX Administration Services.
  2. Click Manage Instance.
  3. Under Instance Settings, click Feature Configuration.
  4. Locate the Team Development section.
  5. Configure the following:
    1. Enable Issue File Repository - Specify whether to enable file upload on the Issues page to the Team Development central file repository:
      • Yes - Select Yes to enable file upload for Issues in Team Development.

      • No - Select No to disable file upload for Issues in Team Development.

    2. Maximum File Size (in MB) - Select the maximum file size for any file uploaded for Issues in the Team Development file repository. The default value is 15 MB.
    3. Enable Feedback File Repository - Specify whether to enable file upload for User Feedback within Team Development:
      • Yes - Select Yes to allow files to be uploaded into the Feedback repository in a new workspace.

      • No - Select No to disable file upload into the Feedback repository in a new workspace.

    4. Maximum Feedback File Size (in MB) - Select the maximum file size for any file upload for User Feedback into the Feedback file repository. The default value is 15 MB.
  6. Click Apply Changes.

See Also: