Customizing Web page cache settingsAdded by IBM on December 16, 2010 | Version 1 (Original)
|Web page caching greatly improves the response time of the IBM® Lotus® Quickr™ server. Use the notes.ini file to customize Web page cache settings.
Web page caching greatly improves the response time of the IBM® Lotus® Quickr™ server. Use the notes.ini file to customize Web page cache settings.
About this task
Without a cached copy of a Web page, the HTTP server must access the database upon every HTTP request, which results in a slower response time for the Lotus Quickr server. If a Web page is cached, the server only has to pick up the page from the database one time, and then create a user-specific, cached copy of the page at that time. Upon subsequent requests for the page, the server retrieves and provides the cached copy, as long as it is still valid. If the server is brought down, the existing cache is maintained after the server is brought back up.
Certain actions cause the cache for a page to become invalid. Once a cached paged is invalid, the next time the page is accessed it is re-cached. Following are some examples of how the entire cache or specific pages within the cache can become invalid:
- A change to the server configuration made through the Site Administration link, for example a change to the default maximum attachment size allowed, invalidates all places on the server (the entire cache).
- If the Place Catalog is enabled, a change in the Place Catalog database invalidates the entire cache.
- A change in qpconfig.xml invalidates the entire cache.
- A change to place membership -- a member is added, modified, or deleted -- invalidates the cache for all databases associated with that place -- main.nsf and all the inner rooms. A change to inner room membership invalidates the cache for that particular room and its child rooms.
- A change in rooms -- a room is created or deleted -- invalidates the cache for all databases associated with that place.
- A page published in the Main room (main.nsf) invalidates the cache for all databases associated with that place.
- A page published in a parent room invalidates the cache for the parent room and the child rooms below it.
- A page published in a child room invalidates the cache for the child room and for any rooms below it. The cache for the parent room pages remain valid.
- A customization to a parent room, for example a theme change or a custom form, invalidates the cache for the parent room and the child rooms below it.
Perform the following steps to adjust Web page cache settings:
- Open the notes.ini file in the domino_server_root directory with a text editor.
- Specify any settings described in Table 1 .
- Make sure to leave a blank line at the end of the file. Press Enter, if necessary, to create one.
- Close and save the file.
- Enter the following command at the server console to restart the server so your changes takes effect:
What to do next
Table 1. Web page cache settings in the notes.ini file
|QuickPlaceWebCacheEnabled=value||Enables or disables Web page caching. When set to 1 or omitted, enables Web page caching. When set to 0, disables Web page caching. |
|QuickPlaceWebCacheDir= path||Specifies the full path to the cache directory on the server. If omitted, the default path is domino_data_root/domino/lotusquickr/cache.|
|QuickPlaceWebCacheLimitInMB=size||Specifies a maximum size, in MB, for the cache. If omitted, or if a negative value is specified, the maximum size is 50 MB.|
|QuickPlaceWebCacheGCIntervalInMIN=interval||Specifies the time interval, in minutes, for cache cleaning. If omitted, or if a negative value is specified, then the interval is 60 minutes.|
|QuickPlaceWebCacheUsers=anonymous||Enables caching for anonymous users only. If omitted, and by default, caching is enabled for all users.|
|QuickPlaceWebCacheLogging=level||Specifies the level (1, 2, 3), for cache logging. Level 1 is the least detailed and 3 is the most detailed. Logging is written to domino_data_root/log.nsf.|
Parent topic: Configuring services for Lotus Domino