You can use either default work classes that are created during a system application installation or define your own. Default work classes and directories for system applications are created during profile augmentation to support the high availability deployment manager. Default and new application work classes are defined on a per application edition basis.
Each default work class has membership that is equivalent to a wildcard expression for all the work of that protocol type for that application. This work class is matched to last, with any new user defined work classes taking precedence. Default work classes cannot have their membership altered manually nor can they be deleted. They are meant to define how any work directed toward the application that does not get classified into any user-defined work classes into a service policy definition. While the membership cannot be deleted, classification rules can be defined on the default work class. This is especially useful if the environment does not need to classify based on work class membership, but does need to classify on some advanced criteria such as group identification or host name.
The default matchAction on the default work classes for the application is to classify to the default transaction class of the default service policy. This can be changed to select an alternate transaction class/service policy pair.
Routing and service policies for work classes are not supported for IIOP or JMS for applications deployed to z/OS® platforms. WebSphere® Application Server z/OS provides IIOP and JMS service classification.
<context> <context-name>applications</context-name> <child-context-names> <child-context-name>deployments</child-context-name> <child-context-name>workclasses</child-context-name> </child-context-names> </context> <context> <context-name>deployments</context-name> <child-context-names> <child-context-name>workclasses</child-context-name> </child-context-names> </context> <context> <context-name>workclasses</context-name> <root-document-type>WorkClass</root-document-type> <child-document-names> <child-document-name>WorkClass</child-document-name> </child-document-names> </context>
cells/<cellName>/xd/systemApps/<earName>/workclasses/<workclass>/ cells/<cellName>/xd/systemApps/<earName>/xddeployments/<appName>/workclasses/<workclass>/
cells/<cellName>/nodes/<nodeName>/systemapps.xml
<context> <context-name>middlewareapps</context-name> <child-context-names> <child-context-name>middlewareappeditions</child-context-name> <child-context-name>workclasses</child-context-name> <child-context-name>preferences</child-context-name> </child-context-names> </context> <context> <context-name>middlewareappeditions</context-name> <child-context-names> <child-context-name>workclasses</child-context-name> </child-context-names> </context>
cells/<cellName>/nodes/<nodeName>/systemapps.xml