22 Managing an Oracle Application Express Hosted Service

Creating a Site-Specific Tasks List

The Site-Specific Tasks list is a list of links that appears on the Workspace home 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 Oracle Application Express 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.

Topics in this section include:

• Adding a New Task

• Editing an Existing Task

• Deleting a Task

Managing Log Entries

Oracle Application Express administrators can delete log entries on the Logs page.

Topics in this section include:

• Deleting SQL Workshop Logs

• Deleting Page View Activity Log Entries

• Deleting Developer Activity Log Entries

• Deleting Click Counting Log Entries

• Deleting Mail Log Entries

• Deleting the Login Access Log

Managing Session State

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. Oracle Application Express administrators can also purge them manually.

An Oracle Application Express administrator can view session state statistics and purge the session state on the Session State page.

Topics in this section include:

• Purging Sessions by Age

• Viewing Session Details Before Purging

• Viewing Session Statistics Before Purging

Managing Mail

Oracle Application Express administrators can manage email sent from applications by monitoring email messages in the mail queue and Mail Log.

Topics in this section include:

• Viewing the Mail Queue

• Viewing the Mail Log

Viewing Installed Translations

Oracle Application Express administrators can view a page showing what translated languages have been installed within the current development instance.

To view the list of installed translations:

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

2. Click Manage Service.

3. Under Manage Service, click Installed Translations.

   The Installed Translations page appears, displaying a list of languages and indicating if the translations have been loaded.

Disabling PL/SQL Program Unit Editing for an Instance

By default, developers can change and compile PL/SQL source code when browsing database procedures, packages, and functions in Object Browser. As an Oracle Application Express 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:

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

2. Click Manage Service.

3. Under Manage Environment Settings, click Feature Configuration.

4. Locate the Application Development section.

5. For Allow PL/SQL Program Unit Editing, select No.

6. Click Apply Changes.

Disabling the Creation of Demonstration Applications in a New Workspace

When an Oracle Application Express administrator creates a new workspace, Oracle Application Express automatically creates a demonstration application within the workspace.

To disable the creation of demonstration applications:

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

2. Click Manage Service.

3. Under Manage Environment Settings, click Feature Configuration.

4. Locate the Application Development section.

5. For Create demonstration objects in new workspaces, select No.

6. Click Apply Changes.

Configuring SQL Workshop

As an Oracle Application Express administrator, you can use the attributes under SQL Workshop to configure basic SQL Workshop behavior.

To configure SQL Workshop:

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

2. Click Manage Service.

3. Under Manage Environment Settings, click Feature Configuration.

4. Under SQL Workshop, enter the attributes described in Table 22-1.

   Table 22-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.

   
   

5. Click Apply Changes.

Enabling Database Monitoring

Before you can access the Database Monitoring page, an Oracle Application Express administrator must enable database monitoring.

To enable database monitoring:

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

2. Click Manage Service.

3. Under Manage Environment Settings, click Feature Configuration.

4. Scroll down to Monitoring.

5. For Enable Database Monitoring, select Yes.

6. Click Apply Changes.

Configuring Security Settings

Oracle Application Express 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.

Topics in this section include:

• Turning Off Cookies Used to Populate the Login Form for Application Express

• Excluding Domains from Regions of Type URL and Web Services

• Enabling Login Controls for All Workspaces

• About Password Policies

• Configuring Password Policies

• Disabling Access to Oracle Application Express Administration Services

• Disabling Access to Oracle Application Express Internal Applications

• Restricting User Access by IP Address

BEGIN
    WWV_FLOW_API.SET_SECURITY_GROUP_ID(p_security_group_id=>10);
    WWV_FLOW_PLATFORM.SET_PREFERENCE( 
        p_preference_name => 'DISABLE_ADMIN_LOGIN',
        p_preference_value => 'N' );
end;
/

commit
/

Configuring Email Settings

To enable Oracle Application Express to send mail, an Oracle Application Express administrator must configure a email settings on the Instance Settings page.

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

To configure Oracle Application Express to send mail:

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

2. Click Manage Service.

3. Under Manage Environment 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.

5. Click Apply Changes.

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.

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 Oracle Application Express 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.

To specify wallet settings:

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

2. Click Manage Service.

3. Under Manage Environment 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 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 need to configure the printing settings:

