Set the autonomic request flow manager in manual mode and specify
the various settings. Let the autonomic request flow manager estimate speed
factors based only on observations from an on demand router (ODR). In
manual mode, you must supply seat counts, or concurrency allocations, for
each combination of ODR, deployment target, and service class. The dequeuing
weights and gateway concurrency limits are derived from this information.
To allocate a certain number of seats to each combination of ODR,
deployment target, and service class, use the ProfileRoot/properties/arfm/manual/cell_name.xml file. In WebSphere Extended Deployment Version 5.1, the file was was_root/properties/arfm/manual/cell_name/node_group_name.xml. Use this file on the
machine where the autonomic request flow manager (ARFM) controller is running. With WebSphere Extended Deployment Version 6.0, the ARFM
controller runs on one of the machines that has the ODR. With
WebSphere Extended Deployment Version 6.0.1 and later, the ARFM controller
can run on the node agent or an ODR.
The manual/ directory
contains an example file that describes the format. See Configuring the autonomic request flow manager
for more information.