Popular Posts

  • Extending an SOI service with UserData
    C ustomization of the Order noun by using the UserData field. This involves extending the Order noun of the Web services archite...
  • Persistent Sessions in WCS
    WebSphere Commerce can be configured to enable persistent sessions. This enables some session-related information of the registered or gues...
  • WCS Data Cache
    Data that is cached by the WebSphere Commerce data cache can be configured by using either the command caching or DistributedMap objects c...
  • WCS Calculation Framework
    WCS need to calculate monetary amounts and apply them to business objects. Business rules and legal requirements specify how and when thes...
  • WCS Commands in Catalog Subsystem
    The Catalog Subsystem contains all logic and data relevant to an online catalog, including catalog groups (or categories), catalog entries...
  • WCS Order Management Commnds
    The Order Management subsystem includes all logic and data relevant to placing, processing, and managing orders.  This is done using variou...
  • Store with Multiple Languages and Multiple Currencies
    What if a store has to support multiple currencies to sell based on the language/country ? Here is a smal POC done to make it work. PFB...
  • WCS Subsystems
    WCS framework is majorly used fo E-Commerce Sites development on basis of many subsystems, which helps in developing and integrating diffe...
  • WCS Promotions
    Promotions provide the ability to offer customers incentives to purchase. WebSphere Commerce supports numerous types of promotions. For e...
  • WCS Payment Subsystem
    The Payments subsystem helps us manage the payment information. It connects to Payment Service Providers by using payment plug-ins. Paymen...

Cache Invalidation

Cache invalidation can be based on time, user or other variables. There are four methods to invalidate the dyna cache.
  •     Time based invalidation
  •     Command based invalidation
  •     Dynacache API and CACHEIVL table invalidation
  •     Group based invalidation

Time based invalidation: This is useful when the cache entries cannot be invalidated by any other mechanism, or they should be refreshed after a set period. This method can be accomplished by specifying the <timeout>value</timeout> sub-element with a cache-entry in the cachespec.xml file

This is especially useful for user dependent cache entries where the an average user session duration can be specified as an inactivity timeout.

Command based invalidation: Invalidation occurs upon execution of a command, based on invalidation rules, that extends from the WebSphere Commerce Command Framework API. Invalidation IDs for command-based invalidation are constructed based on methods and fields provided by the commands. Such commands extend from CacheableCommandImpl.

Dynacache API and CACHEIVL table invalidation: WebSphere Application Server dynamic caching provides the following Java classes to support programmatic invalidation
  •     com.ibm.websphere.cache.DistributedMap
  •     com.ibm.wsspi.cache.Cache
  •     com.ibm.websphere.cache.Cache
WebSphere Commerce provides a DynaCacheInvalidation command, which is called by the scheduler periodically to process the records in the CACHEIVL table and call the above WebSphere Application Server dynamic cache Java classes to invalidate the specified cache entries. By default, the schedule interval is every ten minutes.

Group based invalidation: Using dependency trees we can create conceptual groupings of the cache-entries, and invalidate based on those groups.

No comments:

Post a Comment

Subscribe to: Posts (Atom)