Setting the expiry time for invalidation-based caching

Related topics

With invalidation-based caching, a cache entry is refreshed when the portal or a provider sends a message informing Web Cache that the object has changed (for example, when an item is edited). However you can also set an expiry time for cache entries. A cache entry that reaches this time limit is refreshed, even if Web Cache has not received an invalidation message for it.

To set the expiry time for invalidation-based cache entries, you must be the portal administrator.

To set the expiry time for invalidation-based cache entries:

1. In the Services portlet, click Global Settings.

   Note: By default, the Services portlet is on the Administer tab of the Builder page.

2. Click the Cache tab.

3. In the Maximum Expiry Time field, enter the maximum amount of time (in minutes) a cache entry should remain in the cache before being refreshed.

4. Click OK.

Notes

• For more information about Oracle9iAS Web Cache, refer to the Web Cache documentation on Oracle Technology Network.

Related topics

How does caching work in Oracle9iAS Portal?
Clearing the cache

Back to top