1. Administration Guide
  2. Oracle Application Express Administration Services
  3. Managing Existing Workspaces

2.15 Managing Existing Workspaces

Instance administrators can manage existing workspaces within an Oracle Application Express instance.

See Also:

Parent topic: Oracle Application Express Administration Services

2.15.1 Viewing Existing Workspace Information

Use the Existing Workspaces report to view an interactive report of existing workspaces. From the Existing Workspaces report, you can view or edit workspace details.

To view and edit existing workspaces:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Existing Workspaces.

    The Existing Workspaces page appears

  4. To edit a workspace, click the workspace name.

    The Edit Workspace Information page appears.

See also:

"Isolating a Workspace to Prevent Browser Attacks" and "Viewing the Workspace Summary Report"

Parent topic: Managing Existing Workspaces

2.15.2 Deleting a Workspace

Deleting a workspace does not remove any of the associated database objects. To remove the associated schemas, a database administrator (DBA) must use a standard database administration tool, such as Oracle Enterprise Manager or SQL*Plus.

See Also:

"Viewing the Workspace Summary Report" and "Creating Workspaces in Administration Services"

Parent topic: Managing Existing Workspaces

2.15.2.1 Identifying and Deleting Inactive Workspaces

Learn how to identify and delete inactive workspaces.

Parent topic: Deleting a Workspace

2.15.2.1.1 How to Identify Inactive Workspaces

If you are managing a large hosted Oracle Application Express instance, manually deleting inactive workspaces can free up resources for other users. The process of manually deleting inactive workspaces consists of the following steps:

Tip:

To systematically purge inactive workspaces you must configure Workspace Purge settings. See "Purging Inactive Workspaces."

2.15.2.1.2 Identifying Inactive Workspaces By Checking Recent Updates

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.

See Also:

"Determining the Oracle 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 = APEX_18100;
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'));
2.15.2.1.3 Viewing Workspaces with Only a Sample Application

Another way to identify potentially inactive workspaces is to view the Workspaces with Only Sample Application report.

To view a report or workspaces only containing only a sample application:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Workspaces with Only Sample Application.

    The Workspaces with Only Sample Applications page appears.

    This page displays as an interactive report. To customize the report, use the Search bar at the top of the page.

2.15.2.1.4 Removing the Resources Associated with Inactive Workspaces

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

Note:

Before removing the schemas, tablespaces, or data files associated with inactive workspaces, make sure these resources are not being used in any other workspace or application.

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';
2.15.2.1.5 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;

2.15.2.2 Deleting Workspaces in a Full Development Environment

Delete workspaces in a full development environment.

To delete a workspace:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Existing Workspaces.

    The Existing Workspaces page appears.

  4. Under the Action column, click Delete.
  5. On Verify Applications:
    1. Review the workspace name and the number of applications and users.
    2. Select Check to confirm that you wish to proceed with the removal.
    3. Click Next.
  6. Confirm the displayed information and click Remove Workspace.

Parent topic: Deleting a Workspace

2.15.2.3 Deleting Workspaces in a Runtime Development Environment

Delete workspaces in a runtime development environment.

To delete a workspace in a runtime development 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:
    ALTER SESSION SET CURRENT_SCHEMA = APEX_190200
  3. Run the following statement:
    BEGIN
APEX_INSTANCE_ADMIN.REMOVE_WORKSPACE(WORKSPACE_NAME, DROP_USER, DROP_TABLESPACE)
END;

    Where:

    • WORKSPACE_NAME is the name of the workspace.

    • DROP_USER is either Y or N. The default is N.

    • DROP_TABLESPACE is either Y or N. The default is N.

Parent topic: Deleting a Workspace

2.15.3 Locking a Workspace

Instance administrators can lock a workspace to address security or performance issues.

Locking a workspace immediately locks all workspace administrator, developer, and user accounts in the workspace. It also changes the status of all applications in the workspace to Unavailable.

Warning:

Locking a workspace makes it permanently inaccessible.

