WebSphere Extended Deployment V6.0.x     操作系统: AIX, HP-UX, Linux, Solaris, Windows, z/OS

Work classes

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 new applications.

Default application work classes

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.

New application work classes

Work classes for service policies are defined on a per application edition basis. Each edition of the application has its own definitions on how it should be classified into service policies. After the on demand router (ODR) determines which application edition should be routed to, its service policy work class definitions are evaluated to determine how its work should be classified. When a new edition of an application is installed, you can choose an edition of the application to clone or choose none at all. If an edition is chosen, all of its work classes are cloned with the defaults appropriately renamed with the new application edition name. If no edition is chosen, only the defaults are created.

Configuration placement location

The configuration placement location for work classes for applications is:
<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>

System application work classes

Default work classes and directories for system applications, such as the adminconsole.ear, are created during profile augmentation to support the high availability deployment manager. An xd directory under the cell context mimics the systemApps structure and contains the default work classes. The default work classes are created under the following contexts:
cells/<cellName>/xd/systemApps/<earName>/workclasses/<workclass>/

cells/<cellName>/xd/systemApps/<earName>/xddeployments/<appName>/workclasses/<workclass>/
Extended Deployment listens for changes to the systemapps.xml file under the node context for any updates:
cells/<cellName>/nodes/<nodeName>/systemapps.xml



相關概念
The high availability deployment manager
相關參考
Routing policies for work classes
概念主题    

使用条款 | 反馈

最近更新日期: Aug 14, 2006 2:00:44 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/codoeworkclass.html

© Copyright IBM Corp. 2006. All Rights Reserved.
本信息中心基于 Eclipse 技术。(http://www.eclipse.org)