1. Site Level: Oracle Application Express service administrators must specify the level of functionality (Standard or Advanced) for an entire Oracle Application Express instance, as described in this section. See "Setting Up Region Report Printing for an Instance"

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. See "About Report Queries".

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 Report Region Print Attributes".

Configuring Workspace Size Options for Requests

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

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

2. Click Manage Service.

3. Under Manage Environment Settings, click Instance Settings.

4. Scroll down to New Workspace Request Size and Workspace Change Request Size, specify the appropriate information:

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

Managing Login and System Messages

Oracle Application Express 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.

Topics in this section include:

• Managing a Login Message

• Managing a System Message

Determining the Application Express Engine Schema

A schema is a logical container for the database objects. Oracle Application Express administrators may need to perform certain actions within the Application Express engine schema. For example, in order for an Oracle Application Express administrator to have the ability to assign Oracle default schemas, the database administrator (DBA) must explicitly grant the privilege by running the APEX_SITE_ADMIN.UNRESTRICT_SCHEMA procedure within the Application Express engine.

To determine the current Application Express engine schema for your Oracle Application Express instance:

1. Use SQL*Plus to connect to the database.

2. Run the following query in a schema with DBA privileges (for example, SYSTEM).

   SELECT TABLE_OWNER FROM all_synonyms
   WHERE SYNONYM_NAME = 'WWV_FLOW' and OWNER = 'PUBLIC'
   

Understanding Oracle Default Schema Restrictions

When Oracle Application Express installs, the Oracle Application Express administrator does not have the ability to assign Oracle default schemas to workspaces. Default schemas (such as SYS, SYSTEM, and RMAN) are reserved by Oracle for various product features and for internal use. Access to a default schema can be a very powerful privilege. For example, a workspace with access to the default schema SYSTEM can run applications that parse as the SYSTEM user.

In order for an Oracle Application Express administrator to have the ability to assign Oracle default schemas to workspaces, the database administrator (DBA) must explicitly grant the privilege using SQL*Plus to run a procedure within the APEX_SITE_ADMIN_PRIVS package.

Topics in this section include:

• Granting the Privilege to Assign Oracle Default Schemas

• Revoking the Privilege to Assign Oracle Default Schemas

• Working with Restricted Schemas

EXEC FLOWS_030000.APEX_SITE_ADMIN_PRIVS.UNRESTRICT_SCHEMA(p_schema => 'SYSTEM');
COMMIT;

EXEC FLOWS_030000.APEX_SITE_ADMIN_PRIVS.RESTRICT_SCHEMA(p_schema => 'SYSTEM');
COMMIT;

EXEC FLOWS_030000.APEX_SITE_ADMIN_PRIVS.CREATE_EXCEPTION(p_schema => 'SYSTEM', p_workspace=> 'DBA_WORKSPACE');
EXEC FLOWS_030000.APEX_SITE_ADMIN_PRIVS.CREATE_EXCEPTION(p_schema => 'SYSTEM', p_workspace  => 'AUDITOR_WORKSPACE');
COMMIT;

EXEC FLOWS_030000.APEX_SITE_ADMIN_PRIVS.REMOVE_WORKSPACE_EXCEPTIONS(p_schema => 'SYSTEM');
COMMIT;

EXEC FLOWS_030000.APEX_SITE_ADMIN_PRIVS.REMOVE_WORKSPACE_EXCEPTIONS(p_workspace => 'AUDITOR_WORKSPACE');
COMMIT;

SET SERVEROUTPUT ON
EXEC FLOWS_030000.APEX_SITE_ADMIN_PRIVS.REPORT;

SELECT a.schema "SCHEMA",b.workspace_name "WORKSPACE" FROM WWV_FLOW_RESTRICTED_SCHEMAS a, WWV_FLOW_RSCHEMA_EXCEPTIONS b WHERE b.schema_id (+)= a.id;

About Workspace Provisioning

When an Oracle Application Express administrator creates a new workspace with a new schema, a new tablespace and datafile are created for that schema. The datafile for the new tablespace is managed by Oracle-managed files if Oracle-managed files is enabled.

Using Oracle-managed files simplifies the administration of the Oracle database and eliminates the need for the database administrator (DBA) to directly manage the operating system files that comprise the database. Using Oracle-managed files, the DBA specifies operations in terms of database objects rather than file names. The datafile for the new tablespaces are named according to the Oracle-managed files conventions. The placement of these files is determined by the database initialization parameter DB_CREATE_FILE_DEST.

