Classifying z/OS workload
You can use a common workload classification document to classify inbound HTTP, IIOP, Session Initiation Protocol (SIP), optimized local adapter, and message-driven bean (MDB) work requests for the z/OS® workload manager.
Before you begin
About this task
A workload classification document file is an XML file in which you classify incoming HTTP, IIOP, Session Initiation Protocol (SIP), optimized local adapter, and message-driven bean (MDB) work requests and assign them to a transaction class (TCLASS). The TCLASS value, if it is assigned, is passed to the MVS™ Workload Manager. WLM uses the TCLASS value to classify the inbound work requests and to assign a service class or a report service class to each request.
The common workload classification document is the method you should use to classify work requests in a z/OS environment. Support for other WebSphere® Application Server mechanisms for classifying work in a z/OS environment is deprecated and you should no longer use those mechanisms.
If you want to classify work for message-driven beans deployed against
JCA 1.5 resources with the default messaging provider, or you want
to classify mediation work for use with service integration buses,
you need to define a Classification element that uses SibClassification
elements. You must also perform z/OS Workload Manager actions that are required to use the TCLASS
value SIBUS
. If you replace any listener port with a JMS activation
specification for use by MDB applications with the Version 6 default
messaging provider, you should replace any related InboundClassification
type="mdb" classifications with SibClassifications type="jmsra" classifications.
If you want to classify work
for message-driven beans deployed against a WebSphere MQ messaging provider activation
specification, you need to define a Classification element that uses
WMQRAClassification elements. You must also perform z/OS Workload Manager actions that are required
to use the TCLASS value WMQRA
. If you replace any listener
port with a JMS activation specification for use by MDB applications
with the WebSphere MQ
messaging provider, you should replace any related InboundClassification
type="mdb" classifications with WMQRAClassification classifications.