Define 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.
Define a service policy to categorize and prioritize work requests. See the topic on defining a service policy for more information.
Optionally, we can add rules to the 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 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.
- Select Applications > Application types > WebSphere enterprise applications > application_name > Service policies. Click OK.
- From the Service policies tab, expand the work request type and the work class for which to create a rule, and click Add rule > Rule builder > Add.
- 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
- Click the new rule to set its operators. A predefined set of operators displays for the type of rule condition that is selected.
- Select the operator to use and enter the appropriate information in the provided field. For example, we can classify incoming requests for the StockTradeWork work class by a group ID to use a different transaction class.
- Select the (=) operator and type HTTP in the provided field, to provide a different transaction class for HTTP requests.
Subtopics
- (dist)(zos) Rules support
Support for HTTP rules applies for both routing and service policy rules. They can be variously located and have a specific order of priority.
- (dist)(zos) Ruleset administrative tasks
We can use the ruleset commands to add, remove, or modify rules and actions of the ruleset.xml file without using the administrative console.
- (dist)(zos) Route policy action types
We can create routing policies for HTTP and SOAP and SIP requests. The routing policy actions types vary for different locations of rules. The table in this topic shows the actions types for routing policies based on location and protocol.
- (dist)(zos) Overview of work classes
A work class is a grouping of work that is to be done by an application server. Work is an HTTP request, a SIP message, an IIOP call, or a JMS message. Each work class contains a set of rules used by Intelligent Management to determine how to handle that work.
- (dist)(zos) Work class types
We can use either default work classes created during a system application installation or define our own. Default work classes and directories for system applications are created during profile augmentation to support the high availability deployment manager. Default and new application work classes are defined on a per application edition basis.
- (dist)(zos) Intelligent Management: default work class administrative tasks
We can use the default work class administrative tasks to create work classes.
- (dist)(zos) workclassoperations.py script
We can use the workclassoperations.py script to create, update, and manage work classes.
- (dist)(zos) Intelligent Management: request classification operators
Intelligent Management supports operators in the rules expressions. These operators are also referred to as predicates in Structured Query Language (SQL) terminology because they appear inside of a WHERE or HAVING clause. Operators are case insensitive.
- (dist)(zos) Rule-based request classification
With any rule-based technology, rule-based processing involves three basic areas: the vocabulary that forms the language, the grammar for expressing the vocabulary in statements, and the rule-processing engine.
Related concepts
Work class types
Related tasks
Define a service policy
Intelligent Management: subexpression builder operands Intelligent Management: routing and service policies