To lock a workspace:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Actions, click Lock Workspace.
  4. For Workspace, select the workspace you want to lock and click Next.
  5. Review the information about applications and users and click Lock Workspace.

Parent topic: Managing Existing Workspaces

2.15.4 Managing Workspace to Schema Assignments

Instance administrators can view, edit, and remove schema and workspace assignment, associate additional schemas with a workspace, and create new schemas.

When users sign in to Oracle Application Express, they access a shared work area called a workspace. Each workspace can have multiple associated (or mapped) schemas. By associating a workspace with a schema, developers in that workspace can create new database objects in that schema and build applications that interact with the database objects in that schema.

See Also:

"Managing Schemas" and "Viewing the Parsing Schemas Report"

Parent topic: Managing Existing Workspaces

2.15.4.1 Viewing Schema and Workspace Assignments in a Development Environment

View an existing schema to workspace assignments in a full development environment.

To view an existing schema to workspace assignment:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Actions, click Manage Workspace to Schema Assignments.

    The Manage Workspace to Schema Assignments page appears, listing all workspaces in your environment along with their associated schemas.

    This page displays as an interactive report. To customize the report, use the Search bar at the top of the page.

Parent topic: Managing Workspace to Schema Assignments

2.15.4.2 Viewing Schema and Workspace Assignments in a Runtime Environment

View the existing schema to workspace assignments in a runtime environment.

To view the existing schema to workspace assignment 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:
    ALTER SESSION SET CURRENT_SCHEMA = APEX_190200
  3. Run the following statement:
    SELECT APEX_INSTANCE_ADMIN.GET_SCHEMAS(WORKSPACE_NAME) 
FROM DUAL;

    Where WORKSPACE_NAME is the name of the workspace.

Parent topic: Managing Workspace to Schema Assignments

2.15.4.3 Editing Existing Schema and Workspace Assignments

Edit existing schema and workspace assignments.

To edit an existing schema and workspace assignment:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Actions, click Manage Workspace to Schema Assignments

    The Manage Workspace to Schema Assignments page appears.

  4. To edit an existing workspace to schema assignment:
    1. Select the workspace name.
    2. Select a new workspace or database schema.
    3. Click Apply Changes.

Parent topic: Managing Workspace to Schema Assignments

2.15.4.4 Associating Schemas in a Full Development Environment

Associate existing or new schemas with a workspace on the Manage Workspace to Schema Assignments page.

To associate an schemas with a workspace:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Actions, click Manage Workspace to Schema Assignments.
    The Manage Workspace to Schema Assignments page appears.
  4. Click Add Schema.
    The Add Schema wizard appears.
  5. The schema is a - Select Existing or New.
    The options that display next differ depending upon your selection.
  6. If you select Existing:
    1. Workspace - Enter the name of the workspace, or select one from the list.
    2. Schema - Enter new schema name.
    3. Click Next.
  7. If you select New:
    1. Workspace - Enter the name of the workspace, or select one from the list.
    2. Schema - Enter new schema name.
    3. Password - Enter a password for schema..
    4. Default Tablespace - Enter the default tablespace for the provisioned schema, or select one from the list.
    5. Temporary Tablespace - Enter the temporary tablespace for the provisioned schema, or select one from the list.
    6. Click Next.
  8. Review your selections and click Add Schema.

Parent topic: Managing Workspace to Schema Assignments

2.15.4.5 Associating Additional Schemas in a Runtime Environment

Associate additional schemas with a workspace in a runtime environment.

To associate additional schemas with a workspace 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:
    ALTER SESSION SET CURRENT_SCHEMA = APEX_190200
  3. Run the following statement:
    BEGIN
APEX_INSTANCE_ADMIN.ADD_SCHEMA(WORKSPACE_NAME, SCHEMA_NAME)
END;

    Where:

    • WORKSPACE_NAME is the name of the workspace.

    • SCHEMA_NAME is the name of the schema.

Parent topic: Managing Workspace to Schema Assignments

2.15.4.6 Removing a Schema Mapping from a Workspace in a Runtime Environment

