Tuning the marketing business object cache

You can improve performance by altering the size of the cache that is used to store marketing business objects. You can cache the marketing business objects for a store and cache the information for customers that participate in marketing activities.

About this task

The object cache instance MarketingCache is used to cache the marketing business objects. The object cache instance MarketingUserCache is used to cache the information that is related to the customers that participate in marketing activities.
If your WebSphere Commerce environment is clustered, a MarketingCache object (DM_Cache) is created at both the server and cluster scope within the clustered environment. You can manage the cache objects individually at the server level for every server in your cluster. The settings for the cache objects at the server level override the settings for the cache object at the node or cluster level. If you want to use settings for the cache object at the cluster level, the server level objects must be deleted first.
Note: If you use the WebSphere eXtreme Scale dynamic cache provider and you are managing the cache objects individually at server level, you must set the same cache-size setting for every server in the cluster.
WebSphere Commerce Version 7.0.0.0WebSphere Commerce Version 7.0.0.1Note: Do not clear the DM_Cache with the WebSphere Application Server cache monitor. If the entire DM_Cache is cleared with the WebSphere Application Server cache monitor, then the marketing services do not detect the events that are associated with any behavior rules. As a result, certain triggers and targets that are used in marketing activities to detect customer behavior do not work properly. If you need to clear the DM_Cache, then update the Marketing registry with the Administration Console.

Procedure

  1. Open the WebSphere Integrated Solutions Console.
  2. Click Resources.
  3. Click Cache instances.
  4. Click Object cache instances.
  5. Click MarketingCache or MarketingUserCache and in the page that is displayed, change the value for the Cache size.
  6. Optional: If you are using a staging server, or a utility such as massload, clear the marketing cache entries when data is pushed into production.
    Feature Pack 5 or laterNote: This step is not required if you are using a staging server and you are using the e-Marketing Spot JSP caching technique that is based on activity behavior. But it is required when you are using a utility such as massload with any caching technique.