IBM BS029ML - WebSphere Portal Server, Self Help Manual

Page: 173 / 242

Chapter 5. WebSphere Portal runtime and services
159
Table 5-21 Portlet Container Service
Consult the Information Center for additional parameters that can be modified.
PUMA Service
The options configured under the PUMA Service affect the performance characteristics of the
internal PUMA layer, the function of which is to build a member object associated with a
user’s specific attributes. This is achieved in part by submitting a request to another internal
Portal component called WWM. For efficiency, PUMA was designed to initially request a
minimum subset of attributes from WMM, which would in most circumstances fulfill most
member object requests.
The user.base.attributes property is a comma separated list of attributes that will be
requested initially from WMM by PUMA when a user first logs in. The user.minimum.attributes
property is a comma-separated list of attributes that will be requested initially from WMM by
PUMA. If Portal or a Portlet requests an attribute that is not defined in the list, PUMA is then
forced to make a subsequent request for the entire attribute subset. This is somewhat costly
in terms of performance, as additional queries to the user data store will result. Table 5-22
shows the default and recommended values for the PUMA Service.
Table 5-22 PUMA Service
You should ensure that both the user.minimum.attributes and group.minimum.attributes
settings contain the attributes deemed necessary for your requirements. If Portal (or a Portlet)
requests an attribute that is not present in any of the above lists, PUMA will make a second
request to the user registry. However, such a request will actually be for a full attribute set
retrieval, from the user registry through WMM.
Registry Service
The parameters found under the Registry Service control the expiry times of cached
instances of various Portal objects read from the database, such as cached Portlets, themes
and skins, and so on. By default, the majority of these buckets are set to expire at the same
regular time interval. However, a semaphore does exist in the applicable code to prevent
simultaneous reloading, which would otherwise lead to temporary lockups. For beneficial
results, setting the values at slightly different intervals may help to prevent the refreshes from
hitting the database at the same time. Furthermore, the staggering can be extended to
horizontally clustered Portal Server deployments.
Parameter Default value Recommended value
parallel false true
legacy.useParallelRendering false true
std.useParallelRendering false true
Parameter Default value Recommended value
user.minimum.attributes uid,cn See notes.
user.base.attributes uid,cn,givenName,sn,preferred
Language See notes.
group.minimum.attribute cn See notes.