| Oracle® Application Express Administration Guide Release 3.2 Part Number E12512-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Express Administration Guide Release 3.2 Part Number E12512-01 |
|
|
PDF · Mobi · ePub |
When users log in to Oracle Application Express, they log in to a shared work area called a workspace. A workspace is a virtual private database allowing multiple users to work within the same Oracle Application Express installation while keeping their objects, data and applications private. Each workspace has a unique numeric ID and name.
To make changes to their workspace, Workspace administrators submit change requests to an Oracle Application Express administrator. Only an Oracle Application Express administrator can approve change requests or provision new workspaces.
Topics in this section include:
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.
See Also:
"Using Oracle Managed Files" in Oracle Database Administrator's GuideAs 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:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Service.
Under Manage Environment Settings, click Instance Settings.
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).
Selecting Disabled from Email Provisioning, completely disables workspace provisoning when provisioning with Email Verification. Use the Message field to display a message to the user that explains why email provisioning is disabled.
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.
Click Apply Changes.
Note:
To enable users to request a workspace using a link on the Login page, an Oracle Application Express administrator must choose the provisioning status of Request or Email Verification as described in the previous procedure. If the provisioning status is set to Manual, no link appears on the login page.Oracle Application Express administrators can provision a workspace manually in either a full development environment or a runtime environment.
Topics in this section include:
Oracle Application Express administrators can provision a workspace manually by running the Create Workspace Wizard.
To create a workspace manually:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Workspaces.
Under Manage Workspaces, click Create Workspace.
The Create Workspace Wizard appears.
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:
For Re-use existing schema, select Yes.
Select a schema from the list.
Click Next.
If you are creating a new schema:
For Re-use existing schema, select No.
Enter a schema name and password.
Specify a space quota.
Click Next.
For Identify Administrator, enter the Workspace administrator information and click Next.
Confirm your selections and click Create.
To add a workspace in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_030200
Run the following statement:
BEGIN APEX_INSTANCE_ADMIN.ADD_WORKSPACE(WORKSPACE_ID,WORKSPACE_NAME, SCHEMA_NAME, SCHEMA_LIST) END;
Where:
WORKSPACE_ID is the ID for the workspace. Auto-assigned if NULL.
WORKSPACE_NAME is the name of the workspace.
SCHEMA_NAME is the name of the primary schema to associate with the workspace.
SCHEMA_LIST is a colon delimited list of additional schemas to associate with the workspace.
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 (or mapped) 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 Schema and Workspace Assignments in a Development Environment
Viewing Schema and Workspace Assignments in a Runtime Environment
Removing a Schema Mapping from a Workspace in a Runtime Environment
Oracle Application Express administrators can view the existing schema to workspace assignment on the Manage Workspace to Schema Assignments page.
To view the existing schema to workspace assignment:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Workspaces.
Under Manage Workspaces, click Manage Workspace to Schema Assignments.
'The Manage Workspace to Schema Assignments page appears. It lists all workspaces in your environment along with their associated schemas.
To view the existing schema to workspace assignment in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_030200
Run the following statement:
SELECT APEX_INSTANCE_ADMIN.GET_SCHEMAS(WORKSPACE_NAME)
FROM DUAL;
Where WORKSPACE_NAME is the name of the workspace.
To edit an existing schema and workspace assignment:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Workspaces.
Under Manage Workspaces, click Manage Workspace to Schema Assignments.
The Manage Workspace to Schema Assignments page appears.
To edit an existing workspace to schema assignment:
Select the workspace name.
The Edit Schema to Workspace Assignment page appears.
Select a new workspace or schema.
Click Apply Changes.
Oracle Application Express administrators can associate (or map) additional existing schemas to a workspace.
To associate additional schemas with a workspace:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Workspaces.
Under Manage Workspaces, click Manage Workspace to Schema Assignments.
The Manage Workspace to Schema Assignments page appears.
Click Create.
The Add Schema wizard appears.
For New or Existing Schema, select Existing and click Next.
Follow the on-screen instructions to associate the existing schema to a workspace.
To verify that the new schema is added to the workspace:
Log in to the workspace on Oracle Application Express.
Review the Workspace Schemas list on the Workspace home page. The list shows all schemas currently associated with this workspace.
To associate additional schemas with a workspace in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_030200
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.
To remove a schema mapping from a workspace in a runtime environment:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted enter the appropriate password.
Run the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_030200
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.
Oracle Application Express administrators can create a new schema and associate it with a workspace.
To create a new schema for a workspace:
Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services".
Click Manage Workspaces.
Under Manage Workspaces, click Manage Workspace to Schema Assignments.
The Manage Workspace to Schema Assignments page appears.
Click Create.
The Add Schema wizard appears.
For New or Existing Schema, select New and click Next.
For Choose Workspace, select the workspace that you want to associate the new schema with and click Next.
For Identify Schema:
Schema - Enter a unique name containing only letters.
Tip:
To verify that the new schema name is unique, open the select list and search for the name.Password - Enter a case-sensitive password.
Default Tablespace - Identify the default tablespace that you want this schema to use.
Temporary Tablespace - Identify the temporary tablespace you want this schema to use.
Click Next.
Confirm the information and click Add Schema.
To verify that the new schema is added to the workspace:
Log in to the workspace on Oracle Application Express.
Review the Workspace Schemas list on the Workspace home page. The list shows all schemas associated with this workspace.
|
 Copyright © 2003, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|