Use this page to assign application module request types to work classes. This step defines Hypertext Transfer Protocols (HTTPs), enterprise beans, Web services, or buses to the work class, which are used by the on demand router to prioritize service policies. Supported requests include HTTP, Internet InterORB Protocol (IIOP), SOAP, and Java Message Service (JMS). Only HTTP workclasses are supported for middleware applications.
To view this page, click
.The name field cannot contain the following characters: # \ / , : ; " * ? < > | = + & % ' The name that is defined must be unique among work classes.
Use the membership field to add application modules to the work class. Associations are not limited to any one module. With this common grouping, you can assemble all work categories into a work class to ensure that the work class receives the priority that is designated by the service policy. Fields vary slightly, depending on the request type that is used.
A summary of actions displays the changes for the work class creation.
Click Finish to create the work class.
Opens the rule panel where you can create a rule. Select an existing rule to edit, or create a new rule.
The following attributes are viewable for the given request type:
Attribute | Description |
---|---|
Condition | Add a condition, or use the Build sub-expression utility to help you create a condition. Or, click an existing rule condition to change it. For example, if your rule uses an operand of userid set to Fred, your rule condition displays as uid = 'Fred'. |
Select Action | Select from the following options:
|
Deletes an existing, selected rule.
Prioritizes the rules in the case of multiple rules. The order of rules is key in determining matches. If a match occurs on the first rule, subsequent rules are not pursued.