Skip Headers
Oracle® Fusion Middleware User's Guide for Oracle Portal
11g Release 1 (11.1.1)

Part Number E10235-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4.5 Setting Page Defaults for the Pages in a Page Group

Page group properties include many options for setting default information for the page group's associated pages. For example, select a default style for all pages, identify a default navigation page (banner), or choose a template to apply to all associated pages. This section discusses these and other page group default setting options. It includes the following sub-sections:

For additional page group configuration tasks, see Chapter 5, "Preparing to Add Content":

4.5.1 Specifying the Doctype for Pages

It is recommended that every page should identify which version of HTML or XHTML it is using. This information can then be used by browsers to help display the page faster, because it knows what to expect from the page.

You identify the version of HTML or XHTML by including a doctype declaration in the code at the beginning of the page, such as:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

Some examples of doctypes include:

  • HTML 4.01 Compatibility mode

  • HTML 4.01 Transitional

  • HTML 4.01 Strict

  • XHTML 1.0 Transitional

  • XHTML 1.0 Strict

You can specify the doctype to use for all pages within your portal by specifying the global doctype setting. For information about how to do this, see the Oracle Fusion Middleware Administrator's Guide for Oracle Portal. If the portal administrator allows it, you can override this setting at the page group level, specifying a different doctype for all the pages within a specific page group.

Note:

Specifying the doctype does not affect the generated HTML, only the DOCTYPE declaration at the beginning of the HTML.

If you select a strict doctype (for example HTML Strict) some portlet refresh features will be affected due to HTML that is prohibited when using a Strict doctype. Specifically:

  • The page assembly timeout option is not shown when editing pages.

  • Portlet refresh does not use partial page refresh, instead the whole page is refreshed.

In addition, if you choose the middle image alignment option, your HTML will not validate as Strict. This is because an align attribute has to be used in this case, rather than a CSS attribute and the align attribute does not conform to Strict guidelines.

To specify the doctype for pages in a page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work in drop-down list, choose the relevant page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. If necessary, click the Main tab to bring it forward.

  6. In the Page DOCTYPE section, select Choose a specific DOCTYPE for this page group.

  7. Select the doctype that you want to use.

  8. Click OK.

4.5.2 Specifying Inheritance Rules for Newly Created Pages

When a page is created, it inherits default property settings from either its page group defaults, its parent page, or the Portal Template on which it is based. Inheritance is based on which option is selected when the page is created:

  • Inherit Access Settings from Template <template name>

    This option is available only if the page is based on a Portal Template and the template is set up to enable pages to use their own access settings.

    Select this option to use the same access control settings for a page as are specified for the template on which the page is based. If the access control settings for the template are changed, those changes affect all pages based on the template that use the template's access settings (Figure 4-2).

    The page's Access Properties and Grant Access sections do not display when this option is selected.

    Figure 4-2 Newly Created Pages Inheriting Access Settings from a Portal Template

    Inheriting from a Portal Template
    Description of "Figure 4-2 Newly Created Pages Inheriting Access Settings from a Portal Template"

  • Copy Parent Page Properties When Creating Page

    Select this option to use parent page property settings as default settings for any newly created sub-pages. When a new page inherits its default property settings from its parent page, each successive generation inherits its default property settings from the previous generation (Figure 4-3).

    Figure 4-3 Newly-Created Pages Inheriting Properties From the Parent Page

    Inheriting properties from the parent page
    Description of "Figure 4-3 Newly-Created Pages Inheriting Properties From the Parent Page"

  • Use Default Properties When Creating Page

    Select this option to use the page group's default settings for all newly created pages. All newly created pages use the page group's settings for their own defaults, regardless of whether their parent page's property settings are different (Figure 4-4).

    Figure 4-4 Newly-Created Pages Inheriting Properties From the Page Group

    Inheriting privileges from the parent page group
    Description of "Figure 4-4 Newly-Created Pages Inheriting Properties From the Page Group"