Remove a schema mapping from a workspace in a runtime environment.

To remove a schema mapping from a workspace 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:
    ALTER SESSION SET CURRENT_SCHEMA = APEX_190200
  3. Run the following statement:
    BEGIN
APEX_INSTANCE_ADMIN.REMOVE_SCHEMA(WORKSPACE_NAME, SCHEMA_NAME)
END;

    Where:

    • WORKSPACE_NAME is the name of the workspace.

    • SCHEMA_NAME is the name of the schema.

Parent topic: Managing Workspace to Schema Assignments

2.15.5 Managing Component Availability for an Instance

Control which components are available within an Oracle Application Express instance, including App Builder, SQL Workshop, PL/SQL Editing in SQL Workshop, Team Development, or installation of productivity and sample applications.

To configure component availability:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Actions, click Manage Component Availability.
    The Component Availability page appears. To customize the report, use the Actions menu at the top of the page.
  4. Locate the workspace for which you want to enable or disable components.
  5. Click the workspace name.
    The Workspace Settings page appears.
  6. Under Workspace Settings, select Yes to enable a component or No to disable it. Options include:
    • Enable App Builder - Determines the availability of App Builder in this workspace.
    • Enable SQL Workshop - Determines the availability of SQL Workshop in this workspace.
    • Allow PL/SQL Editing in SQL Workshop - Allow PL/SQL procedures, packages, functions, and triggers to be edited in the browser.
    • Enable Team Development - Determines the availability of Team Development in this workspace.
    • Enable Productivity and Sample Application Installation - Controls the ability to install productivity and sample applications in the current workspace.
  7. Click Apply Changes.

See Also:

"Configuring Workspace Preferences"

Parent topic: Managing Existing Workspaces

2.15.6 Defining a Workspace Message in Administration Services

Create a workspace message in Administration Services.

Workspace messages display both on the Workspace home page and on the Workspace Administration page. Nn the Workspace home page, workspace message display in the News and Messages region.

To define a workspace message:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Actions, click Manage Component Availability.
    The Component Availability page appears. To customize the report, use the Search bar at the top of the page.
  4. Locate and select the workspace for which you want to define a workspace message.
    The Workspace Settings page appears.
  5. Under Workspace Message, enter a message in the Message field. To format the display, include standard HTML tags.
  6. Click Apply Changes.

See Also:

"Defining a Workspace Message"

Parent topic: Managing Existing Workspaces

2.15.7 Performing a Workspace Search

Perform a workspace search by clicking Find a Workspace on the Worspace Tasks page.

To perform a workspace search:

  1. Sign in to Oracle Application Express Administration Services.
  2. Under Workspace Tasks, click Find a Workspace.
    The Workspace Search page appears. To customize the report, use the Search bar at the top of the page.
  3. To view workspace details, click a workspace name.

    The Workspace Details report appears.

  4. To email the report to other users, click Email and follow the on-screen instructions.

Parent topic: Managing Existing Workspaces

2.15.8 Isolating a Workspace to Prevent Browser Attacks

Instance administrators can configure limits to isolate a workspace and prevent browser attacks.

See Also:

Parent topic: Managing Existing Workspaces

2.15.8.1 About Isolating a Workspace to Prevent Browser Attacks

Isolating workspaces is an effective approach to preventing browser attacks.

The only way to truly isolate a workspace is to enforce different domains in the URL by configuring the Allow Hostnames attribute. When the URLs of the attacker and the victim have different domains and hostnames, the browser's same-origin policy prevents attacks.

Parent topic: Isolating a Workspace to Prevent Browser Attacks

2.15.8.2 Configuring Workspace Isolation Attributes

Configure Workspace Isolation attributes.

