- arfmIgnoreDialogsForCpu
You can set this custom property to true so
that the ARFM ignores the dialog structure for the purposes of CPU overload
protection. Every incoming message is subject to admission control.
| Valid values
| Boolean
|
| Default
| False
|
- arfmManualAllocation
You can specify this custom property on a deployment target to
put ARFM into manual mode when the custom property arfmMode is not set to
manual. The value of the property is a string in a syntax that allows expression
of allocations.
| Valid values
| String
|
| Default
| no default
|
- arfmMode
You can use this custom property to specify the operating mode
of the ARFM. In automatic mode, the ARFM has an autonomic controller that
adjusts the dispatching priority of requests from the on demand routers to
the servers and sends the placement controller information about the computational
needs for the various dynamic clusters. In manual mode, you can override the
autonomic controller with administrative settings.
| Valid values
| Manual, Automatic
|
| Default
| Automatic
|
- CPUAdjustment
You can set this custom property on nodes that are on hyperthreaded
computers. When the CPUAdjustment custom property is specified on a node,
a correction function to apply to processor utilization readings is specified
for that node. This function is applied to the processor utilization that
is reported by the operating system, and yields a more accurate utilization
measure.
| Valid values
| String
|
| Default
| no default
|
- goodServiceTimeLimitSpec
Specify the goodServiceTimeLimitSpec custom property to indicate
a value that is multiplied by the response time threshold to determine the
fine-grained timeout threshold. Use a goodServiceTimeLimitSpec custom property
when configuring the ARFM. The default value of one minute for determining
timeouts is used if goodServiceTimeLimitSpec or timeoutFactor is not set.
To override the default, set this custom property to customize the value
for different levels of granularity. For example, service class, application,
or module. To create a general rule of 5 minutes, create the custom property
and set the value to "*:*:*:*:*=300" where the last part is the timeout value
of 300 seconds. The timeout value is a decimal number, not necessarily a whole
number, and is in units of seconds.
| Valid values
| Decimal number in unit of seconds
|
| Default
| no default
|
- magicNMode
You can set this custom property when ARFM is in automatic mode.
When in automatic mode, concurrency limiting is performed according to one
of two criteria, depending if the magicNMode custom property is enabled. When
Magic N mode is enabled, the total number of requests that are running concurrently
at any given time is limited to a certain total. In normal mode, the total
number of requests depends on the use of processor power on the nodes.
| Valid values
| Boolean
|
| Default
| false
|
- magicN
You can use this custom property when ARFM is in Magic N Mode,
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 you are using the reasonable limit estimation, 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.
| Valid values
| 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.
|
| Default
| -1
|
- maxHttpLiveRequests
You can use this custom property to define the maximum number of
requests that are targeted for a particular cell, that might be anywhere in
the cell. That is, either queued in an ODR or running on an application server
at a given time.
| Valid values
| integer
|
| Default
| no default
|
- node.speed
You can use this property to define the node speed in MHz. Set
the value to the processor speed, multiplied by the number of processors on
a multi-processor node. Set this custom property on the node.
| Valid values
| A floating point number that represents the number of MHz of the
reference instruction set.
|
| Default
| no default
|
- node.memory
You can use this property to specify the available RAM defined
in megabyte units on a node. Set this custom property on the node. Although
this value is determined automatically, you can override the value.
| Valid values
| A number of megabytes
|
| Default
| no default
|
- node.numCPUs
You can use this custom property to specify the number of processors
on a multi-processor node. This value is automatically determined, but you
can override the value. Set this custom property on the node.
| Valid values
| Integer that represents the number of processors
|
| Default
| no default
|
- timeoutFactor
Specify the timeoutFactor custom property to indicate a value that
is multiplied by the response time threshold to determine the fine-grained
timeout threshold. 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.
This fine-grained timeout threshold is one of three different factors that
the ARFM uses to determine that a running request has timed out. The running
request has timed out when one of the following factors is true:
- The proxy framework indicates the request timed out.
- The request reply includes a special HTTP header that indicates that the
internal application timed out.
- The service time exceeds the fine-grained timeout value.
| Valid values
| Decimal representation of a floating point number
|
| Default
| no default
|
- useODRs
Specifies if the work profiler and placement controller rely on
the services of the ODR servers.
| Valid values
| Boolean
|
| Default
| true
|