Choosing a Default Navigation Page for a Page Group

4-20 Oracle Fusion Middleware Users Guide for Oracle Portal 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.

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.

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. Working with Page Groups 4-21

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 portals 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 hostportaldad, the rewrite rule you create for your page group must do the reverse: It must replace hostportaldad 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 Administrators Guide for Oracle HTTP Server. To set up a rewrite rule on the Oracle HTTP Server, go to the following file: ORACLE_INSTANCEconfigOHSohs1httpd.conf Add the rule to the end of the file. For example, add: RewriteRule mycompany.portalpagemycompany_dadmycompany_pgrp1 [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:5000mycompanypage1 It is translated to the actual URL for the page: http:mymachine.mycompany.com:5000portalpagemycompany_dadmycompany_pgrppage1 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: portalpagemycompany_dadmycompany_pgrp And enter the replace pattern: mycompany