WebSphere Commerce store pages properties

WebSphere Commerce store pages properties

For a more complete list see the topic cachespec.xml file in the WAS Information Center. When caching WebSphere Commerce store pages, the following properties are used in the cachespec.xml file:

Property Value Valid classes Description

EdgeCacheable True or False Default is false. Servlet If the property is true, then the given servlet or JSP file is externally requested from an Edge Server. Whether the servlet or JSP file is cacheable depends on the rest of the cache specification.
consume-subfragments True or False. Default is false Servlet When a servlet is cached only the content of that servlet is stored. Placeholders for any other fragments to which it includes or forwards are created. Consume-subfragments (CSF) tells the cache to continue saving content when it encounters a child servlet via an include. The parent entry (the one marked CSF) will include all the content from all fragments in its cache entry, which result in one big cache entry that has no includes or forwards, but the content from the whole tree of entries. This method can save a significant amount of application server processing, but is typically only useful when the external HTTP request contains all the information needed to determine the entire tree of included fragments.
save-attributes True or False. Default is true. Servlet When save-attributes is set to false, the request attributes are not saved with the cache entry.
store-cookies True or False. Default is true. Servlet When store-cookies is set to false, the request cookies are not saved with the cache entry.
sharing-policy not-shared or shared-push or shared-pull or shared-push-pull. Default is not-shared.
When sharing-policy is set to not-shared cache entries for this object are not shared among different application servers. These entries can contain non-serializable data. When sharing-policy is set to shared-push cache entries for this object are automatically distributed to the dynamic caches in other application servers or cooperating JVMs. Each cache has a copy of the entry at the time it is created. These entries cannot store non-serializable data. When sharing-policy is set to shared-pull cache entries for this object are shared between application servers on demand. If an application server gets a cache miss for this object, it queries the cooperating application servers to see if they have the object. If no application server has a cached copy of the object, the original application server runs the request and generates the object. These entries cannot store non-serializable data. This mode of sharing is not recommended. When sharing-policy is set to shared-push-pull cache entries for this object are shared between application servers on demand. When an application server generates a cache entry, it broadcasts the cache ID of the created entry to all cooperating application servers. Each server then knows whether an entry exists for any given cache ID. On a given request for that entry, the application server knows whether to generate the entry or pull it from somewhere else. These entries cannot store non-serializable data.

By default, dynamic caching caches the cookies (when caching by servlet class) and all request attributes (servlet and JSP pages) along with the cache entries. However, WebSphere Commerce cookies and request attributes contain user specific information that should not be cached. As a result, the following property names and values are mandatory when caching full pages:
<property name="save-attributes">false</property>
<property name="store-cookies">false</property>
The following property name and value is mandatory for all cache-entries defined for the JSP files:
<property name="save-attributes">false</property>
Related reference

Caching defaults

Property	Value	Valid classes	Description
EdgeCacheable	True or False Default is false.	Servlet	If the property is true, then the given servlet or JSP file is externally requested from an Edge Server. Whether the servlet or JSP file is cacheable depends on the rest of the cache specification.
consume-subfragments	True or False. Default is false	Servlet	When a servlet is cached only the content of that servlet is stored. Placeholders for any other fragments to which it includes or forwards are created. Consume-subfragments (CSF) tells the cache to continue saving content when it encounters a child servlet via an include. The parent entry (the one marked CSF) will include all the content from all fragments in its cache entry, which result in one big cache entry that has no includes or forwards, but the content from the whole tree of entries. This method can save a significant amount of application server processing, but is typically only useful when the external HTTP request contains all the information needed to determine the entire tree of included fragments.
save-attributes	True or False. Default is true.	Servlet	When save-attributes is set to false, the request attributes are not saved with the cache entry.
store-cookies	True or False. Default is true.	Servlet	When store-cookies is set to false, the request cookies are not saved with the cache entry.
sharing-policy	not-shared or shared-push or shared-pull or shared-push-pull. Default is not-shared.		When sharing-policy is set to not-shared cache entries for this object are not shared among different application servers. These entries can contain non-serializable data. When sharing-policy is set to shared-push cache entries for this object are automatically distributed to the dynamic caches in other application servers or cooperating JVMs. Each cache has a copy of the entry at the time it is created. These entries cannot store non-serializable data. When sharing-policy is set to shared-pull cache entries for this object are shared between application servers on demand. If an application server gets a cache miss for this object, it queries the cooperating application servers to see if they have the object. If no application server has a cached copy of the object, the original application server runs the request and generates the object. These entries cannot store non-serializable data. This mode of sharing is not recommended. When sharing-policy is set to shared-push-pull cache entries for this object are shared between application servers on demand. When an application server generates a cache entry, it broadcasts the cache ID of the created entry to all cooperating application servers. Each server then knows whether an entry exists for any given cache ID. On a given request for that entry, the application server knows whether to generate the entry or pull it from somewhere else. These entries cannot store non-serializable data.