Filter
Top Products
12
WEBSPHERE PORTAL V6.1 TUNING GUIDE
WebSphere Portal Services
WebSphere Portal has a number of configurable “services”; each service has several
parameters available to it. This section describes which services we tuned, the tuning values
used, and the rationale for those changes.
How to Set:
1. Edit <wp_profile_root>/PortalServer/config/properties/xxxService.properties
2. uncomment the line, then change the size.
3. run <wp_profile_root>/ConfigEngine/ConfigEngine.sh update-properties
The changes should appear on WAS Console -> Resource Environment Providers ->
WP_xxxService -> Custom properties
N A V I G A T O R S E R V I C E
The navigator service manages the content model for unauthenticated users, which controls
the pages those users are able to see. This content model is periodically reloaded by
WebSphere Portal; new pages which are visible to unauthenticated users will not be
available until the next reload occurs. Our environment assumes a low rate of change for
pages, so we set this reload to only occur once per hour. In a production environment where
new pages for unauthenticated users are rarely created, setting this reload time to an hour
or more will give better performance. In a test or staging environment where updates to
unauthenticated pages need to be seen more often, a lower reload time is more appropriate.
This service also controls the HTTP cache-control headers which will be sent on
unauthenticated pages. While our environment did not exploit HTTP page caching,
increasing these cache lifetimes in a production environment can reduce load on the portal.
For more discussion of the use of HTTP cache-control headers with WebSphere Portal,
refer to the “Caching” section of the “Tuning” topic in the WebSphere Portal V6.1 InfoCenter.
Table 4: Navigation Service Settings
NavigatorService.properties
Parameter
Default
Value
Value
Used
Definition
public.expires (seconds)
60 3600 Determines cache expiration time for caches
outside of WebSphere Portal and for
unauthenticated portal pages only. If the setting
remote.cache.expiration is also set to a value
greater than or equal to 0, the smaller one of the
two values is used.
public.reload (seconds)
60 3600 Determines cache expiration time for the portal
internal cache for unauthenticated pages
remote.cache.expiration
(seconds)
60 28800 Determines cache expiration for caches outside
of portal server for authenticated as well as for
unauthenticated pages