The following properties are inherited from the parent as page defaults. Note that changes to these parent page properties do not continue to cascade to sub-pages after the sub-pages have been created, with the exception of access rules that are set to inherit:

  • Page type

  • Page caching option

  • Portal Template

  • HTML page skin

  • Style

  • Portlet settings

  • Item versioning level

  • Contact e-mail

  • Category

  • Keywords

  • Approval process

  • Parameters

  • Navigation page used for the banner

    This is defaulted to the first navigation page portlet on the parent page. If the parent page contains other navigation page portlets, those will also be inherited by new sub-pages.

  • Access settings

    This includes the settings for Display Page To Public Users and Enable Item Level Security as well as the access control list (that is, the list of users and groups and their associated privileges).

    Any page with the option setting Display Page To Public Users becomes a crawlable data source for Oracle Ultra Search. See also Oracle Fusion Middleware Administrator's Guide for Oracle Portal for information on configuring portal search features.

Note:

When a new page is created, the settings for the property Default WebDAV Types is always reset to Inherit from Parent Page. This allows any changes to a parent page to automatically cascade down to the child pages.

When property settings are copied from the parent page, all sub-pages are set to Use same portal template as parent page. If the parent page uses a Portal Template for items, the sub-page uses the same Portal Template for items. As long as the sub-page is set to Use same portal template as parent page, subsequent changes to the parent's Portal Template for items setting will cascade to the sub-page.

To specify inheritance rules for newly created pages:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work in drop-down list, choose the relevant page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. Click the Configure tab to bring it forward.

  6. Click the Edit link under the Page Defaults section.

  7. Under the Page Defaults heading, select an inheritance rule for the page group.

    Choose from:

    • Inherit Access Settings from Template <template_name>—This option is available when the page is based on a Portal Template for pages, and the template allows access rules other than its own. Select this option to use the same access rules as are specified for the Portal Template for pages. When this option is selected, changes to the template's access rules affect this page.

    • Copy Parent Page Properties When Creating Page—Select this option to use parent page property settings as default settings for any newly created child pages. The relevant properties are those listed at the beginning of this section.

    • Use Default Properties When Creating Page—Select this option to use the page group's default settings for all newly created pages. All newly created child pages use the page group's settings for their own defaults, regardless of whether their parent page's property settings are different.

  8. Click OK.

For information about creating pages, see Chapter 6, "Creating Pages".

4.5.3 Choosing a Default Style for a Page Group

When you create a page, you can choose a style to define the colors and fonts to be used in the page. To simplify this choice, and to identify a preferred style for the pages in your page group, you can identify a default style. You can also choose <None> as the default style.

If inheritance rules specify inheritance from the page group (see Section 4.5.2), the default style you select for the page group becomes the default style when users create a new page. That is, it is the default selection displayed in the Style drop-down list during page creation. If, when creating a page, the user does not explicitly choose a style, the default style is used.

When a selected style is deleted, all pages and item regions that used it revert to the page group default style. If the page group default style is <None>, all pages and regions revert to the system default style.

Note:

A hierarchical structure governs when a default style is put to use. For a summary of how default styles are applied, see Section 11.8, "Applying a Style".

To choose a default style for a page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work in drop-down list, select the page group for which to specify a default style.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. Click the Configure tab to bring it forward.

  6. In the Page Defaults section, click the Edit link.

  7. From the Default Style list, choose a default style for the page group.

    This list includes all the public styles in this page group and the Shared Objects page group.

  8. Click OK to return to the Configure tab.

  9. Click Close.

The default style is ignored if the option to inherit page properties for new pages from the parent page is enabled for the page group. This is because the new page will automatically inherit its style from its parent page. For more information, see Section 4.5.2, "Specifying Inheritance Rules for Newly Created Pages".

For information about creating styles, see Chapter 11, "Working with Colors and Fonts".

4.5.4 Choosing a Default Navigation Page for a Page Group

Navigation pages are special purpose pages within a page group that are added as page portlets to other pages or to Portal Templates. Typically, they provide standard user interface navigation effects such as navigation bars and banners. They often contain one or more navigation item types that provide navigation within the portal.

When you create a page, you can choose a navigation page to display as a banner in a region at the top of the page. To simplify this choice, and to identify a preferred navigation page for the pages in your page group, you can identify a default navigation page. You can also choose <None> as the default navigation page. If inheritance rules specify inheritance from the page group (see Section 4.5.2), your selection becomes the default selection when a user creates a new page. That is, it is the default selection displayed in the Navigation Page For Banner drop-down list during page creation. If, when creating a page, the user does not explicitly choose a navigation page, the default navigation page is used.

Because the default navigation page is added to a region that occupies the full width of the page, make sure that the navigation page you choose here is suited to a wide, horizontally oriented region.

