If you use ATG scenarios or workflows, and your site is running more than one ATG application, it is highly recommended that you use locked cache mode for scenario and workflow item descriptors as described in the ATG Personalization Programming Guide. This setting is enabled when you use the liveconfig configuration layer for the appropriate module.

If you use locked cache mode, you should disable the query cache, since query cache invalidation messages are not distributed between server instances. If query caching is important for the performance of your application, use distributed cache mode. Remember also that you can invalidate caches using a time expiration setting (see the Cache Configuration: Cache Timeout section) or by sending cache invalidation events programmatically (see Cache Flushing).

 
loading table of contents...