To configure Workspace Isolation attributes:

  1. View the existing workspace:
    1. Sign in to Oracle Application Express Administration Services.
    2. Click Manage Workspaces.
    3. Under Workspace Reports, click Existing Workspaces.
    4. Click a workspace name.
    The Edit Information page appears.
  2. Locate Workspace Isolation and edit the attributes as described in the following table.

    Tip:

    To learn more about an attribute and view examples, see field-level Help.

    Table 2-7 Workspace Isolation Attributes

    Attribute Description

    Allow Hostnames

    Enter a comma separated list of hostnames that can be used to access this workspace. If you leave this attribute empty, the instance-level value applies. If you enter one or more hostnames, the incoming HTTP request URL's hostname part must match one of the listed hostnames.

    To learn more, see field-level Help.

    Resource Consumer Group

    Specify the Database Resource Manager consumer group to be used for all page events associated with this workspace. If you leave this attribute empty, the instance-level value applies. At the beginning of every request, the Application Express engine switches the current consumer group of the current database session to the workspace's consumer group. This applies to both executing applications and any of the applications used within the Application Express development environment.

    The privilege to switch to this consumer group must be granted to either PUBLIC or the Application Express schema. This privilege is typically granted using the procedure DBMS_RESOURCE_MANAGER_PRIVS.GRANT_SWITCH_CONSUMER_GROUP.

    Maximum Concurrent Workspace Requests

    Enter the maximum number of concurrent page events that Oracle Application Express supports for all applications of this workspace. If you leave this attribute empty, the instance-level value applies. Instead of processing a page event, Application Express shows an error message when the limit is already reached.

    Application Express keeps track of session requests by querying the CLIENT_INFO column of GV$SESSION. This tracking will not work if developers overwrite CLIENT_INFO, e.g. with a call to DBMS_APPLICATION_INFO.SET_CLIENT_INFO.

    Maximum Concurrent Session Requests

    Enter the maximum number of concurrent page events that Oracle Application Express supports for each session of this workspace's applications. Instead of processing a new page event, Application Express shows an error message when the limit is already reached. Alternatively, use the Concurrent Session Requests Kill Timeout attribute to kill an active database session, to process the new page event.

    Application Express keeps track of session requests by querying the CLIENT_IDENTIFIER column of GV$SESSION. This tracking will not work if developers overwrite CLIENT_IDENTIFIER, for example with a call to DBMS_SESSION.SET_IDENTIFIER.

    Concurrent Session Requests Kill Timeout

    If a new page event comes in that is outside the limits of Maximum Concurrent Session Requests, Application Express can execute alter system kill session on the oldest active database session which processes another page event for this Application Express session. This attribute specifies the number of seconds a database process has to be active, before it can be killed. If you leave this attribute empty, the instance-level value applies.

    Warning: Killing sessions can cause problems with the application server's database session pool.

    Maximum Size of Files in Workspace

    Enter the total size (in bytes) of all files that can be uploaded to this workspace.

    Maximum Email Messages

    Enter the maximum number of email messages that can be sent with the APEX_MAIL API per 24 hour period.

    This value overrides the instance-level setting.

    Maximum Web Service Requests

    Enter the maximum number of web service requests that can be sent per 24 hour period.

    Content Cache target size

    Denotes the target size for the content cache on workspace level.

    This value overrides the instance-level setting.

    Content Cache maximum entry size

    Denotes the maximum size for content to be placed into the content cache.

    This value overrides the instance-level setting.
  3. Click Apply Changes.

Parent topic: Isolating a Workspace to Prevent Browser Attacks

2.15.9 Viewing the Workspace Summary Report

View workspace information by viewing the Workspace Summary Report.

