Public pages are pages that are visible to anonymous users. Once the user authenticates the protected area of Portal is rendered. The protected and public area of Portal have different URLs - e.g. in the default configuration it is /wps/portal for public pages and /wps/myportal for the protected area of Portal.
HCL Portal reloads the public page information at certain intervals. The intervals are controlled by the setting "public.reload" in WP NavigatorService. For best performance the interval should not be set too low since it will trigger a reload from the database.
Rather than triggering a manual cache flush our recommendation is to plan the cache timeouts accordingly and work with the business teams to understand by when their changes need to be in to show up with the configured cache timeout.
If despite the planning you need to trigger a reload of the public pages outside of the interval - e.g. because you need to publish a sales campaign right away - you can do that by flushing the cache "cacheinstance.com.ibm.wps.model.factory.public.pages.update". The cache can be flushed using the Extended Cache Monitor or a wsadmin script.
If despite the planning you need to trigger a reload of the public pages outside of the interval - e.g. because you need to publish a sales campaign right away - you can do that by flushing the cache "cacheinstance.com.ibm.wps.model.factory.public.pages.update". The cache can be flushed using the Extended Cache Monitor or a wsadmin script.
In case you are using WCM and have WCM content on the pages it might be necessary to also flush certain WCM caches. In difference to the public page reload that will happen in parallel to pages being served from the cache, clearing the WCM cache will have an immediate impact on the system and will effect both authenticated and anonymous users.