If the Oracle-Managed Files is not enabled, the datafile is created in the same directory as the first datafile of the tablespace in which Oracle Application Express is installed.

Specifying a Provisioning Mode

As an Oracle Application Express administrator, you determine how the process of provisioning (or creating) a workspace works for your Oracle Application Express development instance.

In Manual provision mode, an Oracle Application Express 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 Service.

3. Under Manage Environment Settings, click Instance Settings.

4. Under Self Service, select a provisioning status:

   • Manual - An Oracle Application Express 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.

Creating a Workspace Manually

Oracle Application Express administrators can provision a workspace manually by running the Create Workspace Wizard.

To create a workspace manually:

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

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Create Workspace.

   The Create Workspace Wizard appears.

4. For Identify Workspace, enter a workspace name and description and click Next.For Identify Schema, specify whether you are re-using an existing schema or creating a new one.

   If you are using an existing schema:

   1. For Re-use existing schema, select Yes.

   2. Select a schema from the list.

   3. Click Next.

   If you creating a new schema:

   1. For Re-use existing schema, select No.

   2. Enter a schema name and password.

   3. Specify a space quota.

   4. Click Next.

5. For Identify Administrator, enter the Workspace administrator information and click Next.

6. Confirm your selections and click Create.

Managing Workspace to Schema Assignments

When users log in to Oracle Application Express, they log in to a shared work area called a workspace. Each workspace can have multiple associated schemas. By associating a workspace with a schema, developers in that workspace can:

• Build applications that interact with the database objects in that schema.

• Create new database objects in that schema.

Topics in this section include:

• Viewing the Existing Schema and Workspace Assignment

• Editing an Existing Schema and Workspace Assignment

• Associating Additional Schemas to a Workspace

• Creating a New Schema

Viewing a Pending Workspace Request on the Notifications List

The Notifications list on the Oracle Application Express Administration Services home page displays pending or approved workspace requests.

Figure 22-1 Notifications List

Description of "Figure 22-1 Notifications List"

To view workspace requests on the Notifications list:

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

2. On the right side of the Administration Services home page, review the Notifications list.

   The Notifications list displays a summary of total and pending workspace requests.

3. To view additional details, click the appropriate workspace request number.

Viewing Requests from the Workspace Requests Page

To view workspace requests from the Workspace Requests page:

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

2. Click Manage Workspaces.

3. Under Manage Requests, click Workspace Requests.

   The Workspace Requests page appears.

4. To filter the report, make a selection from the Status list and click Go.

5. To view request details, click the Edit icon for the appropriate request.

Approving or Declining a Pending Workspace Request

To approve or decline a pending workspace request:

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

2. Click Manage Workspaces.

3. Under Manage Requests, click Workspace Requests.

   The Workspace Requests page appears.

4. From the Status list, select Requested and click Go.

5. Locate a request to review.

6. To edit or review the request details, click the Edit icon. On the Provision Request page you can:

   • Edit the request and click Apply Changes.

   • Delete the request by clicking Delete.

7. Return to the Workspace Requests page.

8. To approve a request:

   1. Click Provision in the Actions column.

   2. On the Provisioning Administration page, click Approve.

   3. Review the email message.

   4. If needed, update the message and click Approve and Send Email.

      If you selected the Provisioning Status, Email Verification, an email containing a verification link is sent to the user. In order to create the workspace, the user must click the verification link to create the workspace. See "Specifying a Provisioning Mode".

9. To decline a request:

   1. Click Provision in the Actions column.

   2. On the Provisioning Administration page, click Decline.

   3. Review the email message.

   4. To add information, such as the reason for declining a request, update the message and then click Decline and Send Email.

      The email is sent to the user notifying them the request was declined.

Please contact administrator.

Changing the Status of an Existing Workspace Request

To change the status of an existing workspace request:

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

2. Click Manage Workspaces.

3. Under Manage Requests, click Workspace Requests.

   The Workspace Requests page appears.

4. To filter the report, make a selection from the Status list and click Go.

5. Locate a request to review.

6. Click the link in the Actions column.

   The Adjust Request page appears.

7. From the Project Status list, select a new status.

8. Click Apply Changes.

Deleting a Workspace Request

