Caching the Top-Level Navigation iView 

Use

As an enhancement to portal performance, you can cache one instance of the top-level navigation (TLN) iView for every role combination existing in your portal. Although all users with the same role combination will see the same TLN, and have the same instance in the cache, users with different themes/languages/browser versions will have separate TLN instances, as this is generic iViews-Cache behavior.

Prerequisites

You have activated TLN caching by selecting the Roles option of the Cache Level property of the TLN iView.

Activities

·        The TLN cache is not automatically refreshed. For optimal benefit and portal performance, set the Cache Validity Period property for 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 10-15 minutes, so that users have an up-to-date version of their TLN bar.

·        If you have activated the TLN 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 TLN iView cache consumes memory resources. Therefore, using the TLN 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 validity period time frame

However, if the portal has many roles, and many role combinations, using the TLN cache may not prove efficient.