To view the Workspace Summary Report:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Workspace Details.

    The Workspace Details page appears.

  4. From the Workspace list, select a workspace.
  5. From the Reporting Period list, select a period and click Set.

    The Workspace Summary Report page appears. The following buttons display above the report:

    • Remove - Removes the current workspace.

    • Edit - Displays the Edit Workspace Information page.

    • Schema Assignments - Manage workspace schema assignments.

    • Manage Users - Edit or create new users.

    • Email - Send this report by email.

    The Workspace Summary Report is divided into the following major sections:

    • Workspace - Displays high-level information about selected workspace.

    • Workspace Schemas - Displays the schema name, and default tablespace, privileges granted, and database role privileges.

      When users sign in to Oracle Application Express, they sign 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 and create new database objects in that schema. To edit workspace to schema assignments, click Workspace to Schema Assignments.

    • Database Applications - Lists details about the database applications within the workspace.

    • Websheet Applications - Lists details about the websheets within the workspace.

    • Productivity and Sample Apps - Lists productivity and sample applications within the workspace.

    • SQL Workshop - Lists the number of SQL scripts, SQL script results, and SQL Command history.

    • Team Development - Lists the number of features, milestones, bugs, To Dos, feedback entries, news entries, and links.

    • Workspace Application Activity Summary - Details statistics about workspace applications.

    Other sections include:

    • 5 Most Active Applications

    • Developer Activity Summary

    • Database Object Counts by Object Type

    • 5 Top Tables by Row Count, Reported by Schema

Note:

Parent topic: Managing Existing Workspaces

2.15.10 Viewing Workspace Database Privileges

View a summary of workspace database privileges on the Workspace Database Privileges page.

To view workspace database privileges:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Workspace Database Privileges.
    The Workspace Database Privileges page appears. This page displays as an interactive report. To customize the report, use the Search bar at the top of the page
  4. To view workspace details, click the workspace name.

    The Workspace Summary report appears.

See Also:

"Viewing the Workspace Summary Report"

Parent topic: Managing Existing Workspaces

2.15.11 Viewing File Size and File Count by Workspace

View total file size and file count by workspace on the File Utilization by Workspace page.

To view total file size and file count by workspace:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Manage File Utilization.
    The File Utilization by Workspace page appears. This page displays as an interactive report.
  4. To customize the report, use the Search bar at the top of the page.

Parent topic: Managing Existing Workspaces

2.15.12 Finding and Emailing Workspace Summary

View total file size and file count by workspace on the File Utilization by Workspace page.

To find and email workspace summary:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Find and Email Workspace Summary.
    The Workspace Search page appears. This page displays as an interactive report.
  4. To view workspace details, click the workspace name.
    The Workspace Summary report appears.
  5. Click Email.
    The Email page appears.
  6. Enter content in the Body field.
  7. Click Email.

Parent topic: Managing Existing Workspaces

2.15.13 Exporting and Importing a Workspace

Move a workspace and all associated users to a new Oracle Application Express instance by exporting and importing.

Tip:

To review recommendations about optimizing the development and deployment of Oracle Application Express applications throughout their life-cycle, see Life Cycle Management with Oracle Application Express. Go to Life Cycle Management with Oracle Application Express.

See Also:

Oracle Application Express App Builder User’s Guide

Parent topic: Managing Existing Workspaces

2.15.13.1 About Exporting and Importing a Workspace

To move a workspace and all associated users to a new Oracle Application Express instance, you export the workspace.

When you export a workspace, Oracle Application Express generates a text file. This file contains information about your workspace, all the users in your workspace, and any groups in your workspace (if applicable). You can import this file into another Oracle Application Express instance.

Exporting a workspace and importing it into a new database instance enables developers to import application components. When building new environments (for example, moving from development to testing or testing to production), Oracle recommends creating workspaces by importing them.

Keep in mind, this method only imports workspace, users, and groups. This file does not contain:

  • The schemas associated with this workspace or the objects in those schemas.

  • Any applications, images, cascading style sheets, and static text files.

These items must be exported separately.

See Also:

"Deploying an Application" in Oracle Application Express App Builder User’s Guide

Parent topic: Exporting and Importing a Workspace

2.15.13.2 Importing a Workspace in Administration Services

Import a workspace by clicking Import Workspace on the Manage Workspaces page.

To import a workspace:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Export Import, click Import Workspace.
  4. Locate the import file and click Next.
  5. To install the workspace, click Install.
  6. Follow the on-screen instructions.

Parent topic: Exporting and Importing a Workspace

2.15.13.3 Exporting a Workspace in Administration Services

Export a workspace by clicking Export Workspace on the Manage Workspaces page.

