WCM: Web Content Manager: Tuning English - Revision history

Ebasso: Página substituída por 'Migrated to WPS: WebSphere Portal: Tuning English'

2013-12-18T13:02:31Z

Página substituída por 'Migrated to WPS: WebSphere Portal: Tuning English'

← Older revision		Revision as of 13:02, 18 December 2013
Line 1:		Line 1:
	~~DRAFT DOCUMENT.~~		Migrated to [[WPS: WebSphere Portal: Tuning English]]



	~~= 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~~]



	~~== Personalization Services Tuning ==~~

	~~This file is located at this location '''<profile root>/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~~

Ebasso: /* Personalization Services Tuning */

2013-12-17T17:49:35Z

Personalization Services Tuning

← Older revision		Revision as of 17:49, 17 December 2013
Line 14:		Line 14:

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


	=== rulesEngine.cache.timeout ===		=== rulesEngine.cache.timeout ===

Ebasso at 17:49, 17 December 2013

2013-12-17T17:49:16Z

← Older revision		Revision as of 17:49, 17 December 2013
Line 8:		Line 8:

	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]		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]



	== Personalization Services Tuning ==		== Personalization Services Tuning ==

Ebasso at 17:48, 17 December 2013

2013-12-17T17:48:33Z

Ebasso: /* Personalization Services Tuning */

2013-12-17T17:45:02Z

Personalization Services Tuning

← Older revision		Revision as of 17:45, 17 December 2013
Line 11:		Line 11:
	== Personalization Services Tuning ==		== Personalization Services Tuning ==

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

	~~<profile root>/PortalServer/config/config/services/PersonalizationService.properties~~

	~~Check for:~~

	=== rulesEngine.cache.timeout ===		=== rulesEngine.cache.timeout ===

Ebasso: /* Personalization Services Tuning */

2013-12-17T17:43:46Z

Personalization Services Tuning

← Older revision		Revision as of 17:43, 17 December 2013
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

Ebasso at 17:29, 17 December 2013

2013-12-17T17:29:53Z

@@ Line 1: / Line 1: @@
 DRAFT DOCUMENT.
 = 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 ==
+== Personalization Services Tuning ==
 * There are different forms of caching within PZN - resource collection caches, visibility rule caches, and others.

Ebasso at 17:24, 17 December 2013

2013-12-17T17:24:59Z

← Older revision		Revision as of 17:24, 17 December 2013
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.

Ebasso: 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...'

2013-12-17T17:16:40Z

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...'

New page

DRAFT DOCUMENT.

= Service Settings =

* 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

← Older revision		Revision as of 17:48, 17 December 2013
Line 20:		Line 20:
	rulesEngine.cache.timeout=36000		rulesEngine.cache.timeout=36000

	=== rulesEngine.cache.enabled.''collectionName'' ~~and~~ rulesEngine.cache.timeout.''collectionName'' ===
			=== rulesEngine.cache.enabled.''collectionName'' AND rulesEngine.cache.timeout.''collectionName'' ===


Line 28:		Line 29:
	rulesEngine.cache.enabled.ibmpznnt:rule=true		rulesEngine.cache.enabled.ibmpznnt:rule=true
	rulesEngine.cache.timeout.ibmpznnt:rule=36000		rulesEngine.cache.timeout.ibmpznnt:rule=36000

	rulesEngine.cache.enabled.ibmpznnt:campaign=true		rulesEngine.cache.enabled.ibmpznnt:campaign=true
	rulesEngine.cache.timeout.ibmpznnt:campaign=36000		rulesEngine.cache.timeout.ibmpznnt:campaign=36000

	rulesEngine.cache.enabled.ibmpznnt:ruleMappings=true		rulesEngine.cache.enabled.ibmpznnt:ruleMappings=true
	rulesEngine.cache.timeout.ibmpznnt:ruleMappings=36000		rulesEngine.cache.timeout.ibmpznnt:ruleMappings=36000

	rulesEngine.cache.enabled.ibmpznnt:resourceCollection=true		rulesEngine.cache.enabled.ibmpznnt:resourceCollection=true
	rulesEngine.cache.timeout.ibmpznnt:resourceCollection=36000		rulesEngine.cache.timeout.ibmpznnt:resourceCollection=36000

	rulesEngine.cache.enabled.ibmpznnt:applicationObject=true		rulesEngine.cache.enabled.ibmpznnt:applicationObject=true
	rulesEngine.cache.timeout.ibmpznnt:applicationObject=36000		rulesEngine.cache.timeout.ibmpznnt:applicationObject=36000

	rulesEngine.cache.enabled.ibmpznnt:uuidPathConversion=true		rulesEngine.cache.enabled.ibmpznnt:uuidPathConversion=true
	rulesEngine.cache.timeout.ibmpznnt:uuidPathConversion=36000		rulesEngine.cache.timeout.ibmpznnt:uuidPathConversion=36000

	rulesEngine.cache.enabled.ibmpznnt:jcrNodeType=true		rulesEngine.cache.enabled.ibmpznnt:jcrNodeType=true
	rulesEngine.cache.timeout.ibmpznnt:jcrNodeType=36000		rulesEngine.cache.timeout.ibmpznnt:jcrNodeType=36000


	=== rulesEngine.attributeBasedAdmin.enableCaching ===		=== rulesEngine.attributeBasedAdmin.enableCaching ===
Line 52:		Line 48:

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


	=== rulesEngine.user.nestedGroupLookup ===		=== rulesEngine.user.nestedGroupLookup ===
Line 62:		Line 59:
	=== rulesEngine.bypassWebContentLink ===		=== 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'''~~		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		rulesEngine.bypassWebContentLink=true