To choose a default navigation page for a page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work in drop-down list, select the page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. Click the Configure tab to bring it forward.

  6. In the Page Defaults section, click the Edit link.

  7. From the Default Navigation Page list, select a default navigation page for the page group.

    This list includes all the navigation pages that have been published as portlets in this page group and the Shared Objects page group.

  8. Click OK to return to the Configure tab.

  9. Click Close to return to the Navigator.

The default navigation page is ignored if the option to inherit parent page properties is enabled for the page group. This is because the new page will automatically inherit its navigation page setting from its parent page. For more information, see Section 4.5.2, "Specifying Inheritance Rules for Newly Created Pages".

For information about creating navigation pages, see Chapter 13, "Designing Your Portal's Navigation".

4.5.5 Choosing a Default Template or Page Skin for a Page Group

When you create a page, you can choose a Portal Template or an HTML page skin to define the layout, look, and feel of the page. To simplify this choice, and to identify a preferred template option for the pages in your page group, you can choose a default Portal Template or page skin for a page group. You can also choose to opt out of identifying a default by selecting Do not use a template. The option you select for the page group default becomes the initial selection when users create a page.

Note:

The default template you select here does not apply to navigation pages. You must specifically select a template for a navigation page.

For a description of the types of templates available in Oracle Portal, see Section 12.1, "Understanding Templates in Oracle Portal".

To choose a default template option for a page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work In drop-down list, select the page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. Click the Configure tab to bring it forward.

  6. In the Page Defaults section, click the Edit link.

  7. Under the Default Template section, choose a default template option for the page group:

    • Do not use a template—Select this option to opt out of specifying a default template or page skin for the page group.

    • Use HTML Page Skin—Select this option to specify the HTML page skin to use as the page group default. Then choose a page skin from the list of available page skins. Click the Preview button to see how the page skin will display.

      The list includes HTML page skins owned by the currently selected page group as well as those owned by the Shared Objects page group.

    • Use Portal Template—Select this option to specify the portal template to use as the page group default. Then choose a template from the list of available templates.

      This list includes the public templates in this page group and in the Shared Objects page group. For a template to be public, its display setting Make available for use in this page group must be selected.

    Note:

    When a page group and the Shared Objects page group both contain a template of the same name, the page group name is added to the template name in pick lists. For example: <template_name> (page_group_name). This assists in distinguishing between templates on pick lists.

  8. Click OK to return to the Configure tab.

  9. Click Close.

The default template selection is ignored if the option to inherit parent page properties is enabled for the page group. See Section 4.5.2, "Specifying Inheritance Rules for Newly Created Pages".

For information about creating templates and page skins, see Chapter 12, "Providing a Standard Look and Feel".

4.5.6 Specifying Tab Navigation Behavior for a Page Group

Page group properties include a control for specifying tab navigation behavior, that is, tab persistence. Tab persistence allows for the return of users to the last tab viewed. The information is preserved for each user for the entire user session (from logon to logoff).

For example, imagine that you have two tabs on the same page at the same level: Tab1 and Tab2. Tab2 has two sub-tabs: SubtabA and SubtabB. A user navigates to Tab2:SubtabB, navigates to Tab1, then returns to Tab2.

  • With tab persistence turned on, when the user returns to Tab2, SubtabB will remain selected and Tab2:SubtabB will display in the page URL.

  • With tab persistence turned off (the default), when the user clicks Tab2, the first sub-tab, SubtabA, will be selected and Tab2 will display in the page URL.

The same principle applies when there are no sub-tabs. For example, when users navigate to Tab2, leave the page, then return, they return to Tab2 when tab persistence is on and they return to Tab1 when tab persistence is off.

There is a performance advantage to leaving tab persistence off. For most page groups, the default is off. The Portal Design Time Pages page group is an exception. Its default is on. This page group includes the Portal Builder.

To specify tab persistence rules for the page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work In drop-down list, select the page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. If necessary, click the Main tab to bring it forward.

  6. Under the Page Properties section, go to the check box Allow Tab Persistence for Pages:

    • Select this check box to preserve tab navigation information during a user session (tab persistence).

    • Clear this check box to turn tab persistence off.

  7. Click OK.

4.5.7 Defining URL Rewrite Rules for a Page Group

