[AIX Solaris HP-UX Linux Windows][z/OS]

Defining service policy rules

Service policy rules define the service policy goal to use for a single piece of incoming work. This is done by associating a transaction class with a Boolean expression. Each transaction class is associated with exactly one service policy goal. The Boolean expression can be customized to match any specific piece of work.

Before you begin

Define a service policy to categorize and prioritize work requests. See the topic on defining a service policy for more information.

About this task

Optionally, you can add rules to your service policy. If the expression evaluates to true for a particular request, the policy associated with that rule is used. A work class contains a set of rules that is used to classify requests, such as an HTTP request or IIOP call. Complete the following steps to define a service policy rule. This is just one example of how to create service policy rules.
Avoid trouble: The default rule for HTTP service and routing policy rules is not supported at the on demand router (ODR) level. You can use the Routing policy HTTP rules console page to add, delete, or move routing rules but you cannot use the console page to perform an If no routing rules apply action. To create a rule which applies when no routing rules apply, add a rule and set the priority of the rule higher than all other rules.

Procedure

  1. Select Applications > Application types > WebSphere enterprise applications > application_name > Service policies. Click OK.
  2. From the Service policies tab, expand the work request type and the work class for which you want to create a rule, and click Add rule > Rule builder > Add.
  3. Select the type of rule, such as Group ID
    This displays the rule builder panel. Continue to build a rule, specify the transaction class, or click OK
  4. Click the new rule to set its operators.
    A predefined set of operators displays for the type of rule condition that is selected.
  5. Select the operator that you want to use and enter the appropriate information in the provided field.
    For example, you can classify incoming requests for the StockTradeWork work class by a group ID to use a different transaction class.
  6. Select the (=) operator and type HTTP in the provided field, to provide a different transaction class for HTTP requests.