caching on detailed navigation besides navigation cache?

[Former Member]

Hello Everyone,

We use Btexx EasyWCM as a content management system on our SAP NW portal.

When we create a new page in the portal it should appear directly in the detailed navigation, but instead it appears much much later, often after more then an hour. The same happens when deleting a page.

We thought of navigation cache at first but we disabled it and the problem was still there.

Because the new page does appear after a while, what makes it time-based, we still think it might be a caching issue. We don't know what other caches influence the detailed navigation.

The page does appear in the PCD (role) directly after it is made, same goes for deletion.

We tried a restart already, but that didn't resolve anything. And I donu2019t think it's a network problem because the PCD updates instantly. Just the detailed navigation doesn't. Even when we changed the customised detailed navigation back to the standard SAP detailed navigation there was no difference.

We tried creating a page directly on the server so the caches of the proxy's etc could be excluded and the problem was still there.

Thanks.

[Former Member · Accepted solution]

Hello Sander,

that's a strange behaviour...

Have you checked the Portal Runtime Cache? Each iView can be configured to use the PRT Cache via the iView Property "CachingLevel". If the PRT cache is e.g. enabled for your detailed navigation iView that could explain the delay...

Hope that helps!

Michael

Michael Beining

SAP NW Portal Technology Consultant

btexx business technologies GmbH - The Portal Experts

[www.btexx.de]

[Former Member · Accepted solution]

Hello Michael,

Thank you for your reply. That was a good idea and I checked it.

However it didn't turn out to be the problem. What was the case is that the setting for the navigation cache was only turned off in the frontend and was still very much on in the backend.

I can't look into those backend settings from here but the people who could set it to false and the problem was gone.

Greetings Sander van Laarhoven.

[Former Member]

Hello Sander,

that's good to hear. But you do not need not turn the navigation cache off.

easyWCM supports the new Navigation Cache API. If a editor changes navigation structures, easyWCM automatically invalidates the relevant roles from the cache.

Please check if your SAP Portal release and easyWCM release supports that feature.

More information are available on our support plattform:

http://www.btexx.de/support/

Best regards,

Michael