Page group URL rewrite rules work with the rewrite rules set up in the Oracle HTTP Server to ensure that users are consistently exposed to the same URL for a particular object, regardless of how they access that object.

Use page group rewrite rules to specify rewrite rules for the URLs within the page group. This setting works in conjunction with any rewrite rules you may have created on the Oracle HTTP Server. The Oracle HTTP Server rewrite rules control the appearance of the URL that is used to initially access your portal. The rewrite rules you create on this page control the appearance of the URLs that are used to subsequently navigate within your portal. This is useful for ensuring a consistent appearance to your portal's URLs as users navigate into, then within, the portal.

Page group rewrite rules must be created in conjunction with the rewrite rules you set up on the Oracle HTTP Server. That is, they must replace the same elements in the URL but in reverse. For example, if your middle-tier rewrite rule replaces /mycompany/ with /host/portal/dad/, the rewrite rule you create for your page group must do the reverse: It must replace /host/portal/dad/ with /mycompany/.

This section provides some basic information about setting up rewrite rules on the Oracle HTTP Server and in page group properties. For more information about setting up rewrite rules in the Oracle HTTP Server, refer to the mod_rewrite section of the Oracle Fusion Middleware Administrator's Guide for Oracle HTTP Server.

To set up a rewrite rule on the Oracle HTTP Server, go to the following file:

ORACLE_INSTANCE/config/OHS/ohs1/httpd.conf

Add the rule to the end of the file. For example, add:

RewriteRule ^/mycompany/(.*)$/portal/page/mycompany_dad/mycompany_pgrp/$1 [PT]

The rewrite rule in the Oracle HTTP Server may be set up so that when a user types the following URL in the browser, or includes it as a link in another document:

http://mymachine.mycompany.com:5000/mycompany/page1

It is translated to the actual URL for the page:

http://mymachine.mycompany.com:5000/portal/page/mycompany_dad/mycompany_pgrp/page1

To keep all of your portal's URLs consistent with those governed by the middle-tier rewrite rule, you would go to the page group's rewrite rule option and enter the search pattern:

/portal/page/mycompany_dad/mycompany_pgrp/

And enter the replace pattern:

/mycompany/

The resulting URL would appear in the browser's address bar just as it would for those URLs handled by the middle-tier rewrite rule, that is:

http://mymachine.mycompany.com:5000/mycompany/page1

To specify a URL rewrite rule for the page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work In drop-down list, select the page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. Click the Configure tab to bring it forward.

  6. Click the Edit link in the URL Rewrite Rules section.

  7. In the Search pattern field, enter the portion of the page group URL you will replace.

    For example:

    /portal/page/mycompany_dad/mycompany_pgrp/
    
  8. In the Replace pattern field, enter the character or characters that will replace the Search pattern.

    For example:

    /mycompany/
    
  9. Click OK to save your changes and return to the Configure tab.

  10. Click Close.

4.5.8 Enabling and Disabling Parameters and Events for a Page Group

A parameter is a value that is passed between pages and portlets. There are two types of parameters:

  • Page parameters

    • Pages can accept and store parameter values.

  • Portlet parameters

    Portlets can:

    • Read page parameter values

    • Update page parameters in response to an event

    • Read parameter values from another portlet (using an application programming interface, API)

An event is a user action defined by a portlet developer. User actions include clicking a link, a button, or another control on a Web page. A page designer can specify that an event forces the reloading of the current page or the loading of another page, and optionally passes parameters to the newly loaded page. A portlet's events are specified in the provider.xml file.

For more information about parameters and events, see Chapter 22, " Using Parameters and Events".

When a page group is created, parameters and events are enabled by default. When they are enabled, page designers can add parameters to pages in a selected page group and use the portlet parameters and events that are associated with the portlets placed on pages in the page group. When they are disabled, the use of parameters and events is not allowed, and none of the tabs and fields associated with them display in the user interface.

To enable or disable parameters and events in a page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work In drop-down list, select the page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. Click the Configure tab to bring it forward.

  6. In the Parameters and Events section, click the Edit link.

  7. On the resulting page:

    • Select Enable Parameters and Events to enable the use of parameters and events in the current page group.

    • Clear Enable Parameters and Events to disable the use of parameters and events in the current page group.

  8. Click OK to return to the Configure tab.

  9. Click Close.

4.5.9 Enabling JavaServer Page Access to a Page Group

