In response to: Automatic Application of Portal Tuning Parameters
Many Customer are asking what is changed by using this tool. I have
performed some research on the tool and based on the Tool update
from 03/19/14 here is what I have found related to the
configuration changes that are performed by the tool
The Bulk of the tuning changes that will be performed for the JVM
and web container service are found in the TuningTask directory in
the archive in the file named tuning.properties. The first 5 lines
are what the user sets for the environment they are configuring as
follows
# - this is set to true if wcm rendering is being used on the site
tuning.wcm=true
# - set the following to true for a subscriber only :ie this does
not syndicate content to other environments
tuning.wcm.subscriberOnly=true environments
#- this is set to false of running the command against a rendering
environment and true if it is an authoring environment
tuning.wcm.authoring=false - only set this to true for authoring
environments
# managed pages is a Portal V8+ feature that allows WCM to manage
page #definitions. If you want the "edit" button on the V8 theme,
you have to set #managedPages to "true"
tuning.wcm.managedPages.inlineEdit=true
#set the bit level of the jvm environment being configured
tuning.os.bit=64
#The other properties in this file sets the JVM Heap initial amd
Max size as well as
# other generic jvm arguments depending on the OS being used per
the tuning
# guide recommendations the values here are the values that will be
configured in
# the Process definition for the Server being configured
# The properties from here to the end of file are recommendations
from IBM on the
#initial tuning recommendations
tuning.64.linux.maxHeap=3584
tuning.64.zlinux.maxHeap=3584
tuning.64.zos.maxHeap=3584
tuning.64.windows.maxHeap=3584
tuning.64.aix.maxHeap=3584
tuning.64.unix.maxHeap=3584
tuning.64.os400.maxHeap=3584
tuning.32.linux.maxHeap=2048
tuning.32.windows.maxHeap=1408
tuning.32.aix.maxHeap=1792
## The next three OSes are not known to be used in 32 bit mode but
are included
# here for completeness
tuning.32.unix.maxHeap=1792
tuning.32.zlinux.maxHeap=1792
tuning.32.zos.maxHeap=1792
tuning.32.os400.maxHeap=1792
# this adds - Xmn<value> "nersey initial and max heap size
setting to the
# generic jvm arguments for the Process definition
# for the jvm being configured depending on whether its a 32 bit or
64 bit jvm
tuning.64.linux.nursery=1024M
tuning.64.zlinux.nursery=1024M
tuning.64.zos.nursery=1024M
tuning.64.windows.nursery=1024M
tuning.64.aix.nursery=1024M
tuning.64.unix.nursery=1024M
tuning.64.os400.nursery=1024M
tuning.32.linux.nursery=256M
tuning.32.unix.nursery=256M
tuning.32.aix.nursery=512M
tuning.32.zlinux.nursery=512M
tuning.32.zos.nursery=512M
tuning.32.windows.nursery=512M
tuning.32.os400.nursery=512M
## All these settings would be in the Generic JVM ArgumentsM
# sets -XX:MaxDirectMemorySize=256000000
tuning.all.DirectMemorySize=256000000
# sets --Xjit:iprofilerMemoryConsumptionLimit=67108864
tuning.all.MemoryConsumptionLimit=67108864
# sets -Dcom.ibm.websphere.alarmthreadmonitor.threshold.millis=
tuning.all.AlarmMonitor=40000
# sets -Xscmx150m note it must also be destroyed for this to take
effect
tuning.all.SharedClassCache=150m
# sets -Xcodecache20m if running on power 7 hardware
tuning.power7.CodeCache=20m
#for Portal servers running with Oracle Java the following generic
jvm arguments will be used
tuning.unix.Server=true
tuning.unix.MaxPermSize=-XX:MaxPermSize=768m
tuning.unix.UseConcMarkSweepGC=-XX+UseConcMarkSweepGC
tuning.unix.SurvivorRatio=-XX:SurvivorRatio=6
tuning.unix.UseParNewGC=-XX:+UseParNewGC
tuning.unix.ParallelGCThreads=-XX:ParallelGCThreads=5
tuning.unix.PrintGCDetails=-XX:+PrintGCDetails
tuning.unix.PrintGCTimeStamps=-XX:+PrintGCTimeStamps
#
## These sections set the min and max WebContainer thread pools to
50
#WebSphere Integrated Solutions Console
#Servers > Server Types > WebSphere application servers >
WebSphere_Portal # > Additional Properties: Thread Pools >
Web Container > Thread Pool
#minimum size = 50
#maximum size = 50
#inactivity timeout = 60000 this is in ms
tuning.all.webcontainer.min=50
tuning.all.webcontainer.max=50
tuning.all.webcontainer.timeout=60000
### This section update the datasources for JCR and Release. The
name of the
#datasource is obtained from wkplc_dbdomain.properties
#WebSphere Integrated Solutions Console: Resources > JDBC
Providers >
#provider name > Data Sources > data source name >
Connection pool
#properties
#JCR datasource connection pool min/max set to 10/110
# Release datasource connection pool min/max set to 10/55
tuning.all.datasource.jcr.size.max=110
tuning.all.datasource.jcr.size.min=10
tuning.all.datasource.release.size.max=55
tuning.all.datasource.release.size.min=10
## Security > Global security > Custom properties > New
#name: com.ibm.CSI.disablePropagation.CallerList
#value: true
tuning.all.disablePropagationCallerList.name=com.ibm.CSI.disablePropagation.CallerList
tuning.all.disablePropagationCallerList.value=true
## Security > Global security > Custom properties > New
#name: com.ibm.ws.security.ltpa.useCRT
#value: true
#Note the tuning Guid rcommends this be removed
#the code appears to be adding this property
tuning.all.ltpaUseCRT.name=com.ibm.ws.security.ltpa.useCRT
tuning.all.ltpaUseCRT.value=true
## Disable the Internalization Service on the server
#In the WebSphere Integrated Solutions Console
#Servers > Server Types > WebSphere application servers >
WebSphere_Portal
# > Container Services: Internationalization service
# Uncheck “Enable service at server startup”.
tuning.all.enableInternationalization=false
## Set the WAS session timeout
#Servers> Server Types> WebSphere application servers>
# WebSphere_Portal > Container Settings: Web Container Settings
> Session
# Management > Session Timeout > Set Timeout
tuning.all.webcontainer.sessionManagement.sessionTimeout=30
## Avoid Refreshing Static Content which allows the modular theme
to avoid
#reloads on login.
## These resources include the ra: collection URLs that are part of
the theme. The
#same URL can safely be used for authenticated and unauthenticated
users.
## The default is "lazy". "Persisting" provides better performance.
"Persisting"
#means the checkbox "Use available authentication data when an
unprotected
#URI is accessed" was checked.
# WebSphere Integrated Solutions Console: Security > Global
security
#2. Expand Web and SIP security
#3. Click on General Settings
#4. Check 'Use available authentication data when an unprotected
URI is
#accessed'
tuning.all.security.avoidRefreshStaticContent=persisting
## Set the WAS Enable Servlet Cache
#
#WebSphere Integrated Solutions Console Servers > Server Types
>
# WebSphere application servers > WebSphere_Portal > Web
Container
#Settings > Web container
#Check Enable servlet caching
tuning.all.webcontainer.enablecache.value=true
#WebSphere Integrated Solutions Console Servers > Server Types
>
# WebSphere application servers > WebSphere_Portal > Portlet
Container
#Settings > Portlet container
#Check Enable portlet fragment caching
## Set the Portet Container to enable portlet fragment caching
tuning.all.portletcontainer.enablecache.value=true
Resource Environment Provider Changes
WebSphere Integrated Solutions Console > Resources >Resource
Environment
> Resource Environment Providers
<ResourceEnvironmentProviderName>
The following are performed for Portal servers version 7 or version
8+
WP CacheManagerService
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.ac.AccessControlUserContextCache.size=6000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.ac.ChildResourcesCache.lifetime=28800
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.ac.CommonRolesCache.size=33000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.ac.ExternalOIDCache.lifetime=-1
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.ac.OwnedResourcesCache.enabled=FALSE
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.ac.PermissionCollectionCache.lifetime=-1
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.ac.ProtectedResourceCache.lifetime=14400
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.datastore.services.Identification.SerializedOidString.cache.size=5000
########
# This cache uses more memory per object than other caches.
# The value should be set based on the number of concurrent, logged
in users. Larger values may require a larger JVM heap size.
# A value of 6,000 was used to support 6,000 virtual users in the
benchmark measurements.
# Increasing to 7,000 in other measurements increased throughput
but required a heap size of 4,608 MB.#
#########
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.model.factory.UserSpecificModelCache.size=6000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.pe.portletentity.lifetime=28800
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.pe.portletentity.size=45000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.policy.services.PolicyCacheManager.lifetime=43200
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.puma.CommonPrincipalCache.size=30000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.puma.DN_OID_Cache.size=30000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.puma.OID_DN_Cache.size=5000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.resolver.data.cache.DataSourceCache.size=8000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.resolver.data.cache.FirstLevelDataSourceCache.size=2003
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.services.vpmapping.HostnameToVirtualPortalIDCache.lifetime=-1
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.spa.parser.locale.FirstLevelLocalizationParserCache.size=1009
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.spa.parser.skin.FirstLevelSkinParserCache.size=1009
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.spa.parser.theme.FirstLevelThemeParserCache.size=2003
# Description = Portal/WCM initial tuning
cacheinstance.com.lotus.cs.services.UserEnvironment.size=4500
# Description = Portal/WCM initial tuning
cacheinstance.DigestCache.cache.size=45000
# Description = Portal/WCM initial tuning
cacheinstance.com.ibm.wps.resolver.resource.AbstractRequestDispatcherFactory.size=200
WP CommonComponentConfigService
# Description = Portal/WCM initial tuning
cc.multipart.enabled=false
# Description = Portal/WCM initial tuning
cc.multipart.correlatehosts=false
WP ConfigService
# Description = Portal/WCM initial tuning
cache.dynamic.content.spot=false
# Description = Portal/WCM initial tuning
resourceaggregation.cache.markup=true
# Description = Portal/WCM initial tuning
resourceaggregation.enableRuntimePortletCapabilitiesFilter=false
WP CPConfigService
# Description = Portal/WCM initial tuning
com.ibm.wps.cp.tagging.isTaggingEnabled=false
# Description = Portal/WCM initial tuning
com.ibm.wps.cp.rating.isRatingEnabled=false
WP NavigatorService
# Description = Portal/WCM initial tuning
public.expires=3600
# Description = Portal/WCM initial tuning
public.reload=3600
# Description = Portal/WCM initial tuning
remote.cache.expiration=28800
WP RegistryService
# Description = Portal/WCM initial tuning
default.interval=28800
# Description = Portal/WCM initial tuning
bucket.transformationapplication.interval=28800
# Description = Portal/WCM initial tuning
bucket.transformation.interval=28800
For Websphere Portal 8+ and WCM Rendering Only
### Do these only if in a WCM rendering environment only
# Description = Portal/WCM initial tuning
global.toolbar.enabled=false
# Description = Portal/WCM initial tuning
default.toolbar.enabled=false
WCM WCMConfigService
# Description = Portal/WCM initial tuning
deployment.subscriberOnly=true
# Description = Portal/WCM initial tuning
connect.moduleconfig.ajpe.contentcache.defaultcontentcache=SECURED
# Description = Portal/WCM initial tuning
connect.moduleconfig.ajpe.contentcache.contentcacheexpires=REL 2H
# Description = Portal/WCM initial tuning
user.cache.enable=true
For Authoring Only
WP AccessControlDataManagementService
# Description = Portal/WCM initial tuning for Authoring
environments
accessControlDataManagement.acucIgnoreResourceTypes=null
# Description = Portal/WCM initial tuning Authoring environments
accessControlDataManagement.loadRolesParentBased=true</ResourceEnvironmentProviderName></value>