Choosing a Default Template or Page Skin for a Page Group

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 4-22 Oracle Fusion Middleware Users Guide for Oracle Portal 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:5000mycompanypage1 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: portalpagemycompany_dadmycompany_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 portlets events are specified in the provider.xml file.