Use this task to override the values that are computed by the work profiler.
When using explicit transaction classes like in WebSphere Extended Deployment Version 5.1, each TCM is stored in the file that defines the service class to which it belongs. A service class is defined by a profile/config/cells/cell name/serviceclasses/service class name/serviceclass.xml file. In this file, each <TransactionClassModules> element defines a single TCM, and you can attach a workFactor attribute to override the work profiler calculations for that TCM.
When you are using work classes, an XML element does not exist for each TCM. In this case, the work factor overrides related to a given deployment target (cluster, or unclustered server) can be specified in a custom property that is attached to that deployment target.
Use the workFactorOverrideSpec custom property. The value for this custom property is a string that contains a set of matching rules, or cases, that define the work factor override, either a value or none, for every TCM of that deployment target. The syntax of that string is the same as the syntax of the speed factor overrides, except that you cannot specify a tier for a work factor override case. See Configuring speed factors in multiple tier configurations for more information about speed factors. A work factor is in units of millions of CPU clock cycles on a standard kind of machine, and describes the average amount of work that must be done on the managed tier for a single request of that TCM.