WPS: WebSphere Portal: Tuning English: Difference between revisions

From Wiki
(Criou nova página com ''''Tuning''' This wiki will be creating a series of articles outlining best practices for IBM WebSphere Portal environment. I ask you to always return to this article w...')
 
No edit summary
Line 16: Line 16:
# Have a baseline reference
# Have a baseline reference


= '''JVM Tuning''' =
= '''Web Content Manager''' =


== '''Personalization:''' ==
== '''Personalization:''' ==

Revision as of 18:35, 4 November 2013

Tuning

This wiki will be creating a series of articles outlining best practices for IBM WebSphere Portal environment.

I ask you to always return to this article will be updating as usual.

Steps

  1. Have an implementation plan
  2. Know your infrastructure
  3. Divide the compounds
    1. Platform
    2. Notes Mail Statistics
    3. Network report
    4. Server Load Statistics
  4. Have a baseline reference

JVM Tuning

Web Content Manager

Personalization:

Improve the performance of the personalization (PzN) function in WebSphere Portal.

Important: PersonalizationService.properties file is not managed by the DMGR, you need to change in all servers in the cluster.

Enabling Caching in Personalization

You can enable caching for Personalization.

Open file /opt/IBM/WebSphere/wp_profile/PortalServer/config/config/services/PersonalizationService.properties and set the property

rulesEngine.attributeBasedAdmin.enableCaching=true


Disable Nested Group Lookup in Personalization (UNDOCUMENTED)

if you don't have nested groups, you can disable nested group lookup.

Open file /opt/IBM/WebSphere/wp_profile/PortalServer/config/config/services/PersonalizationService.properties

set the property

rulesEngine.user.nestedGroupLookup=false