Intelligent Management: autonomic request flow manager advanced custom properties

Intelligent Management: autonomic request flow manager advanced custom properties

We can use these properties to configure the autonomic request flow manager (ARFM).
All ARFM custom properties are case sensitive.

Work profiler properties

Work profiler is a highly available controller; it can be active on a nodeagent, deployment manager or on a demand router. To disable it from becoming active on an on demand router (ODR), set the disableODRBasedWorkProfiler cell custom property to true. A cell restart is required for this custom property to take effect.

profilerPeriod

Number of milliseconds, specified for each cell that specifies the length of the work profiler cycle.

Value Description
Scope Cell
Valid values Integer value for number of milliseconds
Default 60000 (1 minute)

profilerHalfLife

Number of minutes, specified for each cell. The work profiler discounts observations by an exponential function of time. The half life is the amount of time over which the discount changes by a factor of 2.

Value Description
Scope Cell
Valid values Integer value for number of milliseconds
Default 600000 (10 minutes)

publishedAlphasPrintFrequency

Frequency at which work factors are printed to the SystemOut.log file. These work factors are printed to the log file during the work profiler cycle, which is a length of time specified with the profilerPeriod custom property. The work profiler to print work factors to the log file during each of these cycles, then we can specify the value as 1. However, to decrease the amount of text being printed to the log file, we can increase this value. For example, if we want the work factors to be printed after every 5 work profiler cycles, then we can specify the value as 5.

Value Description
Scope Cell
Valid values Integer value greater than or equal to zero
Default 0 (Work factors are not printed to the SystemOut.log file.)

Work profiler output decay half life and smoothing weight function parameters

The work profiler works in two passes: first it fits the observations to a simple model to extract preliminary work factors, then it smooths the work factors by taking a weighted average. Each weight is the product of two factors, one of which diminishes the preliminary work factor importance with age and the other that varies with the goodness of the first pass fit. The age factor is an exponential decay; the half-life is the amount of time over which that factor drops by a factor of 2. This parameter is given in the cell with the profilerAlphaSmoothingHalfLife custom property, with a value that is the decimal notation for an integer, a number of milliseconds. The default is 10 minutes. To adjust the goodness level, two parameters are used, a threshold and a factor. The threshold is defined with the goodnessWeightThresholdcell custom property. The factor is given in the cell with the goodnessWeightFactor custom property.

Property name Value Default
profilerAlphaSmoothingHalfLife a decimal notation for an integer in a number of milliseconds 600000 (10 minutes)
goodnessWeightThreshold a non-negative floating point number 20
goodnessWeightFactor a non-negative floating point number 20

Work factor overrides

We can override the values that are computed by the work profiler. The work profiler computes a work factor for each transaction class and deployed Java EE module pair (TCM). The work factor is a floating point number that represents the number of megacycles of the reference instruction set.
We can override work factors by adding the custom property to the dynamic cluster.
Use the following grammar for defining work factor override specifications:
spec ::= case ( "," case )*
case ::= pattern "=" value pattern ::= service-class ":" txn-class ":" application ":" module service-class ::= step txn-class ::= step application ::= step module ::= step step ::= name | "*"
value ::= number | "none"
Examples are provided in the following table:

Example Spec Description

*:*:*:* = none

Specifies that every transaction class module (TCM) in the deployment target has no override. The deployment target has only one tier, and the value is calculated in the normal way for each case.

*:*:*:* = 42

The deployment target has one tier. Every TCM in the deployment target has a work factor override for the tier, equal to 42 megacycles per request.

Platinum:*:*:* = 42, *:*:*:* = none

The deployment target has one tier. There is an override of 42 megacycles per request for transaction class modules that have a Platinum service class, and no overrides for transaction class modules assigned to any other service class in the deployment target.

*:tc_A:*:*=42, *:tc_B:AccountManagement:MicroWebApp.war=17, *:tc_B:*:*=none

There is an override of 42 megacycles per request for TCMs that have the tc_A transaction class. For any TCMs that have the tc_B transaction class, a deployed Java EEapplication named AccountManagement, and a Java EE module named MicroWebApp.war, there is an override of 17 megacycles per request. There is no override for any other TCMs that have the tc_B transaction class. This example does not consider transaction classes other than the tc_A or tc_B transaction classes and if it encounters another transaction class, an error message is displayed.

*:*:*:* = none, *:*:*:*:../DbCel/CICS = 0.7

There is no override for the first tier. For the tier that is named CICS+1, a work factor override of 0.7 exists. The CICS+1 tier is the first tier in the CICS deployment target, in the DbCel cell, regardless of the target TCM. The transaction class does not change from tier to tier, but the module might change.

Use per-process CPU readings

Set the useProcessCPU custom property to true to enable the ARFM controller and application placement controller to consider background work when computing the required resources and enable per-process CPU utilization statistics. When false, the work profiler cannot estimate work factors as well because it uses CPU utilization readings for the whole node.
If we configure this property a cell restart is required.

Name Property Setting Default Valid Values
useProcessCPU Set this custom property on the cell. true true or false

MustGather documents

Use the Intelligent Management mustGather documents to troubleshoot the autonomic request flow manager and application placement. For more information, read about the mustGather support documents for each version of Intelligent Management.

Related tasks

Configure the autonomic request flow manager

Related information:

mustGather documents

Value	Description
Scope	Cell
Valid values	Integer value for number of milliseconds
Default	60000 (1 minute)

Property name	Value	Default
profilerAlphaSmoothingHalfLife	a decimal notation for an integer in a number of milliseconds	600000 (10 minutes)
goodnessWeightThreshold	a non-negative floating point number	20
goodnessWeightFactor	a non-negative floating point number	20

Example Spec	Description
::: = none	Specifies that every transaction class module (TCM) in the deployment target has no override. The deployment target has only one tier, and the value is calculated in the normal way for each case.
::: = 42	The deployment target has one tier. Every TCM in the deployment target has a work factor override for the tier, equal to 42 megacycles per request.
Platinum:::* = 42, ::: = none	The deployment target has one tier. There is an override of 42 megacycles per request for transaction class modules that have a Platinum service class, and no overrides for transaction class modules assigned to any other service class in the deployment target.
:tc_A::=42, :tc_B:AccountManagement:MicroWebApp.war=17, :tc_B::*=none	There is an override of 42 megacycles per request for TCMs that have the tc_A transaction class. For any TCMs that have the tc_B transaction class, a deployed Java EEapplication named AccountManagement, and a Java EE module named MicroWebApp.war, there is an override of 17 megacycles per request. There is no override for any other TCMs that have the tc_B transaction class. This example does not consider transaction classes other than the tc_A or tc_B transaction classes and if it encounters another transaction class, an error message is displayed.
::: = none, ::::../DbCel/CICS = 0.7	There is no override for the first tier. For the tier that is named CICS+1, a work factor override of 0.7 exists. The CICS+1 tier is the first tier in the CICS deployment target, in the DbCel cell, regardless of the target TCM. The transaction class does not change from tier to tier, but the module might change.