analytics/webapps/p2pd/WEB-INF/p2pd_deploy_defaults.properties

# Licensed Materials - Property of IBM
# IBM Cognos Products: disp
# (C) Copyright IBM Corp. 2005 2014
# US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

# 
# This file contains INTERNAL dispatcher properties. 
# 

# Default deployment values.  These provide settings that should 
# work out of the box, provided win32\bin (or bind) is the current
# working directory when tomcat is launched.

# This is used to find binaries, warpserver.exe (defaults to baltic/bin)
dispatcher.bin=../bin
dispatcher.bin64=../bin64
dispatcher.epbin=../bin

# Dispatcher host name
# dispatcher.host=localhost

# tell p2pd what port the dispatcher (tomcat) listens on
# dispatcher.port=8080

# tell p2pd which servlet context it is work from
# dispatcher.url=/p2pd/servlet/dispatch

# Dispatcher Capacity for load balancing
dispatcher.capacity=1.0

# Content Manager Connection Pool size
dispatcher.cm_poolsize=10

# Dispatcher internal temp directory
dispatcher.temp=../temp

# Content Manager Host Name
#cm.host=localhost

# Content Manager Port Number
#cm.port=8080

# Password Encryption
dispatcher.encryption=disabled

# Content Manager URI
#cm.url=/CM/servlet

# Size of the request cache of the report server (default = 10)
wp_cache_size=10

# Lifespan in seconds of non-busy requests in the report server cache (default = 300)
wp_idle_request_lifespan=300

# Filename for Cognos.wsdl
wsdl.name=/Cognos.wsdl

# this can be used to override the port that use to connect to CM,
# overriding the value from the CM URI in crnstartup.xml.  This is
# provided to make it easy/possible to use tcpmon to watch traffic 
# with CM.  When CM is in on the same machine the config tool is 
# very uncooperative in letting you change the port in the URI.
# cm.port.override=19300

# interval between checks for updates to PogoLogkitConfig.xml, in ms 0 means never
loggingConfigUpdateCheckInterval=30000

# time in ms the dispatcher will timeout idle connection pool connections
dispatcher.connection_timeout=25000

# The default socket timeout used for server connections in the dispatcher.
# A value of -1 indicates the default HttpClient timeout will be used (the actual timeout value is platform-specific).
# A value of 0 indicates an infinite timeout will be used (not recommended).
# Any other value must be positive and specified in milliseconds.
dispatcher.socket_timeout=-1

# timeout for how long dispatcher will wait for getActiveCM requests
ActiveCMFinderTimeout=30000

# true to enable pooling of SAXReaders
SAXReaderPool.enabled=true
# SAXreaders are created as required (no limit), but only "numSticky" are kept around.  The rest are 
# pooled via SoftReferences that allow them to be garbage collected.
SAXReaderPool.numSticky=10

# Where the MBean dump config file is 
mbeandump.filename=metricdumpconfiguration.xml

# How often to check to see if the MBeanDump configuration has changed
mbeandump.checkInterval=30000

# uncomment the following line if using WebSphere 5.1.  This will stop IBM Cognos from using the JMX libraries
#noJMX=true
# domain for JMX server: IMPORTANT: Not ready to be used yet; 
#JMX.domain = domain 

MIMEParseBoundaryFix=true

#Note: If you have any spaces in your install dir, start JConsole as follows: Jconsole -J-Djava.rmi.server.useCodebaseOnly=true
#Uncomment the next line to enable the JMX RMI Registry if not already set in configuration
#rmiregistryport=9700
#Uncomment the next line to specify the port number for JMX Server - default is to use a random free port
#jmxServerPort=9701

# The default amount of time the dispatcher will wait for an expired process to become idle.
# After this wait, expired processes will be considered run-away processes and will be destroyed.
# This value can be overridden on a per-service basis by specifying the parameter
# "max_wait_for_expired_process_to_become_idle_secs" in the service XML file.
# See services/reportservice.xml for an example.
# Note: 86,400 secs = 1 day
dispatcher.DefaultMaxWaitForExpiredProcessToBecomeIdleInSecs=86400

