Revision as of 17:55, 17 December 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

Have an implementation plan
Know your infrastructure
Divide the compounds
1. Platform
2. Notes Mail Statistics
3. Network report
4. Server Load Statistics
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

DRAFT DOCUMENT.

Personalization Tuning

Make the default tuning based on WebSphre Portal Performance Tuning Guides

Personalization Services Tuning

This file is located at this location <profile root>/PortalServer/config/config/services/PersonalizationService.properties

Example: /opt/IBM/WebSphere/wp_profile/PortalServer/config/config/services/PersonalizationService.properties

rulesEngine.cache.timeout

The number of seconds before an entry in the cache expires. Increasing the length of the cache timeout if content doesn't change rapidly (what is the case for this customer), the default value is 300.

rulesEngine.cache.timeout=36000

rulesEngine.cache.enabled.collectionName AND rulesEngine.cache.timeout.collectionName

rulesEngine.cache.enabled.collectionName = The variable collectionName is the fully qualified path to the resource collection in Personalization.
rulesEngine.cache.timeout.collectionName = The same as rulesEngine.cache.timeout, except that this property applies to a specific resource collection.

rulesEngine.cache.enabled.ibmpznnt:rule=true 
rulesEngine.cache.timeout.ibmpznnt:rule=36000
rulesEngine.cache.enabled.ibmpznnt:campaign=true
rulesEngine.cache.timeout.ibmpznnt:campaign=36000
rulesEngine.cache.enabled.ibmpznnt:ruleMappings=true 
rulesEngine.cache.timeout.ibmpznnt:ruleMappings=36000
rulesEngine.cache.enabled.ibmpznnt:resourceCollection=true
rulesEngine.cache.timeout.ibmpznnt:resourceCollection=36000
rulesEngine.cache.enabled.ibmpznnt:applicationObject=true
rulesEngine.cache.timeout.ibmpznnt:applicationObject=36000
rulesEngine.cache.enabled.ibmpznnt:uuidPathConversion=true
rulesEngine.cache.timeout.ibmpznnt:uuidPathConversion=36000
rulesEngine.cache.enabled.ibmpznnt:jcrNodeType=true  
rulesEngine.cache.timeout.ibmpznnt:jcrNodeType=36000

rulesEngine.attributeBasedAdmin.enableCaching

Use this property to determine whether or not to cache the results of rules used in attribute based admin.

rulesEngine.attributeBasedAdmin.enableCaching=true

rulesEngine.user.nestedGroupLookup

In addition, there is an undocumented property which can be set to false to speed up PZN. This should only be done if (and only if) nested groups are NOT used in the authorization ACL lists in Portal

rulesEngine.user.nestedGroupLookup=false

rulesEngine.bypassWebContentLink

Use this property to bypass the return of web content links in results. By default PZN returns results for content links as well as items, it is recommend disables support for links, queries will run about twice as fast.

rulesEngine.bypassWebContentLink=true