To export a workspace:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Export Import, click Export Workspace.
  4. Select a workspace and then click Export Workspace.
  5. On Export Workspace:
    1. Include Team Development - Set to Yes to include Team Development components such as Features, Milestones, To Dos, Bugs, Feedback, Links and News in your workspace export file. Otherwise, select No.
    2. Export Type:

      • Minimal

        - In most cases, you should not change the default value.

      • Full - Includes all workspace artifacts including SQL Scripts, SQL Command History, saved SQL, user preferences, developer login history, email logs, and user interface defaults.

    3. File Format - Select how rows in the export file will be formatted:

      • UNIX - The resulting file contains rows delimited by line feeds.

      • DOS - The resulting file contains rows delimited by carriage returns and line feeds.

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

Parent topic: Exporting and Importing a Workspace

2.15.13.4 Exporting Applications and Workspaces from a Command-line

You can export workspaces, applications, and related files from a command-line, without requiring a manual export from the Web interface of Oracle Application Express using the APEXExport program.

About APEXExport

Use the APEXExport program to export Oracle Application Express workspaces, applications, and related files from the command-line. You have the option to split the export files into separate SQL scripts which is useful when managing files corresponding to the discrete elements of an Oracle Application Express application.

Program Requirements

The APEXExport program requires:

  • JDK (Java Development Kit) release 1.6 or higher

  • Oracle JDBC class libraries must be in your CLASSPATH

Using APEXExport

To use APEXExport:

  1. Set the CLASSPATH. For example:

    • On UNIX and Linux:

      • Issue the command:

        export CLASSPATH=.:${ORACLE_HOME}/jdbc/lib/ojdbc6.jar

      • From the apex/utilities directory, issue the command:

        java oracle.apex.APEXExport

    • On Windows:

      • From the Bash shell:

        set CLASSPATH=%CLASSPATH%;.\;%ORACLE_HOME%\jdbc\lib\ojdbc6.jar

      • From the apex/utilities directory, issue the command:

        java oracle.apex.APEXExport

  2. Returns the following output with both usage directions and examples.

    Usage APEXExport -db  -user  -password  -applicationid  -workspaceid -instance -expWorkspace -expMinimal -expFiles -skipExportDate 
-expPubReports -expSavedReports -expIRNotif -expTranslations -expTeamdevdata -expFeedback -deploymentSystem -expFeedbackSince 
-expOriginalIds -debug -expNoSubscriptions -expComments -expSupportingObjects -nochecksum -split   
 -db:                   Database connect url in JDBC format
 -user:                 Database username
 -password:             Database password
 -applicationid:        ID for application to be exported
 -workspaceid:          Workspace ID for which all applications to be exported or the workspace to be exported
 -instance:             Export all applications
 -expWorkspace:         Export workspace identified by -workspaceid or all workspaces if -workspaceid not specified
 -expMinimal:           Only export workspace definition, users, and groups
 -expFiles:             Export all workspace files identified by -workspaceid
 -skipExportDate:       Exclude export date from application export files
 -expPubReports:        Export all user saved public interactive reports
 -expSavedReports:      Export all user saved interactive reports
 -expIRNotif:           Export all interactive report notifications
 -expTranslations:      Export the translation mappings and all text from the translation repository
 -expFeedback:          Export team development feedback for all workspaces or identified by -workspaceid to development or deployment
 -expTeamdevdata:       Export team development data for all workspaces or identified by -workspaceid
 -deploymentSystem:     Deployment system for exported feedback
 -expFeedbackSince:     Export team development feedback since date in the format YYYYMMDD
 -expOriginalIds:       If specified, the application export will emit ids as they were when the application was imported
 -expNoSubscriptions:   Do not export references to subscribed components     
 -expComments:          Export developer comments     
 -expSupportingObjects: Pass (Y)es, (N)o or (I)nstall to override the default     
 -expACLAssignments:    Export ACL User Role Assignments
 -dir:                  Save all files in the given directory, e.g. -dir some/sub/directory
 -list:                 List all changed applications in the workspace or components in the application
 -changesSince:         Expects date parameter (yyyy-mm-dd). Limit -list values to changes since the given date
 -changesBy:            Expects string parameter. Limit -list values to changes by the given user
 -expComponents:        Export application components. All remaining parameters must be of form TYPE:ID
 -debug:                Print debug output
 -nochecksum:           Overwrite existing files even if the contents have not changed
 -split:                Split applications into multiple files
    Application Example: 
   APEXExport -db localhost:1521:ORCL -user scott -password scotts_password -applicationid 31500 