To delete a workspace request:

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

2. Click Manage Workspaces.

3. Under Manage Requests, click Workspace Requests.

   The Workspace Requests page appears.

4. From Status, select the type of request you want to delete.

5. Click the Edit icon for the request you want to delete.

6. On the Provision Request page, click the appropriate button:

   • If the request Status is Approved, click Terminate or Delete.

   • If the request Status is Declined, Requested, Terminated, or Accepted, click Delete.

7. Click Delete Request.

Viewing a Pending Change Request from the Notifications List

Oracle Application Express administrator can view existing workspace requests and change requests from the Notifications list on the Oracle Application Express Administration Services home page.

Figure 22-2 Notifications List

Description of "Figure 22-2 Notifications List"

To view change requests from the Notifications list:

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

2. On the right side of the Administration Services home page, review the Notifications list.

   The Notifications list displays a summary of total and pending change requests.

3. To view additional details, click the appropriate change request number.

   The appropriate Change Requests page appears.

Viewing a Change Request from the Workspace Utilization Report

To view pending requests from the Workspace Utilization Report:

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

2. Click Manage Workspaces.

3. Under Workspace Reports, click Workspace Details.

4. From the Workspace list, select the workspace and click Go.

   The Workspace Details page appears.

5. Scroll down to the Change Requests section.

Viewing Requests from the Change Requests Page

To view change requests from the Workspace Requests page:

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

2. Click Manage Workspace.

3. Under Manage Requests, click Change Requests.

4. From Status, select the type of requests you want to view and click Go.

Approving or Declining a Pending Change Request

To approve or decline a pending change request:

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

2. Click Manage Workspace.

3. Under Manage Requests, click Change Requests.

4. Locate the request and click View Request under the Action column.

   The View Change Request page appears. Note that the buttons that display depend upon the nature of the change request.

5. Select one of the following:

   • To approve a request for a schema, click Create Schema.

   • To approve a request for additional disk space, click Add Space.

   • To approve a request to terminate the service, click Terminate Service.

   • To deny a request, click Deny Request.

   • To delete a request and deny it, select Delete this request if denying? and then click Deny Request.

Creating New User Accounts

To create a new user account:

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

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Manage Developers and Users.

   The Manage Developers and Users page appears.

4. Click Create.

   The Create/Edit User page appears.

5. Under User Attributes, enter the appropriate information.

   Tip:

   To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark. See "About Field-Level Help".

6. Under Password, type a case-sensitive password for this account.

   If your organization has set up a password policy, be sure the password meets the requirements. See "About Password Policies".

7. Under Developer Privileges:

   • User is a developer - To add this user as a developer or Workspace administrator, select Yes. For end users, select No.

     Developers can create and modify applications and database objects as well as view developer activity, session state, workspace activity, application, and schema reports.

   • User is a workspace administrator - To add this user as a Workspace administrator, select Yes. For developers or end users, select No.

     In addition to having developer privileges, workspace administrators can create and edit user accounts, manage groups, alter passwords of users within the same workspace, and manage development services.

     Note:

     You create end users by adding them as users but not defining them as either developers or Workspace administrators, restricting their privileges.

8. Under Account Control:

   • Account Availability - Select Unlocked to enable a user to log in to this account. Select Unlocked to enable the account to be used.

   • Require Change of Password on First Use - Select Yes to require the user to change the password immediately after logging in with the current, temporary password.

     This rule applies to the use of this account for developers and Workspace administrators. It also applies to all users who use this account when logging in to developed applications.

   Tip:

   An Oracle Application Express administrator can configure these settings for an entire Oracle Application Express instance. See "Enabling Login Controls for All Workspaces".

9. Click Create User or Create and Create Another.

Editing an Existing User Account

To edit an existing user account:

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

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Manage Developers and Users.

4. Locate a user:

   • To narrow the list, select a workspace from the Workspace list and click Go.

   • To locate a specific user, type a user name or partial string in the Find User field and click Go.

   • To view all users, leave the Find User field blank and click Go.

5. To edit account details, select the user name.

   To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark. See "About Field-Level Help".

6. Make the appropriate changes.

7. Click Apply Changes.

   See Also:

   "Creating New User Accounts"

Deleting User Accounts

To delete a user account:

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

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Manage Developers and Users.

