Configuring Intelligent Management properties for web servers

Define and configure the Intelligent Management properties to modify the Intelligent Management capabilities of the web server.

About this task

After you enable Intelligent Management, you can specify new properties to configure or modify the Intelligent Management capabilities of your web server. The new properties display in the generated plugin-cfg.xml configuration file under the IntelligentManagement element. These values are dynamically available to the web server without generating and propagating the plugin-cfg.xml file, unless noted otherwise.

The following advanced custom properties are provided with sensible defaults. Modify these properties only with care or at the direction of IBM® Technical Support.

Table 1. Advanced custom properties

Name	Value	Description
DefaultRequestTraceSpec	Any valid trace specification. For example: http.request:DEBUG Default value: NOTICE	Use this custom property to trace individual requests, if none of the per-request conditional trace rules matches those requests. If this custom property is set, every request that does not match a trace rule condition is traced with this specification. If this custom property is not set, the requests are traced based on the overall control or HTTP specification. For more information about the trace setting hierarchy, read about configuring trace on the web server plug-in.
MaxElapsedTimePerRequestInSeconds	Seconds Default value: There is no time limit	Use this custom property to specify the amount of time in seconds Intelligent Management will try to find an end point for a request once it arrives. After this specified time, it will stop finding an end point and return.
MaxHttpContextPoolSize	Maximum number of HTTP request contexts to be pooled or cached. Default value: -1 (unlimited)	This property is the maximum number of HTTP request contexts, which are pooled or cached.  If the value is -1, there is no limit; otherwise, the pool size is limited.  When the number of concurrent requests for a single Apache process exceeds this limit, contexts are disposed off rather than returned to the pool. Large amounts of pooled HTTP requests limits the amount of memory that is used, and decreases performance during a burst of concurrent requests.
MaxSecondsToWaitDuringAtomicRollout	Seconds Default value: 3 seconds	This property is the maximum number of seconds that a single request can wait when it routs to an application during an atomic rollout.  By allowing a request to wait, it returns successfully rather than returning with a service not available error response (for example, HTTP 503 error code).
MaxTargetEndpointsPerRequest	Valid values are 1-n. Default value: 9999	This global property controls the number of endpoints that are returned per request. This property can be used to limit the number of retries per request, for any reason. In practice, the default limit is never reached because the list of candidate endpoints is exhausted first. To prevent all retries, specify a value of one. A value of one results in no retries after the initial endpoint is returned. A value of zero for this property stops traffic from the request because no endpoints are permitted to be returned.
Request503Retry	Valid values are 0-n. Default value: 9999	You can use this global property to limit the number of retries per request for HTTP 503 responses from backend servers.
AffinityOverAppEd	A Boolean property Default value: false	The default routing policy for selecting servers for an Application Edition request is for the Application Edition Routing Rules selection criteria to supersede session affinity. Setting this property to true causes the target selection to preserve session affinity.
OdrPortPathPrefix	A fully qualified file path	This property allows Intelligent Management to create a .pid file to the specified location, which might be needed if you encounter permission issues with the IBM HTTP Server or Apache processes.
RoutingRulesConnectorClusterName	This value is defined in the admin console at Web servers > webserver1 > Intelligent Management > Intelligent management plug-in properties.	The RoutingRulesConnectorClusterName attribute of the Property element supports routing rules. It is required for Intelligent Management enabled Web Server (IMWS) routing rule features, even in single cell environments. This attribute defines what cell or collective holds the routing rule configuration for IMWS. For more information, see Setting up routing rules.

• To define an Intelligent Management property, follow this procedure:
  1. In the administrative console, click Servers > Server types > Web servers > web_server_name > Intelligent Management > Intelligent Management plug-in properties, and click New.
  2. On the Intelligent Management properties configuration page, specify the plug-in properties.
     Enter an arbitrary name and value. The name is a property key. The value is a string value to be used for setting the internal system configuration properties. Click Apply, and your web server uses the new Intelligent Management property. Click OK to save your input.
• To modify an Intelligent Management property, follow this procedure:
  1. In the administrative console, click Servers > Server types > Web servers > web_server_name > Intelligent Management > Intelligent Management plug-in properties > intelligent_management_property_name.
  2. On the Intelligent Management properties configuration page, modify the plug-in properties.
     Click Apply, and your web server uses the modified Intelligent Management property.