Show TOC

Function documentationCaching the Top-Level Navigation iView Locate this document in the navigation structure

 

To enhance portal performance, you can cache one instance of the top-level navigation iView for each role combination existing in your portal. All users with the same role combination will see the same top-level navigation, and will have the same instance in the cache, but users with different themes/languages/browser versions will have separate TLN instances.

Prerequisites

You have activated top-level navigation caching by selecting the Roles option of the Cache Level property of the TLN iView. For more information, see the Cache Level section in Caching.

Activities

  • The top-level navigation cache is not automatically refreshed. For optimal portal performance, set the Cache Validity Period property to a time span that correlates effectively with the relative stability of the TLN iView.

    For example, if the iView is stable, a valid setting would be 24 hours. If the iView is still undergoing frequent changes, a more logical setting would be 30-60 minutes, so that users have an up-to-date version of their top-level navigation bar.

  • If you have activated the top-level navigation cache, and set the cache validity to reflect a stable situation, do not update the iView too frequently within the set time span.

  • As with any cached iView, the top-level navigation iView cache consumes memory resources. Therefore, using the top-level navigation cache is reasonable when:

    • The number of role combinations is relatively small

    • It is likely that many users with the same role combination will log on to the portal during the specified time frame

    However, if the portal has many roles, and many role combinations, using the top-level navigation cache may not prove efficient.