Administer > Dynamic caching > WebSphere Commerce data cache
Invalidate WebSphere Commerce data cache entries
When data in the database is created, updated, or deleted, using WebSphere Commerce tools, the cache will be kept automatically up to date. Data updated using methods such as mass loading of catalog or price data may need to be invalidated using additional methods of cache invalidation.
Procedure
WebSphere Commerce provides two additional methods of performing cache invalidation:
- Use java programming to call the methods of the WCDataCache java class. These methods accept the database table name, and optionally the column names and values in a row that was created, updated, or deleted, and perform the appropriate cache invalidations. WCDataCache works when executing within the WebSphere Commerce environment and will not work when executing in a stand-alone java utility.
- Define and use the database triggers defined in the wcs.cacheivl.trigger.sql script. These database triggers cause specially formulated invalidation IDs to be appended to the CACHEIVL database table, in the DATAID column. The DynaCacheInvalidationCmd scheduler job processes the CACHEIVL rows and issues appropriate cache invalidations. When this technique is used there is a period of time between when the database changes are made and when the DynaCacheInvalidation scheduler job performs the invalidations. During that time period, the old stale cached data will be used.
Related concepts
Additional WebSphere Commerce data cache configuration
Related reference
Logical cache names and the DistributedMaps they use by default
Access bean classes extended to take advantage of WebSphere Commerce data cache
Data bean classes extended to take advantage of WebSpere Commerce data cache