Administer > Dynamic caching > Improve marketing performance using caching
Command caching for marketing
The most expensive part of evaluating a marketing rule is the query to return the Service Data Object (SDO) business object (for categories, catalog entries, and marketing content) that displays in an e-Marketing Spot. Command caching stores the results of earlier queries in cache to take advantage of lower retrieval times compared to retrieving results from main storage.
The sample cachespec.xml can be found in the following location:
- WCDE_INSTALL\samples\dynacache\marketing\
- WC_INSTALL\samples\dynacache\marketing\
Display Promotion action
If you are using the Display Promotion action, then update the cachespec.xml to use the command RetrieveContentTaskCmdImpl instead of the command FilterContentTaskCmdImpl. If you are not using the Display Promotion action, then using FilterContentTaskCmdImpl is fine.
Cache entry verification
To verify that cache is receiving data properly check the cache entries in the cache monitor.
Typical cache entry
Template Cache ID Timeout Dependency ID com.ibm.commerce.marketing. commands.marketingspot. FilterContentTaskCmdImpl com.ibm.commerce.marketing.commands.marketingspot. FilterContentTaskCmdImpl: getCacheKey=10201:getStoreId=10101: getLanguageId=1:getActivityId=11500: getCatalogId=10101:getContracts=11001: getActiveOrg=2000: getExperimentId=:getTestElementId= 10800 dialogMarketingCommand activityId:11500 contentId:10201 If you experience problems after you have updated the cachespec.xml file, see Troubleshoot: Caching not working after updating cachespec.xml.
Cached data invalidation
Establish that data is correctly added to the cache; then ensure that the cached data being retrieved is not stale or invalid. Command-based invalidation polices in the cachespec.xml file ensure that users of the Web site are not browsing content which has, while stored in cache, been changed in the database. For example, when items are added to, or removed from a catalog, or a price has changed, such changes are not reflected in the data already stored in the cache. For more information, see Command based invalidation.If the marketing information in the database is updated by using SQL statement, the mass load utility, or staging utilities, then clear all cached information.
To clear marketing information in the command cache, business object cache, and JSP caches, select the Marketing registry in the Administration Console Registries page. See Update registry components.
Related concepts
Marketing business object cache overview
Data recording; improving runtime performance
Related tasks
Set up command caching for marketing
Tune the marketing business object cache
Related reference
Commands and methods for generating a cache key