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.
Administering caching in WebSphere Commerce
An administrator using caching in WebSphere Commerce should be familiar with full page and fragment caching, Edge Side include, and using the dynamic API not to cache.
Using dynamic API to not cache
Occasionally, it is not appropriate to cache a page that matches a caching rule, or a fragment within the cached page. In this case, the Dynacache API makes it possible to ignore the cache rule and not cache the page or fragment in question.

Using dynamic API to not cache

Occasionally, it is not appropriate to cache a page that matches a caching rule, or a fragment within the cached page. In this case, the Dynacache API makes it possible to ignore the cache rule and not cache the page or fragment in question.

Full page matching a rule: There are some circumstances where you do not cache a page, even though it matches a rule in the cachespec. For example if the pages content needs to be updated on each refresh using personalized data, or data that is current.
Fragment on a page matching a rule: It might be unsuitable to cache a section of a page for which consume-subfragments=true. For example, suppose a fragment was truly dynamic, and updated on each refresh of the page using personalized data. In this case, do not cache the fragment at all.

While this behavior cannot be achieved through the use of cachespec.xml, you can accomplish this with the Dynacache API.