WLM classification

Classify HTTP traffic to improve workload distribution on z/OS®.

You can classify HTTP traffic in an IBM® z/OS Connect Server so z/OS workload management (WLM) manages it along with other work in the system by enabling the Liberty feature zosWlm-1.0. This identifies work by classification rules and pass that into z/OS WLM for mapping to service classes and reporting classes. Different URIs can have different priority and performance criteria. Classification of HTTP requests is based on host, port, method, and resource and is configured in the server configuration file.

A WLM enclave is associated with the thread that the request is dispatched on. It is also associated with a WLM Service Class. A WLM Service Class is assigned to the WLM enclave by WLM, based on rules that you define in the WLM configuration. The WLM Service Class indicates the WLM goals for each class of client work, for example, 95% complete in 1 second or less. The WLM Service Class also indicates the importance of the goals relative to other work on the system. WLM uses information that is provided by the Liberty server during classification to assign a WLM Service Class.

In a high availability environment, you can specify the same value on the WLM Native Enclave Manager Configuration element for all your servers. For example,

<zosWorkloadManager collectionName="<value>" />

This method allows the servers to use the same collection name in WLM, instead of the default collection name, which is the server name for each server.