WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

work, processed by the system is charged into one reporting class. The decision
of what work should be put into which report class can be defined by the z/OS
system programmer (system administrator).
This grouping of used resources can then be used to tune the system or to
create a charge-back to the departments using the systems. To create reports,
the Resource Measurement Facility (RMF) is used.
Enclaves in an WebSphere Application Server for z/OS environment
An enclave is used to assign the user application a service class during runtime.
An enclave can be thought of as a container that has a service class and
reporting class attached to it. A thread can connect to this enclave and execute
the thread’s work with the priority of the enclave.
WebSphere Application Sever for z/OS uses this technique to pass transactional
work, the user application, from a servant to an enclave. The application then
runs with the priority of the enclave and WLM can make sure that the
performance goals for the application are achieved.
Workload classification
WebSphere Application Server for z/OS V7.0 and its prior versions are capable
of classifying incoming work on a server base. To do this, the control region of an
application server checks to which application server the request belongs. It will
then assign the request to a WLM queue. Each servant will process work for one
service class at any point in time.
As seen in Figure 14-4, incoming work is assigned a service class, based on
information of the user- work request. The granularity is on the application server
level.
Work Request
Known information from request:
Subsystem Type...CB (WebSphere)
USERID................BBOSRV
TransactionClass..TCFAST
Classification Rules
Subsystem Type=CB
Userid=BBOSRV
Service Class
BBOFAST
Figure 14-4 Workload classification for WebSphere Application Server for z/OS
Service Class=BBOFAST
Reporting Class = WASAPPL01
Chapter 14. WebSphere Application Server for z/OS 429