Note that for the function Fast Response Cache Accelerator for high performance handling of cached static web pages, you must classify work as described in the following paragraph. Otherwise, it will be assigned the default service class for IWEB work.
The transactions handled by the Cache Accelerator are all joined to a single, long-lived enclave. This enclave should be assigned a unique transaction class (as specified on the Webserver FRCAWLMParms directive). This transaction class should then be assigned to a service class with a single period and a velocity goal in the service policy under the IWEB subsystem type. Neither response time goals nor multiple periods are appropriate for this work, as WLM is not aware of the individual Cache Accelerator requests. (Because each individual transaction is so trivial, it would cost more resource to manage them than to just process them.) In RMF™ reports, you will see zero ended transactions for the Cache Accelerator service class (assuming you have no other work running in this service class), but you will see some amount of accumulated service for this single enclave.