Skip Headers
Oracle® Application Express Administration Guide
Release 4.0

Part Number E15521-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF · Mobipocket

Configuring Workspace Preferences

Workspace administrators can configure the following preferences for the current workspace, including login controls, support for Websheets, Application Builder, SQL Workshop, and Team Development as well as enable support for PL/SQL editing.

Topics:

Enabling Account Login Controls for a Workspace

There are two different ways to configure login controls:

  • An Instance administrator enables account login controls for all Application Express accounts in all workspaces across a development instance.

    If your Instance administrator configures these preferences for an instance, those settings display as the defaults for all workspaces. See "Enabling Login Controls for All Workspaces".

  • If the Instance administrator does not enable login controls across an entire instance, then each Workspace administrator can enable the following controls on a workspace-by-workspace basis:

    • Require end-user account expiration and locking

    • Set up a maximum number of failed login attempts for end-user accounts

    • Set the password lifetime for end-user accounts, that is, the number of days an end-user account password can be used before it expires

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

To enable login controls for a workspace:

  1. Log in to Oracle Application Express. See "Logging In to Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

    The Workspace home page appears.

  2. Click the Administration icon.

    The Administration page appears.

  3. Click Manage Service.

  4. Click Set Workspace Preferences.

  5. Under Account Login Control:

    1. Account Expiration and Locking - Click Enable.

      If you select Enable, end-user account passwords will expire after a configurable time period and accounts will be locked after a configurable number of authentication failures. Account passwords can be set to expire after the first use.

      If your Instance administrator set the Require User Account Expiration and Locking preference to Yes, this preference defaults to Enable and you cannot update it.

    2. Maximum Login Failures Allowed - Enter a positive integer for the maximum number of consecutive unsuccessful authentication attempts allowed before an end-user account is locked. If you do not specify a value in this field, the instance-level setting for Maximum Login Failures Allowed is used.

    3. End User Account Lifetime (days) - Enter a positive integer for the maximum number of days an end-user account password may be used before the account expires. If you do not specify a value in this field, the instance-level setting for Account Password Lifetime is used.

  6. Click Apply Changes.

Enabling Application Builder Development

To enable Application Builder:

  1. Log in to Oracle Application Express. See "Logging In to Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

    The Workspace home page appears.

  2. Click the Administration icon.

    The Administration page appears.

  3. Click Manage Service.

  4. Click Set Workspace Preferences.

  5. Scroll down to Application Builder.

  6. For Enable Application Builder, select Yes. To disable Application Builder, select No.

  7. Click Apply Changes.

Tip:

These settings can be overridden by an Instance administrator. See "Managing Component Availability".

Enabling SQL Workshop

To enable SQL Workshop:

  1. Log in to Oracle Application Express. See "Logging In to Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

    The Workspace home page appears.

  2. Click the Administration icon.

    The Administration page appears.

  3. Click Manage Service.

  4. Click Set Workspace Preferences.

  5. Scroll down to SQL Workshop.

  6. For Enable SQL Workshop, select Yes. To disable SQL Workshop, select No.

  7. Click Apply Changes.

Tip:

These settings can be overridden by an Instance administrator. See "Managing Component Availability".

Disabling PL/SQL Program Unit Editing for a Workspace

By default, developers can change and compile PL/SQL source code when browsing database procedures, packages, and functions in SQL Workshop Object Browser. Workspace administrators can disable PL/SQL program unit editing by selecting Do not allow PL/SQL program unit editing on the Preferences page.

To disable PL/SQL program unit editing:

  1. Log in to Oracle Application Express. See "Logging In to Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

    The Workspace home page appears.

  2. Click the Administration icon.

    The Administration page appears.

  3. Click Manage Service.

  4. Click Set Workspace Preferences.

  5. Scroll down to SQL Workshop.

  6. Under PL/SQL Editing, select one of the following:

    • Allow PL/SQL program unit editing

    • Do not allow PL/SQL program unit editing

    If you select Do not allow PL/SQL program unit editing, developers can still create and replace PL/SQL program units using scripts or SQL Commands.

  7. Click Apply Changes.

Enabling Team Development

To enable Team Development:

  1. Log in to Oracle Application Express. See "Logging In to Oracle Application Express" in Oracle Application Express Application Builder User's Guide.

    The Workspace home page appears.

  2. Click the Administration icon.

    The Administration page appears.

  3. Click Manage Service.

  4. Click Set Workspace Preferences.

  5. Scroll down to Team Development.

  6. For Enable Team Development, select Yes. To disable Team Development, select No.

  7. Click Apply Changes.