Extended Deployment provides work classes for applications and for systems applications. When an application is installed, a default work class is created for each protocol discovered to be supported in the application. For example, if the application has only Web modules, a single default HTTP work class is created. If the application has one or more EJB modules, a single IIOP work class is created. Additionally if the application has one or more Web services modules, a single SOAP work class is created. A default JMS work class is always created for each application because it is possible to have a JMS resource without a resource reference in the application definition. You can also create work classes for applications.
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.
<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