WebSphere 8.5

This page describes the Optimization Pack for the component type WebSphere 8.5.

Metrics

There are no metrics for this component type.

Parameters

InboudChannels

Parameter	Type	Unit	Default	Domain	Restart	Description
was_tcp_maxppenconnections_tcp2	integer	connections	20000	1 → 128000	yes	Maximum number of connections that are available for a server to use (TCP_2)
was_tcp_listenBacklog_tcp2	integer	connections	511	1 → 1024	yes	Maximum number of outstanding connection requests that the operating system can buffer while it waits for the application server to accept the connections (TCP_2)
was_tcp_maxppenconnections_tcp4	integer	connections	20000	1 → 128000	yes	Maximum number of connections that are available for a server to use (TCP_4)
was_tcp_listenBacklog_tcp4	integer	connections	511	1 → 1024	yes	Maximum number of outstanding connection requests that the operating system can buffer while it waits for the application server to accept the connections (TCP_4)
was_http_maximumPersistentRequests_http2	integer	requests	10000	1 → 20000	yes	Maximum number of persistent requests that are allowed on a single HTTP connection (HTTP_2)
was_http_maximumPersistentRequests_http4	integer	requests	10000	1 → 20000	yes	Maximum number of persistent requests that are allowed on a single HTTP connection (HTTP_4)

Thread Pools

Parameter	Type	Unit	Default	Domain	Restart	Description
was_threadpools_minimumSize_webcontainer	integer	threads	50	1 → 100	yes	Minimum number of threads to allow in the pool (Web Container)
was_threadpools_maximumsize_webcontainer	integer	threads	50	1 → 500	yes	Maximum number of threads to maintain in the thread pool (Web Container)
was_threadpools_minimumSize_default	integer	threads	20	1 → 100	yes	Maximum number of threads to maintain in the thread pool (Web Container)
was_threadpools_maximumsize_default	integer	threads	20	1 → 500	yes	Maximum number of threads to maintain in the default thread pool (default)
was_threadpools_minimumSize_threadpoolmanager_orb	integer	threads	10	1 → 100	yes	Minimum number of threads to allow in the pool (ThreadPoolManager ORB)
was_threadpools_maximumsize_threadpoolmanager_orb	integer	threads	50	1 → 500	yes	Maximum number of threads to maintain in the thread pool (ThreadPoolManager ORB)
was_threadpools_minimumSize_objectrequestbroker_orb	integer	threads	10	1 → 100	yes	Minimum number of threads to allow in the pool (ObjectRequestBroker ORB)
was_threadpools_maximumsize_objectrequestbroker_orb	integer	threads	50	1 → 500	yes	Maximum number of threads to maintain in the thread pool (ObjectRequestBroker ORB)
was_threadpools_minimumSize_custom_TCPChannel_DCS	integer		20	1 → 100	yes	Minimum number of threads to allow in the pool (TCPChannel.DCS)
was_threadpools_maximumsize_custom_TCPChannel_DCS	integer	threads	100	1 → 500	yes	Maximum number of threads to maintain in the thread pool (TCPChannel.DCS)

Timeouts

Parameter	Type	Unit	Default	Domain	Restart	Description
was_auth_cacheTimeout	integer	milliseconds	600	0 → 7200	yes	The time period at which the authenticated credential in the cache expires
was_webserverplugin_serverIOtimeout	integer	milliseconds	900	-1 → 1800	yes	How long should the plug-in wait for a response from the application

Others

Parameter	Type	Unit	Default	Domain	Restart	Description
was_Server_provisionComponents	categorical		false	true, false	yes	Select this property if you want the server components started as they are needed by an application that is running on this server
was_ObjectRequestBroker_noLocalCopies	categorical		false	true, false	yes	Specifies how the ORB passes parameters. If enabled, the ORB passes parameters by reference instead of by value, to avoid making an object copy. If disabled, a copy of the parameter passes rather than the parameter object itself.
was_PMIService_statisticSet	categorical		basic	true, false	yes	When PMI service is enabled, the monitoring of individual components can be enabled or disabled dynamically. PMI provides four predefined statistic sets that can be used to enable a set of statistics