Workspace  Example: 
   APEXExport -db localhost:1521:ORCL -user scott -password scotts_password -workspaceid 9999 
Instance Example:
   APEXExport -db localhost:1521:ORCL -user system -password systems_password -instance 
Components Example:
   APEXExport -db localhost:1521:ORCL -user scott -password scotts_password -applicationid 31500 -expComponents PAGE:1 PAGE:2 AUTHORIZATION:12345678
List Example:
   APEXExport -db localhost:1521:ORCL -user scott -password scotts_password -workspaceid 9999 -list -changesSince 2019-07-29
   APEXExport -db localhost:1521:ORCL -user scott -password scotts_password -applicationid 31500 -list -changesBy EXAMPLE_USER
Export All Workspaces Example:
   APEXExport -db localhost:1521:ORCL -user system -password systems_password -expWorkspace 
Export Feedback to development environment:
  APEXExport -db localhost:1521:ORCL -user scott -password scotts_password -workspaceid 9999 -expFeedback 
Export Feedback to deployment environment EA2 since 20100308:
  APEXExport -db localhost:1521:ORCL -user scott -password scotts_password -workspaceid 9999 -expFeedback -deploymentSystem EA2 -expFeedbackSince 20100308

Parent topic: Exporting and Importing a Workspace

2.15.13.5 Viewing Application Attributes

View applications by workspace on the Application Attributes page.

To view the Application Attributes page:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Manage Applications, click Application Attributes.

    The Application Attributes page appears.

    This page displays as an interactive report. To customize the report, use the Search bar at the top of the page.

Parent topic: Exporting and Importing a Workspace

2.15.14 Changing Application Build Status in Administration Services

An Instance administrator can change the build status of an application.

See Also:

"Managing Build Status in Workspace Administration"

Parent topic: Managing Existing Workspaces

2.15.14.1 About Changing Application Build Status

Use the Build Status attribute to prevent an application from being modified by other developers.

The Build Status attribute 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.

Ways to Modify Build Status

You can change the Build Status of an application as follows:

Parent topic: Changing Application Build Status in Administration Services

2.15.14.2 Changing Build Status in Administration Services

Change a Build Status in Administration Services under Manage Workspaces, Manage Applications.

To change a Build Status in Administration Services:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Manage Applications, click Build Status.
    The Build Status page appears. To customize the report, use the Search bar at the top of the page.
  4. Click the Edit icon adjacent to the appropriate workspace.

    The Edit Build Status page appears.

  5. Select an alternate Build Status:.
    • Run Application Only - Developers can only run an application. Application will not appear in the list of applications shown in the App Builder for the workspace.
    • Run and Build Application - Developers can both run and edit an application. Application will appear in the App Builder's list of applications for the workspace.
  6. Click Apply Changes.

Tip:

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.

Parent topic: Changing Application Build Status in Administration Services

2.15.15 Viewing the Parsing Schemas Report

Use the Parsing Schemas report to identify the current parsing schema of each application in any workspace.

The Parsing Schemas report identifies the Oracle database schema whose privileges are used when Application Express dynamically executes the application's SQL and PL/SQL code at runtime.

To view the Parsing Schemas report:

  1. Sign in to Oracle Application Express Administration Services.
  2. Click Manage Workspaces.
  3. Under Manage Applications, click Parsing Schemas.
    The Parsing Schemas report appears. To customize the report, use the Search bar at the top of the page.

See Also:

"Managing Schemas" and "Managing Workspace to Schema Assignments"

Parent topic: Managing Existing Workspaces