WCM: Web Content Manager: Tuning English: Difference between revisions

From Wiki
No edit summary
Line 15: Line 15:
  <profile root>/PortalServer/config/config/services/PersonalizationService.properties  
  <profile root>/PortalServer/config/config/services/PersonalizationService.properties  


Check for:


=== 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.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.enabled.ibmpznnt:rule=true  
  rulesEngine.cache.timeout.ibmpznnt:rule=36000
  rulesEngine.cache.timeout.ibmpznnt:rule=36000
Line 39: Line 50:
  rulesEngine.cache.timeout.ibmpznnt:jcrNodeType=36000
  rulesEngine.cache.timeout.ibmpznnt:jcrNodeType=36000


* There are different forms of caching within PZN - resource collection caches, visibility rule caches, and others.  
=== rulesEngine.attributeBasedAdmin.enableCaching ===
However, Portal disables the PZN visbility cache by default. Modify the property in '''PersonalizationService.properties''':
 
Use this property to determine whether or not to cache the results of rules used in attribute based admin.


  rulesEngine.attributeBasedAdmin.enableCaching=true
  rulesEngine.attributeBasedAdmin.enableCaching=true


* 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 ===
 
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.user.nestedGroupLookup=false


* 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=900
=== rulesEngine.bypassWebContentLink ===


* 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. Set  in '''PersonalizationService.properties'''
* 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. Set  in '''PersonalizationService.properties'''


  rulesEngine.bypassWebContentLink=true
  rulesEngine.bypassWebContentLink=true

Revision as of 17:43, 17 December 2013

DRAFT DOCUMENT.


Infra- Structure Level

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 

Check for:

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

  • 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. Set in PersonalizationService.properties
rulesEngine.bypassWebContentLink=true