WebSphere Commerce data cache
Enterprise and Professional versions of WebSphere Commerce contain code to use the Websphere Dynamic Cache facility to perform additional caching of database query results. This additional caching code is referred to as the WebSphere Commerce data cache. The data cache is disabled by default.
- Enable WebSphere Commerce data cache
Each kind of data cached by the WebSphere Commerce data cache can be configured using one of two possible configuration methods: command caching or defining distributedMap objects.
- 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.
- Additional WebSphere Commerce data cache configuration
Further configuration of the WebSphere Commerce data cache can be done by adding a <CrossTransactionCache> element or a <LocalTransactionCache> element to the <InstanceProperties> element of the WebSphere Commerce configuration file.
- Logical cache names and the DistributedMaps they use by default
The following tables list the logical cache names under the DistributedMaps they use by default.
- Access bean classes extended to take advantage of WebSphere Commerce data cache
The following access bean classes have been extended to take advantage of the WebSphere Commerce data cache. Instances of these extended access bean classes can be obtained using the WCDataCache API and can be used in the same way as instances of the non-extended access bean classes.
- Data bean classes extended to take advantage of WebSpere Commerce data cache
The following data bean classes have been specifically coded to take advantage of the WebSphere Commerce data cache.