To make JavaServer Pages (JSPs) more useful within your portal, you may wish to add portlets to them. Before you can add portlets to JSPs, you must first enable JSP access to the JSP's page group. Additionally, to use Oracle Portal portlets, you must publish the portlets externally. An externally published portlet is a portlet that has been explicitly made available for users to add to their JSPs. Finally, you reference the portlet by the name you gave it when you published it externally. Reference externally published portlets using JSP tags, such as <portal:showPortlet>.

This section provides information on enabling JSP access to a page group and publishing portlets externally. It contains the following subsections:

More on the Oracle Technology Network

For information about adding portlets to JSPs, including using Oracle JSP tags, see "Integrating Java Server Pages with Oracle Portal," on the Oracle Technology Network:

http://www.oracle.com/technology/products/ias/portal/pdf/pd_jsps_10g.pdf

4.5.9.1 Enabling JSP Access

To enable JavaServer Page access to a page group:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work In drop-down list, select the page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Configure link.

  5. Click the Configure tab to bring it forward.

  6. In the JSP Access section, click the Edit link.

  7. Select the Allow External Access check box.

    This is required for both internal and external JSPs.

  8. In the Access Key field, enter a text string to provide security between the page group and the JSPs.

    The access key can contain up to 200 alphanumeric characters (A to Z, a to z, 0 to 9). Do not use spaces, the underscore character (_), or other special characters.

    An Access Key is required for both internal and external JSPs.

    For your external JSPs to access the page group, you will need to specify this key in the configuration file you create to support your external JSPs. When a JSP is executed, if it includes any externally published portlets, the access key in its configuration file is compared against the access key of the page group. If the keys match, the portlets are displayed.

  9. Click OK to return to the Configure tab.

  10. Click Close.

4.5.9.2 Publishing a Portlet Externally

Before you can publish a portlet externally, you must first enable JSP access in the page group. Follow the preceding set of steps before you publish a portlet externally.

To publish a portlet externally:

  1. Log in to Oracle Portal.

  2. Click the Build tab to bring it forward.

  3. From the Page Groups portlet Work In drop-down list, select the page group.

    By default, the Page Groups portlet is located on the Build tab of the Portal Builder page.

  4. Click the Browse link next to the selected page group.

    This opens the Portal Navigator.

  5. Click the Externally Published Portlets link.

    If you do not see this link, you may not have enabled the access of JSPs to the page group. See Section 4.5.9.1, "Enabling JSP Access" for more information.

  6. Click the Externally Published Portlet link next to Create New.

  7. On the resulting page, enter a name for the portlet in the Portlet Name field.

    This name is used within JSPs to identify which portlet to display. The name must be unique within the page group and can contain up to 200 characters. The name must begin with an alphabetic character (A to Z, a to z), and can contain only alphanumeric characters (A to Z, a to z, 0 to 9) and the underscore (_) character. Do not use spaces or other special characters.

  8. Click the Select Portlet icon, and select the portlet you will use in a JSP.

    Clicking the Select Portlet icon takes you into the Portlet Repository. You can drill down through the repository hierarchy to locate the portlet you will use. Once you click the listed portlet, the task is complete. The portlet is published for use with JSPs, and you are returned to the Portal Navigator.

  9. Click OK.

4.5.9.3 Additional JSP Information

You can create two types of JSPs for use with Oracle Portal:

  • Internal JSPs are created within Oracle Portal. Internal JSPs are quick and easy to set up and manage. You create them using the standard page wizards. Internal JSPs are automatically stored in the Oracle Portal system, and are managed and secured by Oracle Portal. For more information, see Section 6.6, "Creating a JavaServer Page (JSP)".

  • External JSPs are created outside Oracle Portal using a text editor or other external tool. You store external JSPs outside of Oracle Portal. Oracle Portal does not provide any file management or security for external JSPs. There are additional requirements for having Oracle Portal accept and display external JSPs in a page group. You must create a configuration file and install it in the Oracle Portal environment, and modify the server to allow the external JSPs to log in to Oracle Portal. For more information, see the Oracle Fusion Middleware Administrator's Guide for Oracle Portal.

In general, internal JSPs are much simpler to create and use. External JSPs offer more flexibility, are easier to modify, and usually run faster than internal JSPs.

Whether you are using external or internal JSPs, a JSP must be associated with a page group. That page group must be enabled to allow JSP access.