Use this task for configuring multiple tiers.
About this task
To make the autonomic request flow manager aware of nodes that are
not running WebSphere Extended Deployment, you must use one of the following
options to configure the node in the WebSphere Extended Deployment configuration.
Procedure
- The most common scenario is to install the
remote agent on each external node to give WebSphere Extended Deployment access
to CPU information about the node. See Routing requests to external nodes with generic server clusters
for
more information.
- Set the cell to run in Magic N mode. Magic N is the
total number of requests that can run concurrently on the node group. To configure
Magic N mode, specify the magicNMode and magicN custom properties. For more
information about these custom properties, see Autonomic request flow manager custom properties
.
Do not use this approach if your different service classes have very different
computational demands.
- Specify work factors or speed factors and the computing power of
each node. Speed factors are computed automatically by the work
profiler for target tiers. For external nodes, you can manually configure
speed factors for transaction class modules, which are a transaction class
and web module pair. See Configuring speed factors in multiple tier configurations
for more
information.
- Put the autonomic request flow manager in manual mode and specify
the various settings. In manual mode, you must supply seat counts,
or concurrency allocations, for each combination of on demand router (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.
- Let the autonomic request flow manager estimate speed factors based
only on observations from the ODR.