Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Administering
Dynamic caching
In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.
Improving marketing performance by using caching
To improve marketing performance, use runtime caching to eliminate processing to and from the database.
Enabling JSP caching
Caching e-Marketing Spot JSP snippets can lead to a performance improvement.
Invalidating the JSP cache
JSP cache entries can be associated with one or more categories, catalog entries, and marketing content.

Invalidating the JSP cache

JSP cache entries can be associated with one or more categories, catalog entries, and marketing content.

Note: Invalidating JSP cache is not required when using e-Marketing Spot JSP caching based on activity behavior. For more information, see the Invalidation section in Overview of e-Marketing Spot JSP caching based on activity behavior.

The JSP cache key is not granular. Any change to the data requires all marketing JSP snippets to be cleared from the cache in order to pick up the latest data. To clear the cache you go to the Administration Console and update the CampaignInitiativeCache registry entry. The update of the CampaignInitiativeCache registry issues an invalidation for the key dialogMarketingJsp.

For information about how to clear the JSP cache, see Clearing the marketing Web service cache