You can use the following custom properties to change the behavior of the autonomic request flow manager (ARFM).
Name | Description | Default | Valid values |
---|---|---|---|
arfmMode | Specifies the operating mode of the autonomic request flow manager (ARFM). In automatic mode, the ARFM has an autonomic controller that adjust the dispatching priority of requests from the on demand routers to the application servers and sends the placement controller information on the computational needs for the various dynamic clusters. In manual mode, you can override the autonomic controller with administrative settings. | Automatic | Manual , Automatic |
magicNMode | When ARFM is in automatic mode for a given node group, the concurrency limiting is done according to one of two criteria, depending if the ARFM for the node group is in "Magic N mode". When Magic N mode is enabled, the total number of requests that are running concurrently on the node group at any given time is limited to a certain total. In normal mode, the total number of requests depends on the usage of CPU power on the nodes. | false | true, false |
magicN | When ARFM is in Magic N Mode for a given node group,
use this property to the limit on the total number of concurrent requests.
If this property is not defined, a reasonable limit is estimated from other
data. If using the reasonable limit, the limit on the total number of concurrent requests for a cell is the sum of a contribution from each node in the cell. The contribution from a node is the average, over the running application servers on that node, of the maximum size of the thread pool of the Web container on that application server. |
-1 | A positive integer defines the number of concurrent requests. To use the reasonable estimate, set the property value to a negative number or delete the custom property. |
maxHttpLiveRequests | Use this property to define the maximum number of requests targeted for a particular cell, that might be anywhere in WebSphere Extended Deployment. That is, either queued in an ODR or executing on an application server at a given time. | none | integer |
node.speed | Use this property to define the node speed in MHz. The processor speed, multiplied by the number of processors on a multi-processor node. Set this custom property on the node. | none | A floating point number that represents the number of MHz of the reference instruction set. |
node.memory | The available RAM defined in MB units. Set this custom property on the node. Although this value is determined automatically, you can override the value. | none | A number of megabytes. |
node.numCPUs | The number of processors on a multi-processor node. This value is automatically determined, but you can override the value. | none | Integer number that represents the number of processors. |
timeoutFactor | The ARFM deems a request execution to have timed out if the proxy framework indicates it did, the reply includes a special HTTP header that indicates internal application timeout, or the service time exceeds a fine-grained timeout value. Use a timeoutFactor custom property when configuring the ARFM. The timeoutFactor value is multiplied by the response time threshold to yield the fine-grained timeout threshold. | none | Decimal representation of a floating-point number |
useODRs | Specifies if the work profiler and placement controller rely on the services of the ODR servers. | true | true or false |