4. Locate a user:

   • To narrow the list, select a workspace from the Workspace list and click Go.

   • To locate a specific user, type a user name or partial string in the Find User field and click Go.

   • To view all users, leave the Find User field blank and click Go.

5. Select a user.

   The Create/Edit User page appears.

6. Click Delete User.

7. Confirm your selection and click OK.

Viewing Existing Workspaces

Use the Existing Workspaces page to view a report of existing workspaces, delete an existing workspace, or create a new workspace.

To view existing workspaces:

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

2. Click Manage Workspaces.

3. Under Workspace Reports, click Existing Workspaces.

   The Existing Workspaces page appears with a navigation bar at the top:

   • Search - To search for a workspace, enter a case insensitive query in the Search field and click Go.

   • Display - To change the number of workspaces that appear in the list, make a selection from the Display list and click Go.

4. To create a new workspace, click Create Workspace and follow the on-screen instructions.

5. To view workspace details, click the workspace name. See "About the Workspace Details Page".

About the Workspace Details Page

The Workspace Details page is divided into the following sections:

• Name. Displays high-level information about the workspace: ID, Short Name, and the First Schema Provisioned. To edit the workspace name, click Edit Attributes and follow the on-screen instructions.

• Schemas. Displays the default tablespace for each workspace schema.

  When users log in to Oracle Application Express, they log in to a shared work area called a workspace. Each workspace can have multiple associated schemas. By associating a workspace with a schema, developers can build applications that interact with the objects in that schema as well as create new database objects in that schema. To edit workspace to schema assignments, click Workspace to Schema Assignments. See "Managing Schemas".

• Privileges. Lists the database system privileges for each workspace schema.

• Role Privileges. Lists the database roles granted to each workspace schema.

• Table Utilization. Displays the tablespace used with each workspace schema.

• Applications. Lists all applications within the workspace.

• Developers. Lists all application developers within the workspace. To edit a developer, click Manage Application Developers. See "Managing Users in an Oracle Application Express Instance".

• Application Express Users. Lists all defined users within the workspace. To edit a user, click Manage Users. See "Managing Users in an Oracle Application Express Instance".

• Objects by Type. Lists objects used by the schemas in the workspace.

• Change Requests. Lists all change requests in an Oracle Application Express instance.

• User Activity. Lists user activity by date.

• Developer Activity. Lists developer activity by developer name and application.

Identifying Inactive Workspaces

The first step in determining if a workspace is inactive is to establish some basic rules. A common approach is to base the rules on the Oracle Application Express activity records found in the current Application Express engine schema.

The following DDL (data definition language) creates a table of all workspaces requested before June 28, 2004 but that have been inactive since June 10, 2004. In this example, inactivity is determined by checking a key within the Application Express engine schema for the most recent updates by each workspace.

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_030000;
CREATE TABLE ws_to_purge AS
 SELECT c.security_group_id, c.company_name, c.admin_email, c.request_date,
 SYSDATE last_updated_on, 'Y' ok_to_delete
   FROM wwv_flow_provision_company c
  WHERE
c.request_date <= to_date('20040628','YYYYMMDD') AND
     (  not exists
 (SELECT NULL /* Activity Log */
        FROM wwv_flow_activity_log l
       WHERE l.security_group_id = c.security_group_id
         AND l.time_stamp > to_date('20040610','YYYYMMDD'))
 )
    AND NOT EXISTS
     (SELECT NULL /* workspace applications */
        FROM wwv_flows f
       WHERE f.security_group_id = c.security_group_id
         AND f.last_updated_on > to_date('20040610','YYYYMMDD'))
    AND NOT EXISTS
     (SELECT NULL /* Pages */
        FROM wwv_flow_steps s
       WHERE s.security_group_id = c.security_group_id
         AND s.last_updated_on > to_date('20040610','YYYYMMDD'))
    AND NOT EXISTS
     (SELECT NULL /* Regions */
        FROM wwv_flow_page_plugs p
       WHERE p.security_group_id = c.security_group_id
         AND p.last_updated_on > to_date('20040610','YYYYMMDD'))
    AND NOT EXISTS
     (SELECT NULL /* Items */
        FROM wwv_flow_step_items i
       WHERE i.security_group_id = c.security_group_id
         AND i.last_updated_on > to_date('20040610','YYYYMMDD'))
    AND NOT EXISTS
     (SELECT NULL /* Templates */
        FROM wwv_flow_templates t
       WHERE t.security_group_id = c.security_group_id
         AND t.last_updated_on > to_date('20040610','YYYYMMDD'))
    AND NOT EXISTS
     (SELECT NULL /* Files uploaded */
        FROM wwv_flow_file_objects$ o
       WHERE o.security_group_id = c.security_group_id
         AND o.created_on > to_date('20040610','YYYYMMDD'))
    AND NOT EXISTS
     (SELECT NULL /* SQL Workshop history */
        FROM wwv_flow_sw_sql_cmds s
       WHERE s.security_group_id = c.security_group_id
         AND s.created_on > to_date('20040610','YYYYMMDD'));

