Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS
Routing policy action types
You 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.
Action types
Table 1. Action types for rules based on protocol Rules Location Action type HTTP
Inside work classes at the application level
- Permit routing to (permit)
- Permit routing with affinity (permitsticky)
- Redirect routing to (redirect)
- Reject routing with return code (reject)
- Permit to servers in maintenance mode (permitMM)
- Permit with affinity to servers in maintenance mode (permitstickyMM)
SOAP
Inside work classes at the application level
- Permit routing to (permit)
- Permit routing with affinity (permitsticky)
- Redirect routing to (redirect)
- Reject routing with return code (reject)
- Permit to servers in maintenance mode (permitMM)
- Permit with affinity to servers in maintenance mode (permitstickyMM)
HTTP
Inside work classes at the ODR level
- Permit routing to (permit)
- Permit routing with affinity (permitsticky)
- Redirect routing to (redirect)
- Reject routing with return code (reject)
- Permit to servers in maintenance mode (permitMM)
- Permit with affinity to servers in maintenance mode (permitstickyMM)
HTTP
At the ODR level. There is no default rule supported for HTTP rules in this location. The rules created take precedence over any rules at the application level.
- Permit routing to (permit)
- Permit routing with affinity (permitsticky)
- Redirect routing to (redirect)
- Permit to servers in maintenance mode (permitMM)
- Permit with affinity to servers in maintenance mode (permitstickyMM)
SIP
At the ODR level.
- Permit routing to (permit)
- Reject routing with return code (reject)
Selecting an action type
Alternatively, you can apply new classification rules by clicking Add Rule and taking the following actions:
- Selecting one of the following options:
- Permit routing to: From the Select edition name here list select the edition name.
- Reject routing with return code: From the Select edition name here list select the edition name and in the Enter in return code field, type the return code.
- Redirect routing to: From the Select edition name here list select the edition name and in the Enter URI to redirect to field, type the URI.
- Permit routing with affinity to: From the Select edition name here list select the edition name.
- Click Apply.
- If you know your rule name, type the new routing rule name, and select one of the following options from the Then list:
- Permit routing to: From the Select edition name here list select the edition name.
- Reject routing with return code: From the Select edition name here list select the edition name and in the Enter in return code field, type the return code.
- Redirect routing to: From the Select edition name here list select the edition name and in the Enter URI to redirect to field, type the URI.
- Permit routing with affinity to: From the Select edition name here list select the edition name.
- To build a new rule, click Rule builder, select the type of rule to create from the rule Condition list, and click Add:
- Click the new rule to set its operators. A predefined set of operators displays for the type of rule condition selected.
- Select the operator to use and enter the appropriate information in the field provided.
Related tasks
Defining a service policy
Related reference
Work class types
Subexpression builder operands for routing and service policies
Rules for ODR routing policy administrative tasks
Routing and service policies