Show TOC

Activating and Clearing the Portal Runtime CacheLocate this document in the navigation structure

Use

You can optimize portal performance by adding selected portal pages and iViews to the portal runtime cache. The caching mechanism uses both memory (RAM) and the portal database cache. At runtime, you can then monitor the portal objects in the portal runtime cache to detect which objects need fine-tuning for improved response time and performance. You may need to clear the cache to resolve inconsistencies between the cached objects in memory and the cached objects in the database.

Note
  • You should activate the portal runtime cache only for static content

  • The portal runtime cache is effective only at runtime

Procedure

Activating the Portal Runtime Cache

You can optimize the performance of portal pages and iViews by modifying cache settings. The portal runtime cache causes pages and iViews to be called from the memory caches rather than from the database, which is considerably quicker. The validity period of the content of portal pages and iViews varies and can sometimes be valid only for certain users. Therefore you need to maintain cache settings for each portal page and iView.

  1. In the Portal Catalog, in the context menu of the page or iView for which you want to activate caching, choose Start of the navigation path Open Next navigation step Properties End of the navigation path. The Properties editor appears.

  2. Choose Modify Properties to activate the editor.

  3. Define values for the following properties:

    Property

    Value

    Cache Level

    Specifies how the cache is used. Possible values:

    • None : No cache is used. The content of the page or iView is loaded again with each access.

    • Shared : The content of the page or iView is cached for all users. Choose Shared if the content of the page or iView is valid for all users and changes rarely or never (for example, graphics and logos).

    • Session : The content of the page or iView is cached on a user-specific basis for the user's entire browser session or until the lifetime (specified in Cache Validity Period ) expires. Choose Session to display different user-specific content for each session.

    • User : The content of the page or iView is cached on a user-specific basis. Choose User if the content of the page or iView is user-specific and does not change for the duration of all sessions of the user (for example, a welcome message).

    Cache Validity Period

    Lifetime of items in the cache (in milliseconds)

    Default value: -1 (no active caching)

    Example: Enter 360000 for a lifetime of one hour.

  4. Save your changes.

Note

Caching does not take place when you are working in the administration environment. In this case, the content is loaded again each time you access the page or iView.

Clearing the Portal Runtime Cache

Inconsistencies can occur between the cached objects in memory and the cached objects in the database. You can detect this condition only by viewing the contents of the cache. You resolve these inconsistencies by clearing the portal runtime cache in the database. This operation clears the cached objects both in memory and in the database.

  1. In the browser, perform one of the following:

    • Enter the following URL to clear the cached content in the database: http://<portalhostserver>:port/irj/servlet/prt/portal/prtroot/com.sap.portal.prt.cache.PRTRegionDBClear .

    • Enter the following URL to clear the cache in the specific cluster node to which you are currently connected: http://<portalhostserver>:port/irj/servlet/prt/portal/prtroot/com.sap.portal.prt.cache.PRTRegionMemoryClear .

  2. At the prompt, log on to the portal. The portal runtime cache is automatically cleared. A message appears showing information about the cached content that was cleared.