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

From Wiki
(Criou nova página com 'DRAFT DOCUMENT. = Service Settings = * There are different forms of caching within PZN - resource collection caches, visibility rule caches, and others. However, Porta...')
 
No edit summary
Line 1: Line 1:
DRAFT DOCUMENT.
DRAFT DOCUMENT.


= Service Settings =
= Infra- Structure Level =
== Personalization Tuning ==
 
Make the default tuning based on WebSphre Portal [http://www-10.lotus.com/ldd/portalwiki.nsf/xpViewCategories.xsp?lookupName=Performance%20Tuning%20Guides Performance Tuning Guides]
 
== PersonalizationServices.properties ==


* There are different forms of caching within PZN - resource collection caches, visibility rule caches, and others.  
* There are different forms of caching within PZN - resource collection caches, visibility rule caches, and others.  

Revision as of 17:24, 17 December 2013

DRAFT DOCUMENT.

Infra- Structure Level

Personalization Tuning

Make the default tuning based on WebSphre Portal Performance Tuning Guides

PersonalizationServices.properties

  • There are different forms of caching within PZN - resource collection caches, visibility rule caches, and others.

However, Portal disables the PZN visbility cache by default. Modify the property in PersonalizationService.properties:

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=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
  • 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