After you identify inactive workspaces, you can purge them. Purging inactive workspaces is a two-step process:

• First, remove the resources (that is, the database schemas, tablespaces, and data files) associated with each inactive workspace.

• Second, drop the inactive workspaces from Oracle Application Express.

Removing the Resources Associated with Inactive Workspaces

After you have identified inactive workspaces in a single table, the next step is to remove them.

To remove the resources associated with inactive workspaces:

1. Identify the schemas used by the workspaces to be deleted by joining the table containing the identified inactive workspaces to wwv_flow_company_schemas.

2. Drop the schemas, tablespaces, and data files used exclusively by the inactive workspaces from the database. You can identify the schemas to drop by running a query similar to the following:

   SELECT s.schema
     FROM ws_to_purge ws,
          wwv_flow_company_schemas s
   WHERE s.security_group_id = ws.security_group_id
      AND ws.ok_to_delete = 'Y';
   

Deleting Inactive Workspaces

Once you remove the resources associated with an inactive workspace, you can delete the workspace. You can delete inactive workspaces manually using the Oracle Application Express Administration Services application. Or, you can delete them programmatically as shown in the following PL/SQL example.

BEGIN 
     FOR c1 IN (SELECT security_group_id  
                 FROM ws_to_purge
                 WHERE ok_to_delete = 'Y')
     LOOP
         WWV_FLOW_PROVISIONING.TERMINATE_SERVICE_BY_SGID(c1.security_group_id);
     END LOOP;
 END;

Exporting a Workspace

To export a workspace:

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

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Export Workspace.

4. Select a workspace and then click Export Workspace.

5. To export the selected workspace, click Save File.

6. Follow the on-screen instructions.

Importing a Workspace

To import a workspace:

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

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Import Workspace.

4. Click Browse, select a workspace export file, and click Next.

5. To install the workspace, click Install.

6. Follow the on-screen instructions.

Viewing Application Attributes

Oracle Application Express administrators can view applications by workspace on the Application Attributes page.

To view the Application Attributes page:

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

2. Click Manage Applications.

3. Click Application Attributes.

   The Application Attributes page appears.

4. Use the Navigation bar at the top of the page to filter the page view. Make a selection from the Display, Application, and Workspace lists and click Go.

5. To sort by column, select a column heading.

Changing Application Build Status Set During Deployment

Every Oracle Application Express application has an application-level attribute called Build Status. You can use this attribute to prevent an application from being modified by other developers. Build Status has two settings:

• Run and Build Application - Developers can both run and edit an application.

• Run Application Only - Developers can only run an application.

Setting the Build Status to Run Application Only is an effective way to prevent other developers from modifying it.

You can change the Build Status by:

• Changing the Build Status attribute on the Edit Definition page. See "Availability".

• Changing the Build Status during the deployment process. See "How to Move an Application to Another Development Instance".

Note that if you select Build Application Only during deployment, the only way to change this setting is change it on the Build Status page in Oracle Application Express Administration Services.

To change a Build Status set during deployment:

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

2. Click Manage Applications.

3. Click Build Status.

   The Build Status page appears.

4. Locate an application by making selections from the Build Status, Application, and Workspace lists and clicking Go.

5. Click the Edit icon adjacent to the appropriate application.

   The Edit Build Status page appears.

6. Select an alternate build status and click Apply Changes.

Viewing the Parse As Schemas Report

To view the Parse As Schemas report:

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

2. Click Manage Applications.

3. Click Parse as Schemas.

   The Parse As Schemas page appears.

4. Filter the display by making selections from the Parse As, Application, and Workspace lists and clicking Go.