To change how a page is cached:
Go to the page where you will change caching options.
For information on locating a page, see Section 8.1, "Locating Pages in Oracle Portal".
Switch to Edit mode.
Click the Properties link next to Page in the page toolbar.
Be sure to click the link for the page rather than the page group.
Go to the Page Caching section of the Main tab, and select a page caching option.
See Section 21.1.2, "Page Caching Options" for a description of each caching option.
Click OK to save your changes.
Table 21-1 lists and describes the page caching options (Edit Page: Main tab):
Cache Page Definition And Content at User Level For [ ] Minutes
Cache Page Definition Only at System Level
Cache Page Definition And Content at System Level For [ ] Minutes
Caches the page definition for each user, in both Oracle Web Cache and the Portal Cache. The page definition includes:
Choose this option for pages with dynamic portlet content and where the page definition is user specific. For example, user specific page definitions might contain:
Caches the page definition (as described in the previous option), and the assembled page's content, including all portlet content, for a specified period of time, for each user. This is called user-level expiry-based caching.
Choose this option for pages with portlets that do not change within the specified time period and where the page content (either the page definition or portlet content) is user specific.
Caches the page definition once for all users. The page definition is the same for all users and includes:
Choose this option for pages with dynamic portlet content, where the page definition is the same for all users.
This option greatly reduces storage requirements and improves performance. It eliminates regeneration of the page definition on every request, by any user. The page definition is generated the first time any user accesses the page. The portlet content is retrieved and the page is assembled on each request and this allows the page to display dynamic portlet content.
This option can be used when:
Do not choose this option when:
If page performance is critical, you might use this option if the page definition contains certain user specific items:
- Items with item level security,
- Navigation items (Page Link, Page Path, Login/Logout),
- Portal Smart Link items (Edit),
- Portal Smart Text (Current User).
If you do this, these items are displayed the same to all users, regardless of their access privileges. Whilst this is not ideal visually, users can still perform only the actions for which they have the appropriate access privileges. For example, if your page contains an Edit link, every user viewing the page sees the Edit link even if they do not have Edit privileges. All security checks are deferred until a user clicks on the link.
Note: This option is available for Standard, Mobile, and JSP pages only.
Caches the page definition (as described in the previous option), and the assembled page's content, including all portlet content, for a specified period of time, for all users. This is called system-level expiry-based caching.
Choose this option for pages with portlets that do not change within the specified time period and where the page content (both the page definition and portlet content) is the same for all users.
Do not choose this option when:
Note that the use of this option will adversely impact portal performance. Do not use this option except where absolutely necessary. Do not use this option on frequently accessed pages. Keep the number of pages that require this option to a minimum.
You may want to disable page caching in the following circumstances:
You can manually clear the cache entries associated with a page. For example, this might be useful if you revoke a user's privileges on a page and you want to make sure that your privilege level changes are applied immediately. If you do not clear the cache, the user will still be able to access the page if it is in the cache.
To clear the cache for a page: