Define work class memberships and rules

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).

To view this page, click Applications > Application types > WebSphere enterprise applications > application_name > Service policies or Routing policies > request_type.

Note: If you need to access the Generic server cluster policies, click Servers > Server types > On demand routers > odr_name > On demand router properties. Click either Generic server cluster routing policies or Generic server cluster service policies.

To modify rules with the subexpression builder, you must have administrator privileges.

Step 1: Define work class general properties

Name: Specifies a name for the work class.
The name field cannot contain the following characters: # \ / , : ; " * ? < > | = + & % ' The name that is defined must be unique among work classes.

Step 2: Define work class memberships

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.

Attention: The step only exists for application work classes. If you are using generic server work classes, you do not perform this step.

Module

Select the appropriate module from the list. For JMS work classes, if you select an enterprise bean jar file from the module list, a new menu displays from which you can select an enterprise bean name.

EJB

Use with IIOP requests. Select the appropriate enterprise bean from the list. The resulting enterprise bean displays in the Available list. Use the filter option to see a filtered list of enterprise bean methods that are specific to the selected enterprise bean.

Web service

For use with SOAP requests. Select the appropriate Web service from the list. The resulting Web service displays in the Available list.

Bus

For use with JMS requests. Select the appropriate Bus from the list. The resulting bus displays in the Available list. Use the filter option to see a filtered list of Bus methods that are specific to the selected Bus.

Available

Select the appropriate HTTP, EJB, Web service or bus destination from the available list. Select multiple destinations by holding the Ctrl key to highlight all your selections, and clicking Add to add the selected destinations members to the work class.

Members of

All of the modules that are contained as members of the work class display in this list. To remove a member, select it and click Remove.

Custom

HTTP: Custom HTTP pattern
EJB:
- Custom EJB name
- Custom EJB method
JMS:
- Custom bus name
- Custom destination

in the format name:type, where name and type are placeholders. Click Add pattern to make your custom destination a member of the work class. You can use the wildcard option, (*), as well. The Custom pattern field supports regular expressions, for example, you can specify all EJB method names that begin with get with one custom pattern.

Step 3: Confirm work class creation

A summary of actions displays the changes for the work class creation.

Click Finish to create the work class.

Add rule

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 Subexpression builder 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: Permit routing to From the Select edition name list, select the edition name to which routing is permitted. Permit routing with affinity to: From the Select edition name list, select the edition name to which routing is permitted. Redirect routing to In the Enter in URI to redirect to field, type the URI to which requests are redirected. Reject routing with return code In the Enter in return code field provide the routing rejection return code.

Attribute

Description

Condition

Add a condition, or use the Subexpression builder 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:

Permit routing to: From the Select edition name list, select the edition name to which routing is permitted.
Permit routing with affinity to:: From the Select edition name list, select the edition name to which routing is permitted.
Redirect routing to: In the Enter in URI to redirect to field, type the URI to which requests are redirected.
Reject routing with return code: In the Enter in return code field provide the routing rejection return code.

Delete rule

Deletes an existing, selected rule.

Move up / move down

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.

File name: wc_detail_rule.html