Setting up command caching for marketing

Cacheable commands eliminate much of the processor usage associated with running redundant database queries by storing results from earlier queries in a cache. The marketing services can retrieve data to display in e-Marketing Spots on store pages from the command cache instead of the database. This retrieval improves response time and reduces system load.

Before you begin

Review the following document to understand the methods used to generate a key:

Procedure

  1. Open the sample cache configuration file cachespec.xml in the following directory:
    • WebSphere Commerce DeveloperWCDE_installdir/samples/dynacache/marketing/
    • WC_installdir/samples/dynacache/marketing/
  2. Copy all the cache entries from the sample cache configuration file to the cachespec.xml file found in the following directory:
    • WebSphere Commerce DeveloperWCDE_installdir/workspace/Stores/WebContent/WEB-INF/
    • WC_eardir/Stores.war/WEB-INF/
  3. Optional: If you are using a staging server, or a utility such as massload, clear the marketing command cache entries once the data is pushed to production.
    Note: This step is not required if you are using a staging server while using e-Marketing Spot JSP caching technique based on activity behavior. But it is required when using a utility such as massload with any caching technique.