IBM BS029ML - WebSphere Portal Server Self Help Manual page 172

installations. Table 5-19 shows the default and recommended values for the Deployment
Service.
Table 5-19 Deployment Service
Parameter
was.notification.timeout
Consult the Information Center for additional parameters that can be modified.
Navigator Service
Several attributes found under the Navigator Service can be modified to influence the
performance behavior of the Portal anonymous front page. By increasing the public.reload
setting, less of an impact will be made on the Portal database, as the database will be queried
less frequently to reload the page details. The default value of 60 seconds has the potential to
overwhelm the database and can increase without hesitation.
If the Portal anonymous front pages are not likely to change regularly, then the public.expires
setting can also be increased. The expiration value can be used by Portal to define the HTTP
expires header lifetime for anonymous front pages, in accordance with section 14.9.3 of RFC
2612 The CAST-256 Encryption Algorithm. The expiration value is, however, only applicable
for cached responses and not for first-time requests. It effectively sets the duration after which
the cached response is considered stale in a user's browser.
Under certain circumstances, it may prove necessary to create a session associated with the
Portal anonymous front page. This is achieved by setting the public.session parameter equal
to true, but is generally discouraged, as it tends to reduce Portal performance. Table 5-20
shows the default and recommended values for the Navigator Service.
Table 5-20 Navigator Service
Parameter
public.session
public.reload
public.expires
Consult the Information Center for additional parameters that can be modified.
Portlet Container Service
Parallel Portlet Rendering (PPR) permits portlets to be rendered in parallel rather than in
sequence. This means that the overall page aggregation response time can be greatly
accelerated. By default, the Portal is configured for parallel portlet rendering. However,
portlets themselves must be enabled to support the parallel rendering feature. Parallel portlet
rendering is particularly suited for portlets that call remote services or perform intensive I/O,
as a separate thread is spawned for each portlet. Table 5-21 on page 159 shows the default
and recommended values for the Portlet Container Service.
158
IBM WebSphere Portal V6 Self Help Guide
Default value
60
Default value
false
60
60
Recommended value
600
Recommended value
false, unless a session is
needed
600 or higher
60 or higher