78
WEBSPHERE PORTAL V6.1 TUNING GUIDE
entry to the cache involves one database query. One entry is fairly small. Typically there
is no need to modify the settings for this cache.
P O L I C Y
The WebSphere Portal policy manager uses the following caches.
com.ibm.wps.policy.services.PolicyCacheManager
Default size: 1000, default lifetime: 7780, usage pattern: regular.
This cache stores the policies. Out of the box portal comes with twelve theme policies
and one mail policy, each of them being one entry into the cache. Hence the maximum
number of cache entries depends on your system and the number of custom policies.
This cache is accessed fairly often, if you use policies at all. The WebSphere Portal V6.0
default theme uses policies and query this cache during every request, but it is possible
to create themes that do not use policies at all. Furthermore when opening mails the
cache is accessed. Creating a cache entry involves reading data from a database. An
entry into the cache is fairly small.
com.ibm.wps.policy.services.UserPolicyNodeCacheManager
Default size: 2500, default lifetime: 600, usage pattern: regular.
This cache stores connections between a policy and a policy target, for example a user
distinguished name. Theme policies do not use targets, hence there is no cache entry
based on these policies. The out-of-the-box mail policy uses the user as target. Hence
there is at least one entry for every user accessing the CPP mail portlet. The size of a
cache entry depends on the size of the target object. For a distinguished name a cache
entry is fairly small.
C O L L A B O R A T I O N S E R V I C E S
All of the following caches are used by the DEPP portlets and some services around these
portlets. In so far the caches are not used if the DEPP portlets are not utilized in the portal
system. These caches store credential information needed for the backend servers, server
information for these servers and user information that would otherwise require LDAP
lookups.
com.lotus.cs.services.directory.ldap.BasicLDAPDirectoryService.server
Default size: 50, default lifetime: infinite, usage pattern: regular.
This cache stores mail server information. In so far it scales with the number of different
mail servers used in the environment. It is accessed whenever a mail server is
accessed. Creating a cache entry requires one LDAP search. An entry in the cache is
fairly small.
