Dyna caching in WCS

Caching improves response time and reduces system load to improve the performance of world-wide web applications.
The Dyna caching service includes:-
ü  Servlet or JSP result cache, caching the fragments of JSP or whole page.
ü  Command cache to cache business objects.
ü  Edge Side Include (ESI) caching to cache, assemble and deliver the dynamic web pages at the edge of enterprise network.
ü  Invalidation support to ensure that the content of cache is correct. Invalidation can be rule-based, time-based, group-based and programmatic.
ü  Replication support, to enable cache sharing and replication on multiple servers.
ü  Disk offload capability, to enable and storing large amount of data, preserve the content in the application server until it is restarted or stopped.
The caching specific behaviour of the WCS is specified in the cachespec.xml present in the Stores.war.
Dyna caching service, places the objects in the cache which is identified by unique cache-id’s (<cache-id> rules) defined in the <cache-entry> elements.
Once the objects with particular cache-id are in the cache, then the subsequent request for the same cache-id is served from the cache.
Cached objects are removed from the cache according to the information provided in the <cache-entry> elements such as <time-out>, <invalidation> and<priority> elements.
When the available cache memory is full, LRU algorithm removes the cached objects with the lower priority.
The <dependency-id> and <invalidation> elements defines the rule to generate dependency-id’s and the invalidation-id’s, which together specifies certain objects should be removed from the cache after the request is processed.
The <inactivity> element is used to specify a time to live (TTL) value for the cache entry based on the last time that the cache entry was accessed.
Caching strategy
When determining a caching strategy for WebSphere Commerce, the key issues that need to be resolved are:
Ø  Which pages should be cached
Ø  Where caching should take place
Ø  Cache full pages or page fragments
Ø  How to invalidate the cached data.
Which pages should be cached?
When determining which Web pages should be cached, good candidates for caching are pages that:
Ø  Are accessed frequently
Ø  Are stable for a period of time
Ø  Contain a majority of contents that can be reused by a variety of users

The following <cache-entry> example uses a <cache-id> element to cache results created by a JSP and generate a cache ID with two components, "storeId" and "catalogId", obtained from parameters in the request object:
<cache-entry>
 <class>servlet</class>
 <name>/ToolTech/. . ./StoreCatalogDisplay.jsp</name>
 <property name="save-attributes">false</property>
 <property name="store-cookies">false</property>
 <timeout>3600</timeout>
 <priority>3</priority>
 <cache-id>
  <component id="storeId" type="parameter">
   <required>true</required>
  </component>
  <component id="catalogId" type="parameter">
   <required>true</required>
  </component>
 </cache-id>
...
</cache-entry>

Comments

Post a Comment

Popular posts from this blog

Dataload Utility In WCS

Data can be loaded into WCS tables using data load utility.   WCS Data Load utility performs the following functions in a single operation: 1.              Reads the data from the input source file. 2.              Transforms the source data to WebSphere Commerce business objects. 3.              Allocates and resolves WebSphere Commerce business objects to physical data. 4.              Loads the physical data into the database. There are three configurations files and a input source file required to complete the data loader setup. WCS supports only CSV File Reader for other input source you have to write your own Reader Class. This means that if you are using OOB CSVReader then your input file must be a CSV file. The three configuration files are listed below. 1.              wc-dataload-env.xml 2.              wc-dataload-loader.xml 3.              wc-dataload.xml wc-dataload-env.xml holds the environment settings such as database name,encrypted password,data
Read more

10 Steps to Configure Email – Websphere Commerce Server

10 Steps to Configure Email – Websphere Commerce Server Websphere Commerce Server – Configure Email Follow 10 steps for configuring email in Websphere Commerce Server Step 1: Create a JSP ( eg:- AbcEmailNotify.jsp) Create a JSP, lets name it AbcEmailNotify.jsp AbcEmailNotify.jsp will be used for displaying contents of email to recipient. Note: Currently keep AbcEmailNotify.jsp as blank (without any code) Step 2: Create View ( eg- AbcEmailNotifyView) Make an Entry in Struts-Config.xml file for AbcEmailNotify.jsp as below < action path=’/AbcEmailNotifyView’ type=’com.ibm.commerce.struts.BaseAction’> < set-property property =’authenticate’ value =’10101:1′/> < set-property property =’https’ value =’10101:1′/> < /action> < forward name=”AbcEmailNotifyView /10101/-3″ path=”/< location of JSP file >/AbcEmailNotify.jsp” className=”com.ibm.commerce.struts.ECActionForward”> < set-property property=”implClassName” value=”com.i
Read more

Multiple Wish List

Image
Multiple Wish List How to enable?  Go to Commerce Management Center → Store Management → Select Store →  Select Wish list, Widgets and Feeds Tab and check “Multiple wish lists” check box. Characteristic's of Multiple wish list 1.          Wish Lists are stored in gift registry tables. 2.          New Gift List SOA Service a) GiftList noun A subset of these elements is used to represent wish lists. The Boolean element Registry indicates whether the noun represents a gift registry or wish list. Wish List Display Code 1. User will be always having a default wish list. The code snippet to get default wish list for a user is 2.          Get details of the selected wish list of a user. Here “selectWishListExternalId”  is the identifier of the wish list selected by the user. This object snippet calls findGiftListByUniqueIDs expression build to get the specified SOA wish list 3.          Get all the wish lists for a user       < wc
Read more