PK[pT O PK *A OEBPS/adm_create_wkspc.htm]3
Creating Workspaces
Creating Workspaces
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.
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.
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.
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.
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.
Creating a Workspace Manually in a Runtime Environment
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.
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 (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.
PK9a
PK *A OEBPS/aadm_hm.htmK
About the Application Administration Page
About the Application Administration Page
Use the Application Administration page to manage your application development environment. The Application Administration page contains the following icons:
Manage Services links to the Manage Services page. Use this page to manage services, including session state, log files, service termination, schema requests, storage requests, schema reports, preferences, and application models. See "About the Manage Services Page".
Manage Application Express Users links to the Manage Application Express Users page. Use this page to manage Application Express user accounts and user groups. See "Managing Application Express Users".
Monitor Activity links to the Monitor Activity page. Use this page to monitor changes to page views and entire applications in your workspace. It also shows reports on such information as login attempts and external click counts. See "Monitoring Activity within a Workspace".
A Tasks list displays on the right side of the page and displays the following links:
Viewing the Application Express Product Information Page
The About Application Express page lists basic product information. You can access the About Application Express page from either the Workspace home page or the Application Administration page.
The About Application Express page displays the following product information:
Product build
Schema compatibility
Last DDL time
Host schema
Application Owner
Workspace ID
Workspace Name
Current user
Language Preference
Current Time (on server)
NLS_CHARACTERSET
DAD CHARACTERSET
JOB_QUEUE_PROCESSES
Database Version Information
To view the About Application Express page:
Navigate to the Workspace home page.
On the Administration list, click About Application Express.
The About Application Express page appears.
PKҹP K PK *A OEBPS/aadm_schema_request.htmu
Requesting a Database Schema
Requesting a Database Schema
To submit a request to the Oracle Application Express administrator for a new database schema:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Workspace, click Request Database Schema.
For Identify Schema:
Specify whether to request a new schema or use an existing schema and then click Next.
For Schema Name, enter a new name or select one from the list.
Click Next.
Review the online instructions and click Finish.
PKK PK *A OEBPS/aadm_mg_sessions.htmAS
Managing Session State and User Preferences
Managing Session State and User Preferences
A session is a logical construct that establishes persistence (or stateful behavior) across page views. Each session is assigned an 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. Sessions persist in the database until purged.
A session establishes persistence (or stateful behavior) across page views. You can review session details for the current session or for recent sessions. You can also purge the current session state or purge sessions based on their age.
Removing Session State After Reviewing Session Details
You can determine whether to remove existing sessions by first reviewing session details. From the Session Details page, you can then remove the session record or session state.
To view session details and remove session state:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Session State, click Manage Session State.
Click Recent Sessions with Drill-Down to Session Details.
To narrow the results, select a time frame, specify a user, and click Go.
To view session details, select the session ID.
The Session Details page appears.
Click one of the following buttons:
Remove Session removes the record of the session from the SESSIONS table along with the session state (including collections data) associated with the session.
Any user using a session that is removed will no longer be able to use the session and will be prompted to re-authenticate upon their next page request (in most situations). This option can be used by administrators who need to ensure a specific user can no longer access an Oracle Application Express application.
Remove State clears the session data from the session state tables (including collections data) but does not remove the session record. Removing a session is a good approach for developers during debugging.
This is the equivalent of clearing session state for the current session using the Clear Cache argument value SESSION in the f?p URL. This option might also be used by developers during debugging.
To view session state for the current or recent sessions:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Session State, click Manage Session State.
On the Manage Session State page:
To view information about the current session, click Report Session State for Current Session. To search for an item in the details, enter the item and click Go.
To view a list of recent sessions, click Recent Sessions with Drill-Down to Session Details.
You can use preferences to store values for a specific Application Express user across distinct sessions. Once set, these preferences can be removed programmatically or manually. You can set user preferences by creating a page process, by the calculation of a preference Item Source Value, or programmatically by using a PL/SQL API.
Viewing and Resetting Preferences for the Current User
To manage user preferences for the current user:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Session State, click Manage Preferences.
The Manage Preferences page appears.
To view preference information about the current user, click Report Current User Preferences.
The Current User Preferences page appears.
To view and reset preferences for the current user, click Purge Preferences for Current User. On the Purge Preferences page, click the appropriate button:
Reset Preferences
View Preferences
Viewing Preferences by User
To view the preferences for specific users:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Session State, click Manage Preferences.
The Manage Preferences page appears.
To view preference information about a specific user, click Preferences by User.
Use the search bar at the top of the page to narrow the display.
To view and reset preferences for the current user:
Click Purge Preferences by User.
Select a user from the list and click Report.
A report appears.
To purge user preferences, click Purge User Preferences.
Setting User Preferences
You can set user preferences within your application through the creation of a page process, by creating a preference item, or programmatically.
In Item Source Value, enter the name of the preference.
Click Create Item.
Setting User Preferences Programmatically
To set or reference user preferences programmatically, you must use a PL/SQL API. User-level caching is available programmatically. You can use the SET_PREFERENCE procedure to set a user level preference called NAMED_PREFERENCE. For example:
To remove user preferences programmatically, you must use a PL/SQL API. You can use the REMOVE_PREFERENCE procedure to remove a user level preference called NAMED_PREFERENCE. For example:
Specify a process name, sequence, and process point.
Follow the on-screen instructions.
Purging Preferences for a Specific User
You can purge preferences for a specific user on the Purge Preferences page.
To purge preferences for a specific user:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Session State, click Manage Preferences.
Click Purge preferences by User.
The Purge Preferences page appears.
Select a specific user and click Report.
A report appears at the bottom of the page.
To purge the displayed user preferences, click Purge User Preferences.
PKg0FS AS PK *A OEBPS/aadm_wrkspc_rprt.htmi
Viewing the Workspace Overview Report
Viewing the Workspace Overview Report
Workspace administrators can view a summary report of the current workspace by selecting Workspace Overview on the Manage Services page. Administrators can use this report to view:
Contributors: Marco Adelfio, Drue Baker, Carl Backstrom, Christina Cho, Michael Hichwa, Joel Kallman, Sharon Kennedy, Sergio Leunissen, Anne Romano, Kris Rice, Marc Sewtz, Scott Spadafore, Scott Spendolini, Jason Straub, Simon Watt, and Steve Fogel
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
PK6Ƚ PK *A OEBPS/aadmn_mg_cache.htm+
Managing Cached Regions and Pages
Managing Cached Regions and Pages
One way to improve an application's performance is to take advantage of page and region caching. Developers can configure page and region caching by setting the Cache attribute on Edit Page or Edit Region pages. This section describes how Workspace administrators can view and purge cached regions and pages.
To locate an application, page, or region, enter a case-insensitive query in the appropriate field at the top of the page and click Go.
To purge cached regions, you can:
Select the regions you want to purge and click Purge Checked.
Click the Purge by Application tab, select the application, and click Purge Cached Regions.
Click the Purge All tab and then click Purge All Cached Regions.
Purging Cached Pages
To view and purge cached pages:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Caching, click Manage Cached Pages.
The Manage Cached Pages page appears.
To locate an application, page, or region, enter a case-insensitive query in the appropriate field at the top of the page and click Go.
To purge cached pages, you can:
Select the pages you want to cache and click Purge Checked.
Click the Purge by Application tab, select the application, and click Purge Cached Pages.
Click the Purge Expired tab, select the application, and then click Purge Expired.
PK PK *A OEBPS/wkspc_adm_roles.htm
&
Understanding User Roles
Understanding User Roles
In the Oracle Application Express, users log in to a shared work area called a workspace. Users are divided into three primary roles:
Developers create and edit applications.
Workspace administrators are developers who also perform administrator tasks specific to their workspace such as managing user accounts, monitoring workspace activity, and viewing log files. See "Workspace and Application Administration".
Oracle Application Express administrators are superusers that manage the entire hosted instance using the Oracle Application Express Administration Services application.
Oracle Application Express administrators can modify a workspace (for example, add a new schema or increase the disk space limit) by approving a change 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.
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.
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.
PK
PK *A OEBPS/preface.htm3
Preface
Preface
Oracle Application Express is a hosted declarative development environment for developing and deploying database-centric Web applications. Oracle Application Express turns a single Oracle database into a shared service by enabling multiple workgroups to build and access applications as if they were running in separate databases.
Oracle Application Express Application Administration Guide describes how to perform administration tasks for an Oracle Application Express workspace, application, or an entire development instance.
Describes tasks an Oracle Application Express administrator performs when administering an Oracle Application Express hosted instance.
Audience
Oracle Application Express Administration Guide is intended for application developers who are building database-centric Web applications using Oracle Application Express. The guide describes how to use the Oracle Application Express development environment to build, debug, manage, and deploy applications.
To use this guide, you must have a general understanding of relational database concepts and an understanding of the operating system environment under which you are running Oracle Application Express.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Deaf/Hard of Hearing Access to Oracle Support Services
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.
For information about Oracle error messages, see Oracle Database Error Messages. Oracle error message documentation is available only in HTML. If you have access to the Oracle Database Documentation Library, you can browse the error messages by range. Once you find the specific range, use your browser's "find in page" feature to locate the specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation.
Many books in the documentation set use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.
For additional application examples, please visit the Oracle by Examples (OBEs) Application Express page, located on Oracle's Technology Network. The OBEs provide step-by-step examples with screenshots on how to perform various tasks within Application Express.
To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at
PKn \ R PK *A OEBPS/img/nav_bar_users_2.gif GIF89aP" Z s { Z s { BBBRRRZ Z ZZ {ZZZZcccccccckcccccs s ss ss sss{sssssss{{{{{{{{{{{{ Z{Όcccccޔ s Z Υccccﭥ{ ƭƵνsscƽƽƽεννΥc֜ ֭{Ɣֽ֥sΥ֜ ! , P" W H
ҡ9{*\ȰÇ#JHŋ3jȱǏ C Iɓ(;\i!KbʜI͛8sɳϟ@
JѣH*]ʴӧP!xeԫXjʵׯ`Ê t*dӪ]˶۷pʝ9ՠPKZ9߿>U LÈ+^̸ǐ#XX˘3 L@ >!}AD\̺װ'W"۸sͻ N!ʕc+'|УKn6]?aG)Q`iuӫ_l5˟O߯}L}U{s%8u2%OvSF]l
a'W|(${1X,"'&pa@
N9X g
~ZSL mc
s<薍7Vie'H\veh `mqƣ
2>}bБ t́J$qȇb~)蠗e&1BʣF
)Zq> ms9ACWm:%z<ßzot曃-<- 眃2ȇx^h@2&N*O_`6f Hng7(B @ ?29=+)I,Agc\$r>[WvMP#]6蟀.vVʼndn\QK%v
p^abA !zԢ^L&BPN 1{x(01UA3ıx, ~%uCb yޤKpAzL,QJw
a
wf.=@gC1+`
M ]O'h =\ҥ' xT\&q
s#_Jp=!~i q_NAL[ U-Qq ,W\@t3 &폍89HQ
S
<?2{^xD^b-M
R$ډ,JBhx=qyt2IH@ @Q DF{LU @$b ^r #['cb*6WFgҡf?bOȃ!
a21H༉@J$ CxqL4P&Qb;jiBi :8QTNR]hE%|V¢
T@ҪAHCJQNfk 0T tOu6S6?yYQ!&<5<艘S ^Dd(ױk5N0 R`3$^m's%[ %Li\t{$v"kuJ˄[sL2⏌fDkHxXHp `*V8أZPӡLzٻmgx̠ݦxݹ^ )v^M V6"^c)*q=
1.3⋥i[*8 XSx-~Ef E6B 9f.5, %zZDBzW?NF9d s@,2s*uYN,fI"^)9VUT]@Z94h&3G fK_ڋ_Mt;IA h'6j/0nvb4 >K$r|~Ԡ(#,*VƶceY{E;~jn9&ݞfK͆?`_0
|lfRNN;N%㐌j ? Ђ
(r*7rL p3ˤЇNMX4vjr7H
K][X: DR2@ZO}* t+Sacb=T=,:[O;)s$>G IWֻgO" ;PKWN PK *A OEBPS/img/notifi.gifDGIF89a \ ! , \ 0S8ͻ`(dih9!IqtmxHpH,Savl:ԀZ
&t= %բNgN 7V&ûdtc}ag~e{M~^pEuw8'ivϜѹҖfqڞ֍d
H0 \ȰÇ#S(ŋ3
Ǐ r IɌ#O\R0cėr͛ k3N 7_ѐ *y羟
dӦ: աR=0u,Y ]Jt-Zº%Y`Ѳz ~`
z`z
^,خay~X2߾]*
e:yẗ́^-{#QGZۻ5'9cٴm3ؽf-\ sȾu:֍} n'G^ZtjjUs~7hΣ|zqד{+G!DJ2`E >(မMhk^!LnI ST C%EC!w>$b5(0VXЈ8d?C }ޑPvXd6|%9B# 0$4_zW^y^a7)UXr֭&{mn@C#gnf~OCFhhfx1ڨBQY_[瑪mMjA:)]I-ЛDjk M
Fx柾ۣl~9Q :[GW}Dfk$~u1)~ı5ٖwf uhv)xܺGw{\s z
<ߺnJwꮋvl`n@גW!ʥBZlia.ܟ}r,W{,KT4, H
uԪNM5V_&@v:2DrwZchMZٜ8@E8SfnO=s?u"ݮm"D
s˸ldB+ [l㚗ɏ깜2Kz.J z#km8c 6&○}kkFcόyr/a'HD ;PK^' PK *A OEBPS/img/nav_bar_users.gifGIF89aW5 J Z k s { J Z k s { BBBJ J JJ kJJkJJJJZ Z ZZ {ZZZZZZZcccccccckcccccck k Jk kkJ kk kkkkks s ss ss sss{ssssssss{{{{{{{{{{{{ ZJ JJk {ΌcccZcތk s Z ΜccJcפּZk{ ƭƵνs sscsƽƽƽενƥZνΥcν֜ ֭{Ɣֽ֥ZsΌΥέ֜ ! , W5 HA~)\ȰÇ#JHŋ32vCѣɓ(S\ɲ˗0cʜIMƼHɳϟ@
JѣH*ʜRHJիXj5ӛ`Ê KٳhcRCpʝKݻx˷߸"VHZ4+^̸ǐ#KXi3k̹&IӨS+RSMm[^ͻm!ȍbpٷKΘ9سk~RN }{8N9 CzO7ݡ۠e}@ bH] @QFE(EInͅ8רW~|iPL7٧z|'QEc(, APРtrXDiGH\L)$b9DUCbzGX L}s|^"%9`Cxp'6[
6祉@jh\r@'
z`%X & 0}D§ebp)7؇Cإ d* S jg+ /Xǚ[˔"{^z&N ȉurbbz
h)ʅ8{Ȭm"}zH.bPފG\A1鍕
X# q!Hq7\7F,ʚ
gWz Z\Nb\Ss ھWkH@pH3S={T:f]W `ڎS悻aEoJUݠW<%TXf<筍xi L^F4qMi<:NЗ/ps P
if>"~foiX˅3SX]F2Y`Ўzatr>(a bO!Hd b wR
NG@>/Lؓ<'QDgYGdP켤uRLrQ@ʣ}nvK1dAx>z 4*qS\E@js
lWzxL2 Mkq)je`6sq 'gFr4
5٢mM7&z-IZ;~N
B<J 9Іs9W,D ̈́Z(qC7,G
@+ђ 4E'PҖ0LgJӚ8ͩNwӞ@
PJԢHMRzT05JժZXͪVծz`
XJֲhMZֶp\݊
dQ^
`KVu+-:d'Kr)%+H~a Z
hGKҚv*< _
;0ͭnw[ҤUEEf
$ r @KDtKZͮvzwwKnxwu|^rͯ~; " ,eWAQ4P"!@PAm@
[ΰ7{ qf_NX(NWWq=gaV4 ]mk@:(D%(E
pZkҕxTrJ|X
efY3co9f.B!ExD'L 5al=Mrey'!1J[h09%_E$So{fƹ`Þ=WH>B}hD{mB4c:֏+Jkki~C*RA 85* ,Rz5t{z̷v^,=X@x w[b!0 R!]<0sw x ![ &
8H7t֒ A+7'AszhUN'ܫ>iNo@A
pLl`w 7Uo`G T+.օ7ݶ/|s~idxA 40 ':An7L{Q];ZOl7nyXUJc 99q0>v"> X\'dS5֨*
("= |:/rO.v%`
7e/
x_` x
@
f ^E l0
!`4w3 d TjVqI|g
ܨܘHwxwb> I`JGHwn@ nHe |iUِIU ~X )xŗ{7QP|บ!4as*y_Iz=Y@ g#hUP` k;@`p:@r'Gć؉v_7qMw 'pH{9x٘Ycqn=Ǎŗם]*ji: ojtY|Q٤ ǝ {Ոr)K7u2j 89z^e w 4 RGf[U%W'QXU98p ~砭
7ȟaiϺ y ryʞ5ZUGs}!i+7ʖh
~sAי|pn7pVr9 h
qj³ Y xlYe 9 a Y&iF:(~zdY1
r虅ȅѰڦVJ3_=]%]uUՒآZWkę a0WىhLj$+@kB+e[Ex$i薵&[U 0
uen[lhi Ɔx+Uax l}kU
Ƞ
D@ ;z${k%Z_Unݥvc{ KU0
3Fki+bkVK[z6ѼVdkUՐa{;[+图껾i[VDо_c+(8\WE 5 Wi[{u0WFBXi
zju { "L
4\` ʂFP~@# 2<4\ùUWRf @ 6 BDescription of the illustration nav_bar_users_2.gif
This illustration shows the navigation bar on the Manage Developers and Users page. Additional information about this illustration can be found in the surrounding text.
PK3H C PK *A OEBPS/img_text/notifi.htm
Description of the illustration notifi.gif
This illustration shows the Notifications list located on the lower right side of the Administration home page. Each list items displays a summary of total and pending workspace and change requests. To view additional details, click the appropriate change request number.
Additional information about this illustration can be found in the surrounding text.
PKe PK *A OEBPS/img_text/nav_bar_users.htm>
Description of the illustration nav_bar_users.gif
This illustration shows the navigation bar on the Manage Application Users page. Additional information about this illustration can be found in the surrounding text.
PKnC > PK *A OEBPS/adm_login.htmN
Logging in to Oracle Application Express Administration Services
Logging in to Oracle Application Express Administration Services
Oracle Application Express administrators are responsible for managing an entire Oracle Application Express instance. To perform these tasks, an Oracle Application Express administrator logs in to the Oracle Application Express Administration Services application.
To log in to Oracle Application Express Administration Services:
In a Web browser, navigate to the Oracle Application Express Administration Services application. By default, Oracle Application Express Administration Services installs to the following location:
If your setup uses the embedded PL/SQL gateway, go to:
http://hostname:port/apex/apex_admin
Where:
hostname is the name of the system where Oracle XML DB HTTP Server is installed.
apex is the database access descriptor (DAD) defined in the configuration file.
For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.
If your setup uses Apache and mod_plsql, go to:
http://hostname:port/pls/apex/apex_admin
Where:
hostname is the name of the system where Oracle HTTP Server is installed.
port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from either of the following files:
Be aware that if you change a port number, it is not updated in the portlist.ini file. You can only rely on this file immediately after installation.
pls is the indicator to use the mod_plsql cartridge.
apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.
For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.
The Login page appears.
In Username, enter admin.
Tip:
admin is the default Oracle Application Express administrator account. To create additional Oracle Application Express administrator accounts, see "Creating New User Accounts"
In Password, enter the Oracle Application Express administrator account password you specified when you installed Oracle Application Express.
"Managing Oracle Database Port Numbers" in Oracle Database Installation Guide for information about installing Oracle Application Express
PK1 PK *A OEBPS/aadm_activity.htm$9
Monitoring Activity within a Workspace
Monitoring Activity within a Workspace
You can monitor developer activity and changes within your workspace by accessing the Monitor Activity page. The Monitor Activity page over twenty different reports that track changes to page views and applications, including reports on login attempts and external click counts.
Application Express environment through the login pages for Oracle Application Express Administration Services or Oracle Application Express
applications developed using Application Express that use the built-in session management facilities of Application Express
Select a report to review.
Viewing Application Changes by Developer
The Application Changes by Developer report displays the number of pages changed by each developer and offers a graphical representation of the information in either a bar chart or pie chart format.
To view Application Changes by Developer:
Navigate to the Workspace home page.
From the Administration list, click Monitor Activity.
Under Application Changes, select By Developer.
Make a selection from the Time list to specify a time frame and click Go.
To view the data as a bar chart, select Changes by Developer Bar chart. To view the data as pie chart, select Changes by Developer Pie chart.
To view additional details, select a user ID.
A detailed report displays the application, date, component, and action by user.
Viewing Application Changes by Day
The Application Changes by Day report displays a summary of the number of application changes by day. You have the option to view this information by month, as a line chart, or by developer.
To view application changes by day:
Navigate to the Workspace home page.
From the Administration list, click Monitor Activity.
Under Application Changes, click By Day or By Day, Monthly View.
The Application Changes by Day page appears.
Select the appropriate report:
Month View offers a listing of application changes by day in a Calendar format.
Report includes a report of application changes by day.
Line Chart displays a line chart of application changes. By default, all developers are selected. To view only a specific developer, make a selection from the Developer list and click Go.
By Developer Report displays application changes by developer. Specify a time frame by making a selection from the Time list and clicking Go. To view additional details, select a developer. To download the report, click the Download link at the bottom of the report.
Viewing Active Sessions
A session is a logical construct that establishes persistence (or stateful behavior) across page views. The Active Sessions report lists active sessions with the current workspace.
Whenever an application is run, the Application Express engine maintains a record in a database table in the Oracle Application Express schema. This table records a numeric identifier (or session ID), the authenticated (or public) user identifier, the creation date, and other information. The session is the key record that enables session state, or persistence, across page requests. By viewing the Active Sessions report, a developer or administrator can see who has been using applications in a workspace. An active session is a session that has not yet been purged from the sessions table. A DBMS job runs every eight hours and purges session records older than 24 hours.
From the Administration list, click Monitor Activity.
Under Sessions, select Active Sessions.
Click a session ID to view the Session Details page.
PK.$ $ PK *A OEBPS/aadm_mg_service.htm_
About the Manage Services Page
About the Manage Services Page
You can use the Manage Services page to manage session state, caching, preferences, application models, demonstration applications, log files, service termination, schema requests, storage requests, schema reports, and log files.
The Manage Services page contains the following sections:
Workspace Preferences. Use this link to disable and enable application preferences such as PL/SQL program unit editing in Object Browser. See "Managing Workspace Preferences".
Workspace Schema Reports. Use these links to view detailed reports about the schemas in the current workspace. See "Viewing Schema Reports".
Logs. Use these links to purge the Developer Activity and External Count Clicks logs. See "Managing Log Files".
Accessing the Manage Services Page
To access the Manage Services Page:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
PK$ PK *A
OEBPS/toc.ncxW
Oracle® Application Express Administration Guide, Release 3.2CoverTable of ContentsOracle Application Express Administration Guide, Release 3.2PrefaceWorkspace and Application AdministrationAbout Workspace AdministrationUnderstanding User RolesAbout the Application Administration PageAbout the Manage Services PageManaging Session State and User PreferencesManaging Cached Regions and PagesManaging Workspace PreferencesManaging Application ModelsManaging Demonstration ApplicationsLeveraging Application Builder DefaultsViewing the Workspace Overview ReportTerminating a Workspace ServiceRequesting a Database SchemaRequesting Additional StorageChanging Build Status for Multiple ApplicationsViewing Schema ReportsManaging Log FilesManaging Application Express UsersMonitoring Activity within a WorkspaceOracle Application Express Hosted Instance AdministrationWhat Is an Oracle Application Express Administrator?Logging in to Oracle Application Express Administration ServicesManaging ServiceManaging Environment SettingsManaging SchemasCreating WorkspacesManaging Workspace RequestsManaging Change RequestsManaging Users in an Oracle Application Express InstanceManaging Existing WorkspacesManaging ApplicationsMonitoring Activity Across a Development InstanceIndexCopyright
PKM\ W PK *A OEBPS/adm_ser_rqst.htm0J
Managing Workspace Requests
Managing Workspace Requests
An Oracle Application Express administrator is responsible for reviewing requests for a new workspace. To manage workspace requests, you need to have selected either the Request or Email Verification provisioning status.
With either Request or Email Verification provisioning status, users request workspaces directly in a self-service fashion. For example, users could click a link on the login page to access a request form. Once the workspace request has been approved, each user is emailed the appropriate login information.
From the Status list, select Requested and click Go.
Locate a request to review.
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.
Return to the Workspace Requests page.
To approve a request:
Click Provision in the Actions column.
On the Provisioning Administration page, click Approve.
Review the email message.
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. To create the workspace, the user must click the verification link to create the workspace. See "Specifying a Provisioning Mode".
To decline a request:
Click Provision in the Actions column.
On the Provisioning Administration page, click Decline.
Review the email message.
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.
More About the Approval Process
If you are using Email Verification, when an Oracle Application Express administrator approves a workspace request, the following events occur:
An email containing a verification link is sent to the user.
When user clicks the verification link, the workspace is created.
Another email is sent to the user containing login credentials (that is, the workspace name, User ID, and password).
The status of the workspace request changes from Accepted to Approved.
If the user fails to click the verification link, you can quickly delete the request by clicking the DELETE link in the Action column.
When an Error Occurs
If an error occurs during the workspace creation process, the status of the request reverts to Requested and an email is sent to the user containing the following message:
Please contact administrator.
Once the issue is resolved, the administrator can again repeat the previous procedure and approve the request.
Changing the Status of an Existing Workspace Request
To change the status of an existing workspace request:
To filter the report, make a selection from the Status list and click Go.
Locate a request to review.
Click the link in the Actions column.
The Adjust Request page appears.
From the Project Status list, select a new status.
Click Apply Changes.
Note:
Be careful when setting the Project Status to Requested. Although Requested enables you to reprovision a workspace, it could result in data corruption due to the manner in which accounts are provisioned. The provisioning system assumes Requested workspace requests do not have the corresponding schemas and dictionary entries for a Workspace administrator or developers. If you must change the Project Status for an Approved workspace to Requested, terminate the service first and then change the status to Requested.
Oracle Application Express administrators can use the Manage Applications page to view reports on key attributes of applications in all workspaces across a development instance.
Use the Navigation bar at the top of the page to filter the page view. Make a selection from the Workspace, Application, Parsing Schema, and Display lists and click Go.
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 of an application as follows:
Workspace administrators can change the Build Status of applications within the current workspace on the Manage Application Build Status page. See "Changing Build Status for Multiple Applications".
Oracle Application Express administrators can change the Build Status of an application on the Build Status page.
To change a Build Status as an Oracle Application Express administrator:
Locate an application by making selections from the Build Status, Application, and Workspace lists and clicking Go.
Click the Edit icon adjacent to the appropriate application.
The Edit Build Status page appears.
Select an alternate build status and 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.
\a߄i4\&ci! ڥ ʑ Wm _ݭzt r< U#6J 5;O| 9/#JVFcw𱃀 vgCou.8MknUq+*q G~t;/MN 5S
o*>~IC aQ 9cpF2YB&z>#֛儼IJ$A&ԫeOxUռ 5
I ++ >#Wx@ 4}F=F;*ʲ;Hc'=h> /K[]TՇzآ< xz@:_j1=Uhc&7c $u "> 3'%_pF%iw3c#8y (Я=y dtBU8@@}
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(8 xcV/ |#sm W(< |E( F伏Un $||; 'Ɨm#WͷeqaAE x?9
/YlF*y98%֣(o2I2@12K :(Ӽ ?| E /!~t>; 'Ɨm#WͷeqaAE x?9
/YlF*y98%֣(o2I2@12K :(Yj[B@یZO`u(
g8Ke]R嵿Z"Vu@\?|rۑJ(7~$e
ؘqܡr8 ,?Ѵ曦'LyyIybDž {>E q~gF2]jU Xg 'sKmy>Ŵg\Y@`G$((#ඥ|Z'5M>DY`@@Mps>acoiqv$0vdp V(? /5 u]gJIo;E 5Oxb:A:̏ XtiZUevv(I9$I$W(? S>'տ~w+|6;c8 =mo߰y6m} vwvP<?럔~xoR5vwiV6R6
=]% QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QEPKAi i PK *A OEBPS/dcommon/contbig.gif`GIF87a !!!111999BBBJJJRRRccckkksss{{{skk{{ZRRRJJƽ{sZRJRJB91)kcZB9)sskZRJ1ƽ{{ssskkkcƵZZRccZRRJJJB{BB9991ssckkZccR))!RRB!!JJ1))99!11 ƌ)1R)k֔)s1RZJR{BJs9R1J!11J1J9k{csZk!1J!)cBR9J1B)91B!cRs{!)s!){1B!k!s!{ksksckckZc9B)1!)!)BJ9B1919έƌ!!)JJcZZ{!!!1RR{JJsBBkJJ{!!9BB{1!!J9)!!Z!!c1!!kR!!s9Z!BckJs)19 !!c !! ZRZ , H
rrxB(Kh" DժuICiи@ S
z$G3 TTʖ&7!f
b`D 0!A
k,>SO[! \
*_t
Exr%*_}!#U
#4
& ֩3|b]L ]t b+Da&R_2lEٱZ`aC)/яmvUkS r(-iPE Vv_{z GLt\2s!F A#葡JY
r|A A,hB}q|B`du
}00(䡆<pb,G+oB
C0p/x$ ]7 @2HF c ) @AD
\0
LH G',(A ` `@S C)_" PH` }Y+ _|1.K8pAKMA @? 3҄$[JPA)+NH I
,@8G0 /@R T,`pF8Ѓ)$ ^$ DD TDlA@ s ;PK PK *A OEBPS/dcommon/darbbook.css PK PK *A ! OEBPS/dcommon/O_signature_clr.JPG"( JFIF ` ` C
$.' ",# (7),01444 '9=82<.342 C
2! !22222222222222222222222222222222222222222222222222 "
} !1AQa"q2#BR$3br
%&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
w !1AQaq"2B #3Rbr
$4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz ? (
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(
(?O
'~MQ$V z;OlJ i 8L%\]UFjޙ%ԯS;rA]5 ފ<]j7Ouyq$z 'T Q uw 7Ŀ
KX߁M 2=S'T Q t?. 5 w ' 97 ;~pq= " ~k?`'9q6 E|yayM^Om'fkC&<5x'
?A?Zx'jß={=S ßM
gVC.5+H d֪xc^)Җufz{Cީ|D V k znq| +Xa+{50 rx{|O G.OϞ ~ f/ xxX[2H )c+#jpUOZYX\ =SG ߨ C|K @; _ ߆'e?LT ?]:?> w
ڔ` D ^S o ~xo[Ӡ3i7B:Q8 V c-ďoi:FM292 ~y_*_闱YN\Fr =xZ3鳎OwW_QEzW ~c]REeaSM}}Hӏ4&.E]u=gMѠ+mF`r Nn$w9g Ma꺢nTuhf 2Xv>އ
a(Û6߭?<= >z 'T Q uw 7Ŀ
KX߁M 2=S'T Q t?. 5Kko\.8S$TOX߀Gw? Zx汴X)C7 ~.i6(Щ=+4{mGӭ¸-]&'t_kV*I< 1)4thtIs qpQ J+>
\m^[aJ5)ny:4o&QEnyAEPEEss
72,PDۢ׃ K
W{Wjr+wگ
iM/;pd?~&?@; 7E4gv8
$l'z 'T Q uw 7Ŀ
Gֱ= ɿ &G?.
iR(5W*$|?w gkmIbHe/_t>tg% y.l}N5[]+Mk0ĠeHdPrss t'UiC,y8 `V%9Z Iia|ܪvi מYG,o}+kk{YbyIeb*sAtի82z WoEK5z*o-eo;n( P u-I)4(HQE QE QE QEhz (X/Đ?}Bk˩ ݏrk0]4>8XzV?
}6$}d^F>nU K ?Bտ k_9x~w'ߞ uDŽtL ؈5c-E/" |_Oo.IH쐍=i*Iw5(ںw ?t 5s.) +tQ2dUt 5V ĺ.jZ"@IRrZƅY4ߡ_;}ų(KyQf1Aǵt ?sZg+ ?F5_oQR&Dg߿]6FuRD u>ڿxl7?IT8'shj^=.=J1rj1Wl$얲cPx;E,p $֟ˏkw qg"4 5(ǛkV/=+ũ)bYl~K#˝J_כ5&\F'I#8/ |w ʾ_Xj
Q: os^T1.M_|TO.;?_ j F?g
N 8nA2F %i =qW,G=5OU u8]Rq?wr'˻ S+۾.ܼ
87Q^ elo/T*?L|ۚ<%<,/v_OKs
B5f/29n0=zqQq(ª = VX@*J(э( f5qJN_EVǞQE O uoѕO uoa5}g O?:߂8Wא| cڽ~]N & O(
(<]>͠@VQ=^~U ̴m&\խ5i :}|}r~9՝f}_>'vVֲ$~^f30^in{\_.O F8to}?${φ|#x^#^n~w=~k~?'K RtO.㌡h![3Zu*ٷճ( ԟ] z_ /W1( ԟ]v~g|Yq<ז0
; b8 ֮s,w9\?uEyStKaª@\,))
(!EPEPEPEPEPzѧts {v>C/"N6`d*J2 gGӧ WqBq_1ZuΓ\X]r?=Ey88M p&pKtO-" wR2
K^- Z< \c>V0^@O 7x2WFjs<kZ(<Т( OFw/6$1[:ޯԯ#q~4|,LVPem=@=YLUxӃV}AUbcUB.Ds5*k ٸAeG>PJ xt͝ b88?*$~@ׯD V k raiJs}Q.20x&mXξ,Z]A-J#`+-E/" <]\a'tZGy.(|lދ~gMK
OZdxDŽU9T6ϯ^<Ϡt 5CZ]].t۫S=s `ڳ%8iVK:nqe+#<.T6U>zWoy3^I {F?J~=G}k)K$$;$de8*G Uӟ4Ocºw}| ]4=ݣ\x$ʠms ?q^ipw\"ȿPs^ Z Q_ 0 GڼU.t}ROM[G#]8wٞ ӫ87}Cgw
vHȩ BM55vof =A _٭`Ygx[6 P,5} >蚊(0( +?>+?> k |TuX q6_ + szk
:u_ Z ߶ Ak_U}Jc 2u/1 [_»ݸG41-bሬ۴}}Eȹ פ_ c? 5gi
@cL\L<68hF_Ih>X 4K7UТ sMj =J7CKo>Օ5s:߀t
~ηaٿ?|gdL8+gG%o?x`دOqȱwc¨&T W_V_ aI=dpG!wu۞սZ1yL50$(l3(:~'ַo
A}a3N*[0ǭ HKQV }G@֜$
9o f$ArNqUOgË05#m?D ) ^ _h/ /5_/ <? 4}Jį+G kpG4"$ r| >S 4Ђ"S
1%R :ȝ 8 ;PKPz PK *A OEBPS/dcommon/feedback.gif7GIF89a '%(hp|fdx?AN5:dfeDGHɾTdQc`g*6DC\?ؘ||{;=E6JUՄfeA= >@,4`H.|`a (Q 9:&[|ځ,4p Y&BDb, !2@,
$wPA'ܠǃ@ CO~/d.`I @8ArHx9H75j L 3B/` P#qD*s 3A:3,H70 P,R @ p!(F oԥ D;"0 ,6 QB RɄHhI@ @VD LCk8@ NBB L2&pClA?DAk%$`I2
#Q+l7 "=& dL&PRSLIP)PɼirqМ'N8 [_}w ;PK- PK *A OEBPS/dcommon/booklist.gifGIF89a 1֥΄kZ{Jk1Rs!BZ)B ) , @I9Z͓Ca % Dz8Ȁ0 FZЌ0P !x8!eL8aWȠFD(~@p+rMS|ӛR$ v
"Z:]ZJJEc{*=AP
BiA '] j4$*
& 9q sMiO?jQ =
, YFg4.778c&$c%9 ;PKː5 PK *A OEBPS/dcommon/cpyr.htm1
Oracle Legal Notices
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
Warranty Disclaimer
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
Restricted Rights Notice
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
Hazardous Applications Notice
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Third-Party Content, Products, and Services Disclaimer
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Alpha and Beta Draft Documentation Notice
If this document is in prerelease status:
This documentation is in prerelease status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
Managing Users in an Oracle Application Express Instance
Oracle Application Express administrators can manage all user accounts within an Oracle Application Express instance on the Manage Developers and Users page. User accounts are particularly useful if a workspace utilizes Application Express Authentication.
When setting up user accounts, Oracle Application Express administrators can take advantage of some manageability attributes, such as allowing the accounts to be locked, their password to have a fixed lifetime, and their password to require change on first use.
Under Manage Workspaces, click Manage Developers and Users.
The Manage Developers and Users page appears.
Click Create.
The Create/Edit User page appears.
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.
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".
Under Developer Privileges:
User is a developer - To add this user as a developer, select Yes. For end users, select No.
Developers can create and modify applications and database objects and 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.
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.
Under Manage Workspaces, click Manage Developers and Users.
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.
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.
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.
Select a user.
The Create/Edit User page appears.
Click Delete User.
Confirm your selection and click OK.
PKdw&. !. PK *A OEBPS/wrkspc.htm1
Workspace and Application Administration
1Workspace and Application Administration
In an Oracle Application Express development environment, users log in to a shared work area called a workspace. A workspace is a virtual private database that enables multiple users to work within the same Oracle Application Express installation while keeping their objects, data and applications private. This flexible architecture enables a single database instance to manage thousands of applications.
Developers can create and edit applications and view developer activity, session state, workspace activity, application, and schema reports. Workspace administrators additionally can create and edit user accounts, manage groups, and manage development services. This section describes how to perform Workspace administration tasks and access many of these reports.
Disabling PL/SQL Program Unit Editing for a Workspace
By default, developers can change and compile PL/SQL source code when browsing database procedures, packages, and functions in SQL Workshop Object Browser. Workspace administrators can disable PL/SQL program unit editing by selecting Do not allow PL/SQL program unit editing on the Preferences page.
To disable PL/SQL program unit editing:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Click Set Workspace Preferences.
The Set Workspace Preferences page appears.
Under PL/SQL Editing, select one of the following:
Allow PL/SQL program unit editing
Do not allow PL/SQL program unit editing
If you select Do not allow PL/SQL program unit editing, developers can still create and replace PL/SQL program units using scripts or SQL Commands.
There are two different ways to configure login controls:
An Oracle Application Express administrator enables account login controls for all Application Express accounts in all workspaces across a development instance.
If your Oracle Application Express administrator configures these preferences for an instance, those settings display as the defaults for all workspaces. See "Enabling Login Controls for All Workspaces".
If the Oracle Application Express administrator does not enable login controls across an entire instance, then each Workspace administrator can enable the following controls on a workspace-by-workspace basis:
Require end-user account expiration and locking
Set up a maximum number of failed login attempts for end-user accounts
Set the password lifetime for end-user accounts, that is, the number of days an end-user account password can be used before it expires
Tip:
This feature applies only to accounts created using the Application Express user creation and management facilities. It provides additional authentication security for applications. See "Managing Application Express Users".
To enable login controls for a workspace:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Workspace Preferences, click Set Workspace Preferences.
Under Account Login Control:
Account Expiration and Locking - Click Enable.
If you select Enable, end-user account passwords will expire after a configurable time period, accounts will be locked after a configurable number of authentication failures, and account passwords can be set to expire after the first use.
If your Oracle Application Express administrator set the Require User Account Expiration and Locking preference to Yes, this preference defaults to Enable and you cannot update it.
Maximum Login Failures Allowed - Enter a number for the maximum number of consecutive unsuccessful authentication attempts allowed before an end-user account is locked. If you do not specify a value in this field, the instance-level setting for Maximum Login Failures Allowed is used.
User Account Lifetime (days) - Enter a number for the maximum number of days an end-user account password may be used before the account expires. If you do not specify a value in this field, the instance-level setting for Account Password Lifetime is used.
Click Apply Changes.
Specifying a Workspace Message
You can display a message on the workspace home page by defining a Workspace Message on the Set Workspace Preferences page.
To define a workspace message:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Click Set Workspace Preferences.
The Set Workspace Preferences page appears.
Under Workspace Message, enter a message in the Message field. To format the display include standard HTML tags.
Running the Create Application Wizard creates an application model. This model contains basic application property values, such as the application pages and page definitions, DML processes, and multi-row operation processes. When you create a new application, you can base it on an existing application model, making the creation process more productive.
You can remove unwanted application models on the Application Models page.
To delete an application model:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Applications, click Application Models.
On the Application Models page:
To narrow the results, select the owner and click Go.
To search for a model, enter a case insensitive query in the Model field and click Go.
Select the models you want to delete and click Delete Checked.
PK݃- ( PK *A OEBPS/aadm_build_status.htm
Changing Build Status for Multiple Applications
Changing Build Status for Multiple Applications
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 of an application as follows:
To change the Build Status of applications within the current workspace:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Workspace, click Manage Application Build Status.
From Build Status, select one of the following:
Run and Build Application - Developers can both run and edit an application.
Run Application Only - Developers can only run an application.
Click Apply Changes.
PKx\!p
PK *A OEBPS/adm_mg_service_set.htm
Managing Service
Managing Service
Oracle Application Express administrators use the settings under Manage Service to create a site-specific tasks list, manage activity log entries, manage session state, monitor the mail queue, and view a report of installed translations.
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.
On the Create/Edit Site-Specific Tasks page, you can specify the following:
Display Sequence - Indicate the relative order of this task within the list.
Display Location - Indicate the page on which the task should display (that is, the Workspace Login page or Workspace home page).
Task Name - Enter a name for this task.
Tasks Link - Enter the link target for this task using either a relative URL (for example, using f?p syntax) or an absolute URL (such as http://otn.oracle.com).
Page view activity logs track user activity for an application. Developers enable logging within their application using the Logging attribute on the Edit Definition page.
The Application Express engine actually uses two logs to track user activity. At any given time, one log is designated as current. For each rendered page view, the Application Express engine inserts one row into the log file. A log switch occurs at the interval listed on the Manage Activity Logs page. At that point, the Application Express engine removes all entries in the noncurrent log and designates it as current.
The External Clicks Log counts clicks from an Oracle Application Express application to an external site. You can implement this functionality using the APEX_UTIL.COUNT_CLICK procedure.
This table records authentication events by developers and administrators accessing the Oracle Application Express environment and by end users of Oracle Application Express applications that use the built-in login APIs available to developers. Log entries are aged out of the log tables and purged periodically.
On the Manage Login Access Log page, click Delete Entries.
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.
To view a report of session statistics, click Count Sessions.
To purge the selected sessions, click Purge Sessions.
Viewing Session Details Before Purging
Before purging sessions, Oracle Application Express administrators can use the Recent Sessions page to first view a listing of recent sessions and then drill down on session details.
To control the number of rows that display, make a selection from the Display list and click Go.
To delete all log entries, click Truncate.
Viewing Installed Translations
Oracle Application Express administrators can view a page showing what translated languages have been installed within the current development instance.
Managing Themes for an Oracle Application Express Instance
Oracle Application Express administrators manage the theme repository for an entire Oracle Application Express instance. Oracle Application Express administrators can add a theme to the repository or delete a theme.
Under Manage Shared Components, click Public Themes.
The Public Themes page appears.
Select the theme to be deleted.
Click Delete.
Modifying a Public Theme
You cannot edit a public theme directly. To modify a public theme, you must create a new application using the theme, modify it, and then manually add it to the theme repository.
PK~H PK *A OEBPS/aadm_wrkspc_del.htmr
Terminating a Workspace Service
Terminating a Workspace Service
Terminating a workspace service removes all data, database objects, database schemas, tablespaces, applications, scripts, and files from the current Oracle Application Express instance.
To submit a request to the Oracle Application Express administrator to terminate workspace service:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Workspace, click Request Service Termination.
Click the Request Termination button.
Confirm your request by clicking Terminate Service.
PK~A= PK *A OEBPS/aadm_storage_request.htm o
Requesting Additional Storage
Requesting Additional Storage
To request additional storage space for your workspace you must submit a request to the Oracle Application Express administrator.
Specify the amount of storage to add and click Request Storage.
Tip:
To view a report of available storage space, click Schemas Utilizing Space in Tablespaces and then click the Detailed Tablespace Utilization Report (may take several seconds) link.
PK PK *A OEBPS/adm_activity.htm "
Monitoring Activity Across a Development Instance
Monitoring Activity Across a Development Instance
Oracle Application Express administrators can monitor end user and developer activity for an Oracle Application Express instance on the Monitor Activity page.
Workspace administrators can create new user accounts, manage existing user accounts, and change user passwords. User accounts are particularly useful if you are using Application Express Authentication. Application Express Authentication checks the user name and password against the Oracle Application Express account repository. The Oracle Application Express account repository contains account information for developers and administrators when they log in to Oracle Application Express applications.
If the workspace administrator enables the Account Locking/Expiration feature for end user accounts, new account management attributes are exposed. Accounts may be locked, unlocked, or expired. Passwords for those accounts can also have restrictions, such as a fixed lifetime, a maximum number of consecutive incorrect passwords when attempting to log in, and a requirement to be changed on first use.
Workspace administrators can create three different types of user accounts:
Developers can create and edit applications and view developer activity, session state, workspace activity, application, and schema reports.
Workspace administrators perform administrator tasks specific to a workspace, such as managing user accounts, managing groups, altering passwords of users within the same workspace, and managing development services.
End users have no development privileges and can access only applications that do not use an external authentication scheme.
From the Administration list, click Manage Application Express Users.
The Manage Application Express Users page appears.
Click Create.
The Create User page appears.
Under User Identification, enter the appropriate information.
Under Developer Privileges:
Accessible Schemas (null for all) - Enter a colon-delimited list of schemas for which this developer has permissions when using the SQL Workshop. This list of schemas restricts the user to a subset of the full set of schemas provisioned for the workspace and determines what schema names the user sees in SQL Workshop.
Default Schema - Identifies the default schema used for data browsing, application creation, and SQL script execution.
User is a developer - To add this user as a developer, select Yes. For end users, select No.
Developers can create and modify applications and database objects and 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.
Under Account Control:
Set Account Availability - Select Unlocked to allow a user to log in to this account. Select Locked to prevent a user from logging 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.
Workspace administrators can edit existing user accounts.
To edit an existing user account:
Navigate to the Workspace home page.
From the Administration list, click Manage Application Express Users.
The Manage Application Express Users page appears. You can control how the page displays using the navigation bar at the top of the page. See "About the Navigation Bar".
Select a user.
The Edit User page appears.
Under Edit User, update the username or email address.
Under Password, edit the current password by typing a new password in the Password and Confirm Password fields.
Under Developer Privileges:
Accessible Schemas (null for all) - Enter a colon-delimited list of schemas for which this developer has permissions when using the SQL Workshop. This list of schemas restricts the user to a subset of the full set of schemas provisioned for the workspace and determines what schema names the user sees in SQL Workshop.
Default Schema - Identifies the default schema used for data browsing, application creation, and SQL script execution.
Specify the privileges for this user:
User is a developer - Developers create and modify applications and database objects and view developer activity, session state, workspace activity, application, and schema reports.
User is a workspace administrator - 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.
Under Account Control:
Account Availability - Select Locked to prevent a user from logging in to this account. Select Unlocked to enable the account to be used.
Developer/Administrator Password and End User Password - Shows the a status of either valid or expired. A password expires when its lifetime span passes.
Expire Password - Select this option to force the user to enter a new password the next time they log in. This option does not appear for invalid accounts or for workspaces not using the password expiration/account locking functionality.
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 "Configuring Security Settings".
Under User Groups, select an optional user group.
You can use groups to restrict access to various parts of an application. Groups are primarily useful when using Application Express Authentication.
Under Additional Attributes, update the user's name or add descriptive information about the user or account.
The Manage Application Users page navigation bar contains the following controls:
Find. Use the Find field to search for an specific user. Enter a case insensitive query and click Go.
Show. Select the type of user account to view and click Go. Options include:
All Accounts
Expired Accounts
Locked Accounts
Unlocked Accounts
My Account
Developer Accounts
View. Select a display mode and click Go. Display options include:
Icons (the default) displays each user as a large icon. Different colors indicate the user role, and a lock indicates a locked account. An hourglass indicates an expired account.
Details displays each user as a line in a report. To expand the report, select the Show Additional Report Columns check box and click Go.
Display. Select the number of users to display on the page and click Go.
Deleting or Locking User Accounts
Workspace administrators can delete or lock user accounts.
To delete or lock a user account:
Navigate to the Workspace home page.
From the Administration list, click Manage Application Express Users.
The Manage Application Express Users page appears. You can control how the page displays using the navigation bar at the top of the page. See "About the Navigation Bar".
Select a user.
The Edit User page appears.
To delete a user:
Click the Delete User button.
Confirm your selection and click OK.
To lock the account:
Scroll down to the Account Controls section.
For Account Availability, select Locked.
Click Apply Changes.
Changing an End User Password
To change an end user password:
Navigate to the Workspace home page.
From the Administration list, click Manage Application Express Users.
The Manage Application Express Users page appears.
Select a user.
Tip:
To search for an existing user, enter a query in the Find field and click Go.
Under Password, type a new password in the Password and Confirm Password fields.
Click Apply Changes.
Using Groups to Manage Application Express Users
You can create groups to restrict access to various parts of an application. Keep in mind, however, that groups are not portable over different authentication schemes. Groups are primarily useful when using Application Express Authentication (Internal Cookie User authentication).
Make a selection from the Workspace list at the top of the page and click Go.
The Workspace Details page appears.
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 and 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.
Tablespace Utilization. Displays the tablespace used with each workspace schema.
Applications. Lists all applications within the workspace.
If you are managing a large hosted Oracle Application Express instance, periodically purging inactive workspaces can free up resources for other users. The process of purging inactive workspaces consists of the following steps:
Identify inactive workspaces.
Remove the resources associated with each inactive workspace.
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 = APEX_030200;
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.
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:
Identify the schemas used by the workspaces to be deleted by joining the table containing the identified inactive workspaces to wwv_flow_company_schemas.
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;
Removing a Workspace
Removing 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.
Under Workspace Reports, click Existing Workspaces.
Under the Action column, click Delete.
Follow the on-screen instructions.
Removing Workspaces in a Runtime Development Environment
To remove a workspace in a runtime development 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_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.
Locking a Workspace
Oracle Application Express 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.
For Workspace, select the workspace you want to lock and click Next.
Review the information about applications and users and click Lock Workspace.
Exporting and Importing a Workspace
To move a workspace and all associated users to a new Oracle Application Express instance, an Oracle Application Express administrator must 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 use this file to import your workspace into another Oracle Application Express instance.
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.
Click Browse, select a workspace export file, and click Next.
To install the workspace, click Install.
Follow the on-screen instructions.
PK&2Ů^ ^ PK *A OEBPS/adm_roles.htm!
What Is an Oracle Application Express Administrator?
What Is an Oracle Application Express Administrator?
Oracle Application Express administrators are responsible for managing an entire Oracle Application Express instance.
In the Oracle Application Express, users log in to a shared work area called a workspace. These users are divided into three primary roles:
Developers create and edit applications.
Workspace administrators are developers who also perform administrator tasks specific to their workspace such as managing user accounts, monitoring workspace activity, and viewing log files. See "Workspace and Application Administration".
Oracle Application Express administrators are superusers that manage the entire hosted instance using the Oracle Application Express Administration Services application.
See Also:
Refer to the appropriate installation guide for your platform for information about installing Oracle Application Express
About the Manage Service Page
Oracle Application Express administrators use the Manage Service page to configure service for an Oracle Application Express instance.
Environment settings control Oracle Application Express configuration and apply to all workspaces within the current Oracle Application Express instance.
An Oracle Application Express runtime environment enables you to run production applications, but it does not provide a Web interface for administration. A runtime environment only includes the packages necessary to run your application, making it a more hardened environment.You administer the Oracle Application Express runtime environment using SQL*Plus and the APEX_INSTANCE_ADMIN API. To learn more, see "APEX_INSTANCE_ADMIN" in Oracle Application Express Application Builder User’s Guide.
To install an exported application into a runtime installation, you must:
Export the workspace from the Application Express instance where the application was developed as described in "Exporting and Importing a Workspace".
Use SQL*Plus to import your workspace in to the runtime environment:
Connect as APEX_030200, SYS, SYSTEM, or any schema to which the role APEX_ADMINISTRATOR_ROLE has been granted.
Run the workspace import file.
If the workspace export file was created with a version of Oracle Application Express lower than 3.2, you must connect as APEX_030200.
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.
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:
Under Manage Environment Settings, click Feature Configuration.
Under SQL Workshop, enter the attributes described in Table 2-1.
Table 2-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.
Click Apply Changes.
Enabling Database Monitoring
Setting Enable Database Monitoring to Yes enables monitoring withing SQL Workshop. Before you can access the Database Monitoring page, an Oracle Application Express administrator must enable database monitoring.
Under Manage Environment Settings, click Feature Configuration.
Scroll down to Monitoring.
For Enable Database Monitoring, select Yes.
Click Apply Changes.
Note:
Only users having a database user account that has been granted a DBA role can access the Database Monitor page.
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.
Turning Off Cookies Used to Populate the Login Form for Application Express
Oracle Application Express administrators can control if a convenience cookie is sent to the user's computer whenever a developer or administrator logs in to a workspace from the Application Express Login page. By default, the Set Workspace Cookie option is set to Yes.
If selected, Oracle Application Express sends a persistent cookie that:
combines the last used workspace name and user name
has a lifetime of six months
is read to populate the Application Express Workspace Login form (but not the Oracle Application Express Administration Services Login form)
Note:
If your computer has received this cookie, you can physically remove it from its persistent location on disk using browser tools or system utilities. The cookie is named ORA_WWV_REMEMBER_UN. In older releases of Oracle Application Express, this cookie was named ORACLE_PLATFORM_REMEMBER_UN. It may exist for each Oracle Application Express service accessed having distinct hostname and path components.
To prevent a cookie from being sent to the user's computer when logging in:
Under Manage Environment Settings, click Security.
Locate the Security section.
For Set Workspace Cookie, select No.
Click Apply Changes.
Disabling Access to Oracle Application Express Administration Services
Oracle Application Express administrators can restrict user access to Oracle Application Express Administration Services. This prevents any user from logging in to Oracle Application Express Administration Services.
To disable user access to Oracle Application ExpressAdministration Services:
Under Manage Environment Settings, click Security.
Locate the Security section.
For Disable Administrator Login, select Yes.
Click Apply Changes.
Setting this value and logging out prevents anyone from logging in to Oracle Application Express Administration Services.
Enabling Administrator Login
To reverse this setting and enable administrator login:
Connect in 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 statements:
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER('DISABLE_ADMIN_LOGIN', 'N');
commit;
END;
/
Disabling Access to Oracle Application Express Internal Applications
The applications that constitute Oracle Application Express (such as Application Builder and SQL Workshop) exist within a workspace named Internal. To restrict user access to Internal applications, select Yes from Disable Workspace Login. Selecting Yes in production environments prevents all users from running applications (such as Application Builder and SQL Workshop) in the Internal workspace. Administrators who use this feature should also consider disabling user access to Oracle Application Express Administration Services.
Under Manage Environment Settings, click Security.
Locate the Security section.
From Disable Workspace Login, select Yes.
Selecting Yes prevents users from logging in to the Internal workspace.
Click Apply Changes.
Disabling Public File Upload
Use the Allow Public File Upload attribute to control whether unauthenticated users can upload files in applications that provide file upload controls.
Under Manage Environment Settings, click Security.
Locate the Security section.
From Allow Public File Upload, select one of the following:
Yes enables unauthenticated users to upload files in applications in the Internal workspace.
No prevents unauthenticated users from uploading files in applications in the Internal workspace.
Click Apply Changes.
Restricting User Access by IP Address
Oracle Application Express administrators can restrict user access to an Oracle Application Express instance by creating a Runtime setting named RESTRICT_IP_RANGE.
Under Manage Environment Settings, click Security.
Locate the Security section.
For Disable Administrator Login, select No.
In Restrict Access by IP Address, enter a comma-delimited list of IP addresses. Use an asterisk (*) to specify a wildcard.
You can enter IP addresses from one to four levels. For example:
141, 141.* ...
192.128.23.1 ...
Note:
When using wildcards, do not include additional numeric values after wildcard characters. For example, 138.*.41.2.
Click Apply Changes.
Requiring HTTPS
Secure Socktets Layer (SSL) is a protocol for managing the security of data transmitted on the Internet. For Web applications, SSL is implemented by using the HTTPS protocol. Oracle recommends that you run Oracle Application Express applications using SSL (HTTPS protocol) to prevent any sensitive data from being sent over an unencrypted (cleartext) communication channel.
You can configure both your Oracle Application Express instance and all related applications to require HTTPS by setting the Require HTTPS attribute to Yes on the Manage Service page.
Note:
If you set Require HTTPS to Yes, you will only be able to log in to an Oracle Application Express workspace or Oracle Application Express Administration Services over HTTPS.
To require HTTPS for an Oracle Application Express instance:
Under Manage Environment Settings, click Security.
Under Session Timeout For Application Express, specify the following attributes:
Maximum Session Length in Seconds - Enter a positive integer representing how many seconds a session can exist for Oracle Application Express applications (that is, Application Builder, SQL Workshop, and so on). Leave the value NULL to revert the value to the default of 28800 seconds (or 8 hours). This session duration may be superseded by the operation of the job that runs every eight hours which deletes sessions older than 24 hours.
Maximum Session Idle Time in Seconds - Enter a positive integer representing how many seconds a session may remain idle for Oracle Application Express applications (that is, Application Builder, SQL Workshop, and so on). Leave the value null to revert the value to the default of 1 hour (3600 seconds).
Excluding Domains from Regions of Type URL and Web Services
It is possible to restrict regions of type URL and Web services for the entire Oracle Application Express instance. The Oracle Application Express administrator defines excluded domains and regions of type URL. If a Web reference or region of type URL contains an excluded domain, an error displays informing the user that it is restricted.
To exclude a domain from regions of type URL and Web services:
Under Manage Environment Settings, click Security.
In Domain Must Not Contain, enter a colon-delimited list of excluded domains.
Click Apply Changes.
Enabling Login Controls for All Workspaces
By default, no login controls are enabled across an Oracle Application Express instance. Oracle Application Express administrators can enable login controls for all accounts in all workspaces across an entire development instance. Account login controls include:
Require user account expiration and locking
Set up a maximum number of failed login attempts
Set the lifetime of a password before prompted for a new one
If the Oracle Application Express administrator does not enable login controls for an entire instance then each Workspace administrator can enable the following controls on a workspace-by-workspace basis. See "Enabling Login Controls for a Workspace".
Note that Account Login control affect applications that use the Application Express user account creation facilities and authentication against those accounts.
Under Manage Environment Settings, click Security.
Scroll down to Account Login control.
Under Account Login Control:
Require User Account Expiration and Locking - Select Yes to enable this feature for all workspaces across an entire Oracle Application Express instance. This feature applies to end-user accounts created using the Application Express end-user account management interface.
Select No to relinquish control to each Workspace administrator.
Maximum Login Failures Allowed - Enter a number for the maximum number of consecutive unsuccessful authentication attempts allowed before a developer or administrator account is locked. If you do not specify a value in this field, the default value is 4.
This setting applies to Application Express administrator and developer accounts. It does not apply to end user accounts.
The value you enter is used as the default for the workspace-level Maximum Login Failures Allowed preference, if the Workspace administrator does not specify a value. That preference is used for end-user accounts within the respective workspace.
Account Password Lifetime (days) - Enter a number for the maximum number of days a developer or administrator account password may be used before the account expires. If you do not specify a value in this field, a default value is 45 days.
This setting applies to accounts used to access the Application Express administration and development environment only. It does not apply to end-user accounts used by applications developed in Application Express.
The value you enter is used as the default workspace-level End User Account Lifetime preference, if the Workspace administrator specifies no value. That preference is used for end-user accounts within the respective workspace.
Click Apply Changes.
Tip:
This feature applies only to accounts created using the Application Express user creation and management facilities. It provides additional authentication security for applications. See "Managing Application Express Users".
About Password Policies
Oracle Application Express administrators can enable password policies for:
All users across all workspaces (that is, Workspace administrators, developers, and end users).
Oracle Application Express administrators can set up restrictions for all users, including password characters, lengths, words, and differences in consecutive passwords.
Users logging in to Oracle Application Express Administration Services
Turning on the strong password requirement for Oracle Application Express adds another layer of security to prevent hackers from determining an administrator's password. When this option is selected, passwords must meet these requirements:
consist of at least six characters
contain at least one lowercase alphabetic character, one uppercase alphabetic character, one numeric digit, and one punctuation character
cannot include the username
cannot include the word Internal
cannot contain any words shown in the Must Not Contain Workspace Name field in this section
Under Manage Environment Settings, click Security.
To set up a password policy for Workspace administrators, developers, and end users, scroll down to Workspace Password Policy and specify the attributes described in Table 2-2.
Table 2-2 Workspace Password Policy Attributes
Attribute
Description
Minimum Password Length
Enter a number for the minimal character length for passwords.
Minimum Password Differences
Enter a positive integer or 0.
When users change their password, the new password must differ from the old password by this number of characters. The old and new passwords are compared, character-by-character, for differences such that each difference in any position common to the old and new passwords counts toward the required minimum difference.
Must Contain At Least One Alphabetic Character
Select Yes to require that user passwords contain at least one alphabetic character. The Alphabetic Characters field lists the letters considered alphabetic characters.
Must Contain At Least One Numeric Character
Select Yes to require that user passwords contain at least one numeric character: 0,1,2,3,4,5,6,7,8, 9.
Must Contain At Least One Punctuation Character
Select Yes to require that user passwords contain at least one punctuation character. The Punctuation Characters field lists the symbols considered punctuation characters.
Must Contain At Least One Upper Case Character
Select Yes to require that user passwords contain at least one uppercase alphabetic character.
Must Contain At Least One Lower Case Character
Select Yes to require that passwords for users contain at least one lowercase alphabetic character.
Must Not Contain Username
Select Yes to prevent user passwords from containing the username, regardless of case.
Must Not Contain Workspace Name.
Select Yes to prevent user passwords from containing the workspace name, regardless of case.
Must Not Contain
Enter words, separated by colons, that may not be included in user passwords. These words may not appear in the password in any combination of uppercase or lowercase.
This feature improves security by preventing the creation of some simple, easy-to-guess passwords based on words like hello, guest, welcome, and so on.
Alphabetic Characters
Enter new text or edit the existing text. This is the set of characters used in password validations involving alphabetic characters.
Punctuation Characters
Enter new text or edit the existing text. This is the set of characters used in password validations involving punctuation characters.
Next, set up a password policy for service administrators.
Scroll down to the Service Administrator Password Policy and specify one of the following:
Use policy specified in Workspace Password Policy - Applies the password rules specified above in Workspace Password Policy to service administrator passwords.
Use default strong password policy - Applies the default strong password policy to service administrator passwords. To learn more, see item Help.
Click Apply Changes.
Restricting Access to Oracle Application Express by Database Access Descriptor (DAD)
mod_plsql and the embedded PL/SQL gateway support a directive which enables you to name a PL/SQL function which will be called for each HTTP request. You can use this functionality to restrict the procedures that can be invoked through the embedded PL/SQL gateway or mod_plsql. The function returns TRUE if the named procedure in the current request is allowed and FALSE if it is not allowed. You can use this function to enforce access restrictions for Oracle Application Express on a per-database access descriptor (DAD) basis.
Oracle Application Express ships with a request validation function named wwv_flow_epg_include_modules.authorize. This function specifies access restrictions appropriate for the standard DAD configured for Oracle Application Express.
During installation, the installer also creates a PL/SQL function in the Oracle Application Express product schema (APEX_030200). You can change and recompile this function to restrict access. The source code for this function is not wrapped and can be found in the Oracle Application Express product core directory in the file named wwv_flow_epg_include_local.sql. The source code is as follows
CREATE OR REPLACE FUNCTION
wwv_flow_epg_include_mod_local(
PROCEDURE_NAME IN VARCHAR2)
RETURN BOOLEAN
IS
BEGIN
RETURN FALSE; -- remove this statement when
you add procedure names to the "IN" list
IF UPPER(procedure_name) IN (
'') THEN
RETURN TRUE;
ELSE
RETURN FALSE;
END IF;
END wwv_flow_epg_include_mod_local;
/
To add names of procedures that should be allowed:
Remove or comment out the RETURN FALSE statement that immediately follows the BEGIN statement:
...
BEGIN
RETURN FALSE; -- remove this statement when
you add procedure names to the "IN" list
...
Add names to the clause representing procedure names that should be allowed to be invoked in HTTP requests. For example to allow procedures PROC1 and PROC2 the IN list you would write IN ('PROC1', 'PROC2').
After changing the source code of this function, alter the Oracle Application Express product schema (APEX_030200) and compile the function in that schema.
To alter the product schema, APEX_030200
Log in to SQL Command Line (SQL*Plus) as SYS.
Alter the product schema (APEX_030200) by entering the following command:
ALTER SESSION SET CURRENT_SCHEMA APEX_030200;
Compile the function wwv_flow_epg_include_local.sql.
The wwv_flow_epg_include_mod_local function is called by Oracle Application Express's request validation function which itself is called by the embedded PL/SQL gateway or mod_plsql. The Oracle Application Express function first evaluates the request and based on the procedure name, approves it, rejects it, or passes it to the local function, wwv_flow_epg_include_mod_local, which can evaluate the request using its own rules.
When you create new Database Access Descriptors for use with Oracle Application Express, the request validation function directive should be specified. Specifically, the function wwv_flow_epg_include_modules.authorize should be named in the directive PlsqlRequestValidationFunction in the Database Access Descriptor entry in dads.conf.
If you have no additional restrictions beyond those implemented in the wwv_flow_epg_include_modules.authorize function, there is no need to take any action with respect to the source code for the wwv_flow_epg_include_mod_local function.
The PL/SQL Request Validation Function directive is only available in Oracle Application Server 10g and Oracle HTTP Server 11g or later, as well as the embedded PL/SQL gateway in Oracle Database 11g or later. This directive is not available in Oracle HTTP Server Release 9.0.3.
Configuring Email Settings
To enable Oracle Application Express to send mail, an Oracle Application Express administrator must configure email settings
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" for your configuration scenario in Oracle Application Express Installation Guide.
Tip:
You can configure Oracle Application Express to automatically email users their login credentials when a new workspace request has been approved. To learn more, see "Specifying a Provisioning Mode".
Under Manage Environment Settings, click Instance Settings.
Under Email, enter the following:
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.
SMTP Host Port - Defines the port the SMTP server listens to for mail requests. The default setting is 25.
Administration Email Address - Defines the "from" address for administrative tasks that generate email, such as approving a provision request or resetting a password.
Click Apply Changes.
Configuring Email in a Runtime Environment
To configure Oracle Application Express to send mail 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.GET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
END;
For a description of email parameters, see Table 2-3.
Table 2-3 Email Parameters
Parameter Name
Description
SMTP_FROM
Defines the "from" address for administrative tasks that generate email, such as approving a provision request or resetting a password.
Enter a valid email address, for example:
someone@somewhere.com
SMTP_HOST_ADDRESS
Defines the server address of the SMTP server. If you are using another server as an SMTP relay, change this parameter to that server's address.
Default setting:
localhost
SMTP_HOST_PORT
Defines the port the SMTP server listens to for mail requests.
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.
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).
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 must configure the following printing settings:
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.
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.
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 Classic Report Region Print Attributes" in Oracle Application Express Application Builder User’s Guide.
Tip:
If you are running Oracle Application Express with Oracle Database 11g Release 1 (11.1), you must enable network services to use report printing. See "Enabling Network Services in Oracle Database 11g" for your configuration scenario in Oracle Application Express Installation Guide.
Under Manage Environment Settings, click Instance Settings.
Scroll down to Report Printing:
For Oracle BI Publisher, select one of the following:
Standard Support - This is the default setting. Standard Support enables you to print report regions and report queries using either the built-in templates provided with Oracle Application Express or other XSL-FO compatible formats you provide. This setting does not support RTF (rich text format).
Standard Support provides declarative formatting of report regions and report queries with basic control over page attributes, including orientation, size, column heading formats, page header, and page footer.
Advanced Support - Requires a valid license of Oracle BI Publisher (also known as Oracle XML Publisher). Advanced Support provides you with all the capabilities of the Standard setting plus the ability to define RTF-based report layouts developed using the BI Publisher Word Template Builder.
See Also:
PDF Printing in Application Express 3.1 to learn more about installing and configuring Oracle BI Publisher. Go to:
For Print Server Protocol, select the protocol that the print server uses.
For Print Server Host Address, specify the host address of the print server engine.
For Print Server Port, define the port of the print server engine. By default, this is set to 8888 when the report server is installed.
For Print Server Script, define the script that is the print server engine. The default setting is:
/xmlpserver/convert
Click Apply Changes.
Configuring Report Printing Settings in a Runtime Environment
To configure report printing settings 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.SET_PARAMETER(PARAMETER_NAME, PARAMETER_VALUE);
END;
For a description of available parameters, see Table 2-5.
Table 2-5 Report Printing Parameters in Runtime Environment
Parameter Name
Description
PRINT_BIB_LICENSED
Specify either standard support or advanced support. Advanced support requires an Oracle BI Publisher license. Valid values include:
STANDARD
ADVANCED
PRINT_SVR_PROTOCOL
Valid values include:
http
https
PRINT_SVR_HOST
Specifies the host address of the print server converting engine, for example, localhost. Enter the appropriate host address if the print server is installed at another location.
PRINT_SVR_PORT
Defines the port of the print server engine, for example 8888. Value must be a positive integer.
PRINT_SVR_SCRIPT
Defines the script that is the print server engine, for example:
Under Manage Environment Settings, click Instance Settings.
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.
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.
A login message displays on the Oracle Application Express login page. Oracle Application Express administrators can create a login message using the Login Message section of the Messages page.
Under Manage Environment Settings, click Messages.
For Login Message, select No Message.
Click Apply Changes.
Managing a System Message
System messages display on the Workspace home page, Application Builder home page, Application home page, SQL Workshop home page, and the Oracle Application Express Utilities page.
Oracle Application Express administrators can create a system message using the System Message section of the Messages page.
Under Manage Environment Settings, click Messages.
For System Message, select No Message.
Click Apply Changes.
PK'AP P PK *A OEBPS/wkspc_def.htm>
Leveraging Application Builder Defaults
Leveraging Application Builder Defaults
Application Builder Defaults enable developers to reduce the number of steps needed to create a new application. By configuring these attributes, developers can exit the Create Application Wizard early and can create a new application in two simple steps.
Application Builder Defaults are specific to each workspace. These attributes define preferences for tabs, authentication schemes, themes, and globalization when running the Create Application Wizard. When a Workspace administrator configures these attributes, developers within that workspace can utilize these defaults and exit the Create Application Wizard after two easy steps
Configuring Application Builder Defaults
To configure Application Builder Defaults:
On the Workspace home page, click the Application Builder icon.
From the Tasks list, select Application Builder Defaults.
The Manage Application Builder Defaults page appears.
For each section of the page, select the appropriate default.
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.
Determining the Oracle 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:
Use SQL*Plus to connect to the database.
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.
Note:
All schema and workspace names used as arguments to procedures in the APEX_SITE_ADMIN_PRIVS package are used exactly as they are provided by the caller.
For example, if you pass an argument value such as p_schema =>'system', the lower-case schema name 'system' will be recorded and referenced. This example could return unexpected results if you really meant to reference the common schema name SYSTEM, which would be referenced using upper case.
Granting the Privilege to Assign Oracle Default Schemas
The DBA can grant an Oracle Application Express administrator the ability to assign Oracle default schemas to workspaces by using SQL*Plus to run the APEX_SITE_ADMIN_PRIVS.UNRESTRICT_SCHEMA procedure from within the Application Express engine schema. For example:
Revoking the Privilege to Assign Oracle Default Schemas
The DBA can revoke this privilege using SQL*Plus to run the APEX_SITE_ADMIN_PRIVS.RESTRICT_SCHEMA procedure from within the Application Express engine schema. For example:
This example would prevent the Oracle Application Express administrator from assigning the SYSTEM schema to any workspace. It does not, however, prevent workspaces that have already had the SYSTEM schema assigned to them from using the SYSTEM schema.
If a schema has been designated as restricted using the RESTRICT_SCHEMA procedure, the DBA can designate specific workspaces as exceptions by running the APEX_SITE_ADMIN_PRIVS.CREATE_EXCEPTION procedure. For example:
This example would prevent the Oracle Application Express administrator from assigning the SYSTEM schema to the workspace named AUDITOR_WORKSPACE. However this restriction only applies to workspace provisioning requests processed after the REMOVE_EXCEPTION procedure has been run. If the AUDITOR_WORKSPACE already had the SYSTEM schema assigned to it, this method would not prevent that workspace from continuing to use the schema.
Removing Workspace Exceptions for a Schema
The DBA can remove all workspace exceptions for a schema by using SQL*Plus to run the APEX_SITE_ADMIN_PRIVS.REMOVE_WORKSPACE_EXCEPTIONS procedure from within the Application Express engine schema. For example:
This example would prevent the Oracle Application Express administrator from assigning the SYSTEM schema to any workspaces if the SYSTEM schema were already restricted, but had one or more exceptions previously created for it.
Removing Schema Exceptions for a Workspace
The DBA can remove all schema exceptions for a workspace by using SQL*Plus to run the REMOVE_SCHEMA_EXCEPTIONS procedure from within the Application Express engine schema. For example:
This example would prevent the Oracle Application Express administrator from assigning any restricted schemas to the workspace named AUDITOR_WORKSPACE if that workspace had exceptions previously created for it with respect to any restricted schemas.
Determining the Privilege Status
The DBA can determine the current status of the privilege by using SQL*Plus to run the APEX_SITE_ADMIN_PRIVS.REPORT procedure. For example:
SET SERVEROUTPUT ON
EXEC APEX_030200.APEX_SITE_ADMIN_PRIVS.REPORT;
This example would display the text of a query that dumps the tables that defines the schema and workspace restrictions.
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;
When reviewing the output of this query, remember the following:
A schema name in the SCHEMA column indicates that the schema is restricted.
Schemas that are not listed are not restricted and may be assigned to any workspace.
A workspace name next to a schema name means that an exception exists for the schema for the named workspace.
You can run this query in SQL*Plus as shown above, or you can change it and format the output.
PKi
PK *A OEBPS/wkspc_adm_about.htm#
About Workspace Administration
About Workspace Administration
Oracle Application Express enables a single database to host large numbers of users. Users work in a dedicated work area called a workspace. A workspace is a virtual private database that enables multiple users to work within the same Oracle Application Express installation while keeping their objects, data and applications private. This flexible architecture enables a single database instance to manage thousands of applications.
Log entries older then one month are automatically deleted. Workspace administrators can manually purge developer logs and the External Count Clicks log on the Log files page.
The Developer Activity Log tracks changes to applications within the current workspace.
To purge the Developer Activity Log:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Logs, click Manage Developer Activity Log.
Click Purge Developer Log.
Purging the External Click Count Log
The external Click Count Log counts clicks from an application to an external site. You can implement this functionality using APEX_UTIL.COUNT_CLICK procedure.
Schema Reports offer summaries of schema tablespace utilization and database privileges by schema and a list of all database schemas available in the current workspace.
To view Schema Reports:
Navigate to the Workspace home page.
Click Manage Services on the Administration list.
The Manage Services page appears.
Under Workspace Schema Reports, click one of the following reports:
