Use this task to compute and configure work factors for your multiple tier configuration.
A work factor exists for every combination of transaction class, target Web module, and processing tier. The work factor describes how heavily a request of the given transaction class loads the processing tier. You can define work factors at varying levels of granularity. The autonomic request flow manager (ARFM) uses work factors at the level of service class, target deployment target, and processing tier. You can define work factors at a variety of levels for any processing tier that is not a target tier or is not the one and only processing tier in the target module.
In a configuration that has multiple tiers, the work profiler automatically computes work factors for the target tier, which communicates directly with the on demand router (ODR). For any tiers that are deeper than the target tier, you must define work factors. If your deployment target contains both a target tier and a non-target tier, you must configure the work factors for both tiers because the work profiler cannot automatically compute work factors in that situation. You can compute the work factor by dividing average processor utilization by the average number of executing requests per second. This task describes how to find these values and configure the work factor for your multiple tier configuration.