|
Oracle® HTML DB
Release 2.0 |
|
 Previous |
 Next |
Application attributes apply to an entire application. Once you create an application the next logical step is to review and possibly update application attributes.
Topics:
Standard Application Attributes display on the Edit Application Attributes page. You use these attributes to control the application name and availability as well as defined substitution strings. Additionally, the Edit Application Attributes page displays defined build options, the associated theme, template defaults, and component defaults. Required values are marked with a red asterisk (*).
Topics:
To edit application attributes:
Navigate to the Workspace home page and click the Application Builder icon.
Select an application.
Click Edit Attributes.
The Application Attributes page appears.
Click Edit Standard Attributes.
The Edit Application Attributes page appears.
The following sections describe the attributes available on the Edit Application Attributes page.
Topics:
Use Name to define basic characteristics of your application, including the application name, an optional alphanumeric alias, a version number, and the application owner. Table 5-1 describes all Application Definition attributes.
Table 5-1 Application Definition Attributes
| Attribute | Description |
|---|---|
|
Provides a short descriptive name for the application to distinguish it from other applications in the Oracle HTML DB development environment. |
|
|
Assigns an alternate alphanumeric application identifier. You can use this identifier in place of the application ID.For example, suppose you create an alias of
|
|
|
Includes the application's version number on a page. You can also automatically tie the version to the date of last modification using the following format masks:
If your application version uses YYYY.MM.DD then Oracle HTML DB replaces this format mask with the date of last modification of any application attribute. |
|
|
Determines the virtual path the Web server uses to point to the images directory distributed with Oracle HTML DB. During installation, the virtual path is configured as When embedding an image in static text (for example, in page or region headers or footers) you can reference an image using the substitution string <img src="#IMAGE_PREFIX#go.gif">
See Also: "IMAGE_PREFIX", "Uploading Images", and "Referencing Images" |
|
|
Use this field to specify a proxy server. For example, Application Builder may require a proxy server when using a region source type of URL. The URL region source embeds the results of the URL (that is, the page returned by navigating to the URL) as the region source. If you use a firewall and the target of a URL is outside the firewall relative to Oracle HTML DB, you may need to specify a proxy server. You can reference values entered into this field from PL/SQL using the PL/SQL package variable |
|
|
Determines whether or not user activity is recorded in the Oracle HTML DB activity log. When set to Yes, every page view will be logged, allowing a Workspace administrator to monitor user activity for each application. Disabling logging may be advisable for high volume applications. |
|
|
Specifies the schema that all SQL and PL/SQL in the application will be parsed as. You may use |
|
|
Select whether or not only exact substitutions will be supported. For optimal run-time performance, it is recommended you use exact substitutions. Exact substitutions use the following sytnax: &ITEM. Non-exact substitutions use the following sytnax: &ITEM |
Use Availability attributes to manage your application by defining an application status and build status. For example, if you select the status Restricted Access, you can specify which users have access and can run the application. Table 5-2 describes these attributes.
Table 5-2 Application Availability Attributes
| Attribute | Description |
|---|---|
|
Specifies whether or not the application is available or unavailable for use. Options include:
|
|
|
Identifies the build status of the current application:
See Also: "Changing Application Build Status" for information about managing application build status as an Oracle HTML DB administrator |
|
|
If you set Status to Unavailable, Unavailable (Status Shown with PL/SQL), or Unavailable (Redirect to URL), the text you enter in this attribute displays. If you set Status to Available, the text you enter in this attribute does not display. |
|
|
Restrict to comma separated user list (Status must equal Restricted Access) |
Use this attribute in conjunction with the Status Restricted Access. If you set Status to Restricted Access, only the users listed in this attribute can run the application. To use this attribute:
|
You can use the Global Notifications attribute to communicate system status to application users. For example, you can use this attribute to notify users of scheduled downtime, or communicate other messages regarding application availability. If the page templates used in your application contain the #GLOBAL_NOTIFICATION# substitution string, the text entered here will display in that string's place.
To create a global notification:
Include the #GLOBAL_NOTIFICATION# substitution string in your page template.
Navigate to the Edit Application Attributes page and enter a message in the Global Notifications attribute.
Click Apply Changes.
Use these fields to define static substitution strings for your application. You can use static substitution string for phrases or labels that occur in many places within an application. Defining static substitution strings centrally enables you to change text strings in multiple places in your application by making a single change to the Substitution Value defined on this page.
Use these attributes to identify an image to be used as the logo for this application. In Image, identify the image name. If you identify an image in the Image attribute and include the #LOGO# substitution string in your page template, the HTML DB engine generates an image tag. Use Logo Image Attributes to identify specific image attributes for the logo image. For example:
width="100" height="20" alt="Company Logo"
Displays existing build options. Most application attributes have a build option attribute. Do not specify a build option unless you plan to exclude that object from specific installations. Build Options have two possible values: INCLUDE and EXCLUDE. If you specify an attribute to be included, then the HTML DB engine considers it at run time. However, if you specify an attribute to be excluded, then the HTML DB engine treats it as if it does not exist.
Displays the current theme applied to the application. Themes are collections of templates that can be used to define the layout and style of an entire application. Each theme provides a complete set of templates that accommodate every user interface pattern that may be needed in an application.
Template Defaults list the default templates for this application. To specify a new template at the application level, you can either:
Select a new theme
Select a new default page template on the Define Theme page
You can also override this default by making a selection from the Page Template list on the Page Attributes page.
Table 5-3 describes template defaults for the current application.
Table 5-3 Application Template Defaults Attributes
| Attribute | Description |
|---|---|
|
Default Page Template |
Indicates the default page template to display pages. You can override this selection by making a selection from the Page Template list on the Page Attributes page. See Also: "Editing Page Attributes" |
|
Identifies the template to be used when the HTML DB engine is in printer friendly mode. When calling the HTML DB engine to render a page, you have the option to specify whether or not the page should be displayed using the Print Mode Page Template specified. If you specify Yes, then the page displays using a printer friendly template. The HTML DB engine displays all text within HTML Form Fields as text. The printer friendly template does not need to have the See Also: "Optimizing a Page for Printing" |
|
|
Optional. Specifies a page template to use for errors that display on a separate page, as opposed to those that display inline. |
Component Defaults identify default templates used when running wizards. You can override these settings on the attributes page for each control or component. Table 5-4 describes component defaults for the current application.
Table 5-4 Component Defaults
| Attribute | Description |
|---|---|
|
Calendar |
Default calendar template used when creating a new calendar. |
|
Label |
Default label template used when you create new page items. |
|
Report |
Default report template used when you create new report. |
|
List |
Default template used when you create a list. |
|
Breadcrumb |
Default template used when you create a breadcrumb. |
|
Button |
Default template to be used when you create new buttons that are template controlled. |
|
Region |
Default region template used when you create a new region. |
|
Chart Region |
Default region template used when you create a chart. |
|
Form Region |
Default region template used when you create a form. |
|
Report Region |
Default region template used when you create a report. |
|
Tabular Form Region |
Default region template used when you create a tabular form. |
|
Wizard Region |
Default region template used when you create a new wizard component. |
|
Breadcrumb Region |
Default region template used when you create a new breadcrumb. |
|
List Region |
Default region template used when you create a new list. |
You can provide security for your application by configuring attributes on the Edit Security Attributes page. The Security Attributes you choose apply to all pages within an application.
Topics:
To access the Edit Security Attributes page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Click Edit Attributes.
The Application Attributes page appears.
Click Edit Security Attributes.
The Edit Security Attributes page appears.
The following sections describe the attributes available on the Edit Security Attributes page.
Topics:
Authentication is the process of establishing users' identities before they can access an application. Although you define multiple authentication schemes for your application, only one scheme can be current at a time. Table 5-5 describes the attributes available under Authentication.
Table 5-5 Authentication Attributes
| Attribute | Descriptions |
|---|---|
|
Specifies an URL or procedure that should be run when you run the application. For example, Home Link could contain the relative URL used to locate the application home page. For example, You can also use this attribute to name a procedure. For example, you could create a procedure such as Note: Do not use the Home Link attribute to determine the page that displays after authentication. The page that displays after authentication is determined by other components within the application's authentication scheme. See Also: "HOME_LINK" and |
|
|
Replaces the substitution strings &LOGIN_URL. in HTML or #LOGIN_URL# in templates. See Also: "LOGIN_URL" and "Creating an Authentication Scheme" |
|
|
Identifies the Oracle schema (or user) used to connect to the database through the database access descriptor (DAD). The default value is Once a user has been identified, the HTML DB engine keeps track of each user by setting the value of the built-in substitution string
If the current application user ( For example, you can show a login button if the user is the public user and a logout link if the user is not a public user. Reference this value using See Also: "HOME_LINK" and "Understanding Conditional Rendering and Processing" |
|
|
Click this button to define a new authentication scheme. See Also: "Understanding How Authentication Works" and "Creating an Authentication Scheme" |
Authorization controls user access to specific controls or components based on user privileges. You can specify an authorization scheme for your application, by making a selection from the Authorization Scheme list. You can assign only one authorization to an entire application. However, you can assign an authorization scheme to individual pages, page controls (such as a region, a button, or an item), or a shared component (such as a menu, a list, or a tab).
To create a new authorization scheme, click Define Authorization Schemes.
An authorization scheme is a binary operation that either succeeds (equals true) or fails (equals false). If it succeeds, then the component or control can be viewed. If it fails, then the component or control cannot be viewed or processed. When you attach an authorization scheme to a page and it fails, an error message displays instead of the page. However, when you attach an authorization scheme to a page control (for example, a region, a button, or an item) and it fails, no error page displays. Instead, the control either does not display or is not processed or executed.
Use Parsing Schema to specify the database scheme for the current application. You can only select schemas that are accessible to the current workspace. Once defined, all SQL and PL/SQL commands issued by the application will be performed with the rights and privileges of the defined database schema.
Enabling Session State Protection can prevent hackers from tampering with URLs within your application. URL tampering can adversely affect program logic, session state contents, and information privacy.
To enable or disable Session State Protection for your application, make a selection from the Session State Protection list. Setting Session State Protection to Enabled turns on session state protection controls defined at the page and item level.
To configure Session State Protection, click Manage Session State Protection.
A Virtual Private Database (VPD) provides an application programming interface (API) that enables developers to assign security policies to database tables and views. Using PL/SQL, developers can create security policies with stored procedures, and bind the procedures to a table or view by means of a call to an RDBMS package. Such policies are based on the content of application data stored within the database, or are based on context variables provided by the Oracle database. In this way, VPD permits access security mechanisms to be removed from applications and centralized.
The PL/SQL you enter in this field is executed immediately after the user is authenticated. V('USER') is accessible from this function. Session state for the current call is not yet initialized when this call is made. If your application does not need to employ VPD to support multiple customers in the same database, leave this attribute null.
In Oracle HTML DB you can develop applications that can run concurrently in different languages. A single Oracle HTML DB application can be translated to support different languages. Use the attributes on the Edit Globalization Attributes page to specify globalization options such as the primary application language.
Topics:
To access the Edit Globalization Attributes page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Application Builder appears.
Click Edit Attributes.
The Application Attributes page appears.
Click Edit Globalization Attributes.
The Edit Globalization Attributes page appears.
The following sections describe the attributes available on the Edit Globalization Attributes page.
Identifies the language in which an application is developed. This language is the base language from which all translations are made. For example, suppose application 100 was authored in English, translated into French, and published as application 101. English would be the Application Primary Language.
All modifications to the application should be made to the primary language specified here.
Specifies how Oracle HTML DB determines or derives the application language. The application primary language can be static, derived from the Web browser language, or determined from a user preference or item. The database language setting also determines how the date is displayed and how certain information is sorted.
This option enables you to disable browser derived language support. You also have the option of having the application language derived from an application preference.
Automatic CSV Encoding controls the encoding of all CSV report output in an application. The default value for Automatic CSV Encoding is No. If Automatic CSV Encoding is set to Yes, CSV report output will be properly converted to a character set compatible with localized desktop applications. The character set for the CSV encoding is determined by the Application Language Derived From setting.
The encoding of pages in Oracle HTML DB is determined by the character set of the Database Access Descriptor (DAD) used to access Oracle HTML DB. For example, if the character set of the Database Access Descriptor is AL32UTF8, all pages in all applications from the instance of Oracle HTML DB will be encoded in UTF-8.
By default, the CSV output from report regions is encoded in the same character set as the Database Access Descriptor. However, some desktop spreadsheet applications require that the data is encoded in the client desktop operating system character set. In the case of multibyte data, the CSV output from report regions will often appear corrupted when opened by a desktop spreadsheet application. This is because the CSV output is encoded differently that what is required by the desktop application. Enabling Automatic CSV Encoding resolves this issue.
For example, if the user's language preference for an Oracle HTML DB application is de, the CSV data will be encoded in Western European Windows 1252, regardless of the Database Access Descriptor character set setting. If the user's language preference is zh-cn, the CSV data will be encoded in Chinese GBK.