Websphere Member Manager Tuning - IBM BS029ML - WebSphere Portal Server Self Help Manual

Table 5-11 Session management settings
Parameter
Session Timeout (idle time)
However, the full implication of reducing the HttpSession timeout should be understood.
Unlike the LTPAToken timeout setting, which is an absolute timeout value, the HttpSession
timeout is based on inactivity and starts to time out each time after a user's last request. If a
user fails to interact with the Portal within the timeout period, the session expires and the user
will be advised with the message "Your portal session has timed out because of no activity.
Start a new session at your portal home."
In most cases, presenting users with this message and a redirection to the WebSphere Portal
Server login page maybe acceptable, as Portal navigation is more than intuitive for a user. It is
also worthwhile remembering that each Portlet application extends the HttpSession object
and has a separate session.

5.2.9 WebSphere Member Manager tuning

The WebSphere Member Manager (WMM) component of WebSphere Portal Server provides
an internal mechanism for managing member profiles. Both users and groups are considered
members, with WMM constructing a Java object for the resulting entity after performing the
necessary interaction with the underlying data store. However, Portal and Portlets do not
interface with WMM directly. Instead, requests are handled by the intermediary Portal User
Management Architecture (PUMA) layer. This layer of abstraction primarily exists due to
historical reasons and is anticipated to be removed in a future Portal version.
The WMM component of WebSphere Portal Server has a number of parameters that can be
specifically tuned to improve the login response time and the overall performance of the
Portal.
WMM cache configuration
You can tune the way in which WMM caches group information. This can be done by
modifying the wmm.xml file and adding the parameters detailed in Table 5-12.
Table 5-12 WMM cache parameters
Parameter
cacheGroups
groupsCacheTimeOut
attributesCacheSize
attributesCacheTimeOut
namesCacheSize
namesCacheTimeOut
Important: Since the group cache needs to cache all groups in WMM scope, it may cause
a memory problem if there are a large amount of groups. If there are more than 5000
groups in WMM scope, we recommend that groups cache be disabled.
Default value
30
Default value
false
600
2000
600
2000
300
Chapter 5. WebSphere Portal runtime and services
Recommended value
10
Recommended value
true
3600
2000
3600
2000
3600
153