IBM Support

JR44939: CMVC 225347 - PROVIDE IMPROVED INVALIDATION OF THE MARKETING OBJECT CACHE AS PART OF RUNNING THE STAGINGPROP UTILITY

Direct link to fix

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When propagating Marketing data between the Authoring/Staging
    server to production, in order to have the database updates
    reflected to the end user, the CampaignInitiativeCache registry
    needs to be cleared so that the new data is reflected in the
    system, as per the following document in the Information Center
    for WebSphere Commerce 7.0:
    http://pic.dhe.ibm.com/infocenter/wchelp/v7r0m0/topic/com.ibm.co
    mmerce.admin.doc/tasks/tssprodadbtriggers.htm
    
    Running a refresh of the CampaignInitiativeCache will cause all
    data in the cache to be removed, while the stagingprop may have
    only updated a few elements that are in the cache. This may
    cause a performance impact while customers browse the site and
    view e-Marketing Spots, forcing the entries to be reloaded into
    the cache.
    

Local fix

Problem summary

  • USERS AFFECTED:
    WebSphere Commerce v7 users who perform a stagingprop of
    Marketing data during high load and the store heavily leverages
    Marketing web activities.
    
    PROBLEM ABSTRACT:
    Improvements to Marketing Data Cache invalidation during
    stagingprop utility execution
    
    BUSINESS IMPACT:
    Improve the performance of the system after stagingprop of
    Marketing data
    
    RECOMMENDATION:
    

Problem conclusion

  • The stagingprop utility has been enhanced to insert rows to the
    production server CACHEIVL table based on the exact Marketing
    data that was updated during the execution of the stagingprop
    utility.  The rows inserted into the production server CACHEIVL
    table represent new dependency IDs used within the Marketing
    Data Cache to invalidate only the cached entries that relate to
    the database entries that were updated while running the
    stagingprop utility.
    
    By having this enhancement installed, there is no longer a
    requirement to clear the entire CampaignInitiativeCache.
    Triggers created to do "WCR+CampaignInitiativeCache"
    invalidation should be removed.
    
    This enhancement includes the ability to control the amount of
    time entries remain in the marketing cache. To change the
    default values, configure the following settings in a custom
    marketing wc-admin-component.xml file.
    
          <!-- The settings (in minutes) for how long entries remain
    in the marketing cache.
               timeToLiveMarketingCache - The time to live value of
    cache entries. Cache entries will
                           expire after being in the cache for the
    configured amount of time. The default is
                           set to 48 hours (2880 minutes). Set the
    value to -1 to allow entries to
                           remain in the cache indefinitely and rely
    exclusively on explicit invalidation.
                           If you have a large number of marketing
    activities, then you may want to use
                           the timeToLiveMarketingCacheMax setting
    to spread the expiration of entries over
                           a period of time.
               additionalTimeToLiveMarketingCache - The maximum
    amount of additional time to add to the
                          timeToLiveMarketingCache value to set the
    time to live of cache entries.
                          This is an optional value that will assign
    time to live values that range between
                          timeToLiveMarketingCache and
    (timeToLiveMarketingCache + additionalTimeToLiveMarketingCache).
                          This is useful to allow the rebuild of the
    cache to be spread out over a period of time.
                          The default is set to 12 hours (720
    minutes). By default, cache entries will be randomly
                          assigned a time to live value between 48
    and 60 hours (48 + 12). The setting is not used
                          if timeToLiveMarketingCache is set to -1.
    If only timeToLiveMarketingCache is set, then
                          all cache entries will have that value.
               inactivityMarketingCache - The amount of time after
    which a cache entry will be removed
                          from the cache if the entry has not been
    accessed within that time. The default is
                          set to 24 hours (1440 minutes).
          -->
          <_config:property name="timeToLiveMarketingCache"
    value="2880"/>
          <_config:property
    name="additionalTimeToLiveMarketingCache" value="720"/>
          <_config:property name="inactivityMarketingCache"
    value="1440"/>
    
    See the following topic on creating a custom marketing
    wc-admin-component.xml file:
    http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/topic/com
    .ibm.commerce.management-center_customization.doc/tasks/tsbwcadm
    incom.htm
    
    -------------------------------------------------------------
    The latest available maintenance information can be obtained
    from the Recommended Fixes for WebSphere Commerce technote:
    http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
    

Temporary fix

Comments

  • COMMENTS
    

APAR Information

  • APAR number

    JR44939

  • Reported component name

    WC BUS DEV ED W

  • Reported component ID

    5724I3900

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function

  • Submitted date

    2012-11-29

  • Closed date

    2013-04-03

  • Last modified date

    2013-04-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WC BUS DEV ED W

  • Fixed component ID

    5724I3900

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSYT2H","label":"WebSphere Commerce Developer Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]

Document Information

Modified date:
07 December 2021