# The "<serviceName>.inProgressRequestFactor" property affects the load balancing algorithm for that service.  
# The value is a multiplier that controls the contribution to the error calculation for each dispatcher 
# that is a possible target for a request of the number of in-progress requests we have on that dispatcher.  
# An in-progress request is one that we have sent to another dispatcher from this one, but have not 
# received a response for.
#
# When forwarding requests to other dispatchers, we choose the one that minimizes the total error value.  The 
# error is calculated from the difference between the actual round robin proportions versus the desired 
# proportions, and from the number of in progress requests.  It is summed for all target dispatchers.
#
# A value of 0.0 results in the original weighted round robin algorithm.
# A recommended starting value is 2.0
#
# Syntax:
#    <serviceName>.inProgressRequestFactor=<value>
#    Where <serviceName> is the name of the service, or "default" for all services.
#    Example: powerPlayService.inProgressRequestFactor=0.5
#
default.inProgressRequestFactor=2.0

# When use IIS7, by default if the path_info is empty, then instead of returning that, it returns the complete script name and this 
# cause issues with Portal. 
# 
# We'll need check this situation and set the path info back to empty. This checking is on by default, you can disable it by setting the property 
# 'pathInfoChecking.enabled' to false. 
#
pathInfoChecking.enabled=true

# The following property addresses incompatibility issues with the cookie parsing algorithm implemented in Tomcat 6. 
# When set to true, it enables a custom cookie decoder that properly handles scenarios like the following:
#
# - SiteMinder SMSESSION cookies, which uses base64 encoded values containing equal signs
# - Series7 AS_TICKET cookies, which uses semicolons to separate multiple ticket servers, affecting SSO between C8 and S7.
# - JMeter scripts that automatically convert v1 cookies to unquoted v0 cookies.
#
# The default value is true (enabled).
#
CustomCookieDecoder.enabled=true

#when this property is defined and set to true, the method addHeader is used to populate the set-Cookie header
#in the http response; otherwise the webcontainer version of addCookie is used.  
#CustomCookieEncoder.allCookies=true

#This property defines the list of cookies for which the addHeader method is used instead of addCookie
#This is a comma separated list of names (surrounding spaces are trimmed when this property is read)
#It is ignored when CustomCookieEncoder.allCookies is set to true
#CustomCookieEncoder.cookieList=cookie1,cookie2
CustomCookieEncoder.cookieList=AS_TICKET

# This property enables a more efficient way of sending Mime attachments. Older application servers, like
# Tomcat 4.0.1 (no longer supported) , may have an issue where they may not handle the end of a chunked 
# stream properly when this fast method is enabled, causing a 60-second timeout. Setting this property
# to false will resolve the issue. The default value is true (enabled).
MimeParseInputStream.FastStreamRead.enabled=true

# This property enables copying the input stream to memory when dealing with Multipart attachments
# This can help with input streams being closed prematurely
MimeParseInputStream.CopyStream.enabled=true

# This property defines the buffer size used while streaming Mime and SOAP attachments
MimeParseInputStream.ResponseBufferSize=32768

# WAS can send a "expect: 100-continue" header for every HTTP 1.1 post.
# Since we pass through the HTTP headers, this can cause the HTTP client 
# used by dispatcher to set the socket timeout to 3 seconds, 
# so it can wait for a 100-continue response.  However, lower layer Cognos
# services don't support the 100-continue header, and so the request is delayed by this timeout.
# By default expect100Continue is set to false and the "expect: 100-continue" header will be
# removed from the post request before it reaches HTTP client.
# When it's set to true, the header will be kept in the post request header.

# expect100Continue=true

# time in ms the dispatcher will timeout (wait for a response) a "ping" request to the BiBus
# dispatcher.noop_timeout=60000

# How often external processes are checked to see if they are still running.
# Commenting out this property will disable this checking 
processCheckInterval=300000

# Set this to true, and all requests will be bridged (if appropriate)
# in addition, the BridgeRequestHandler and BridgeResponseHandler will no longer bridge requests
# default is false
# enableAutomaticBridging=true