Route requests to nodes that are not running Intelligent Management
Use this task for configuring multiple tiers.
Plan the topology.
To make the autonomic request flow manager aware of nodes that are not running Intelligent Management, use one of the following options to configure the node in the Intelligent Management configuration.
- The most common scenario is to install the node agent on each node running other middleware software. For more information about running middleware software, read about adding middleware servers to configurations .
- 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, read about autonomic request flow manager custom properties. Do not use this approach if the 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, we can manually configure speed factors for transaction class modules, which are a transaction class and web module pair. For more information about work and speed factors, read about configuring work factors in multiple tier configurations.
- 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, 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. The manual/ directory contains an example file that describes the format.
For more information about the manual/ directory, read about configuring the autonomic request flow manager.
Subtopics
- (dist)(zos) Route requests to external nodes with generic server clusters
Use this task to route requests from the on demand router (ODR) to external nodes.
- (dist)(zos) Multiple tiers of processing
The autonomic request flow manager (ARFM) can process requests in multiple tiers. The tiers might include both WebSphere Application Server software and other software.
- (dist)(zos) Configure work factors in multiple tier configurations
Use this task to compute and configure work factors for your multiple tier configuration.
Related tasks
Configure work factors in multiple tier configurations Route requests to external nodes with generic server clusters Add middleware servers to configurations Configure the autonomic request flow manager
Intelligent Management: autonomic request flow manager custom properties