Job classification in Compute Grid

The classification rules are composed of boolean expressions comprised of the operands listed in this article.

Classification rules are saved in a configuration file named gridclassrules.xml under the configuration directory of WebSphere Application Server. In WebSphere Extended Deployment V6.1, there is one gridclassrules.xml per cell, and the rules are ordered based on the priority element.

The runtime implementation of this feature iterates through these rules until it finds a matching rule. Once a match is found, the transaction class corresponding to that rule is applied to that job.

The following operands comprise the boolean expressions in job classification rules:

Sample classification rules

<matchRules xmi:id="MatchRule_1159377240783" matchAction=SimpleCI_TC" matchExpression="apptype='j2ee'"
priority="1"/>
<matchRules xmi:id="MatchRule_1159377240783" matchAction="CompletionTime_TC"
matchExpression="appname='MandlebrotCI" priority="2"/>
<matchRules xmi:id="MatchRule_1159377240783" matchAction="${default_iiop_transaction_class}"
matchExpression="submitterid='admin'" priority="3"/>

Default classification rules and precedence

WebSphere Extended Deployment Version 6.1 provides two default classification rules:

  1. A rule that assigns any job of type Java 2 Platform Enterprise Edition (J2EE) to the transaction class defined by the named J2EE application's default IIOP work class.
  2. A rule that assigns any job to the default transaction class, DEFAULT_TC

Both default rules can be edited and deleted. The order of the rules can be modified, and user-defined classification can be added. The job scheduler evaluates the list of classification rules in order and assigns the transaction class specified by the first matching rule. WebSphere Extended Deployment Version 6.1 only one classification rule set per cell is supported. A default configurable transaction class, named DEFAULT_TC by default, is associated with this set. If none of the classifications rules match a job, then the default transaction class is applied to that job. Graphical user interface (GUI) support for choosing a transaction class from a list while building a rule is only present in the presence of Operations Optimization package. In a Compute Grid only environment there is a text field where a transaction class name is specified.