Product Documentation
ADC
14.1 - Current Release 13.1 13.0 12.1
View PDF

AppQoE policies

August 20, 2024
Contributed by: 
C C S

To implement AppQoE, you must configure at least one policy to tell your Citrix ADC how to distinguish the connections to be queued in a specific queue.

To configure an AppQoE policy by using the command line

At the command prompt, type the following command:

add appqoe policy <name> -rule <expression> -action <string>

Example:

The following example selects requests with a User-Agent header that contains “Android”, and assigns them to the medium priority queue. These requests come from smartphones and tablets that run the Google Android operating system.


> add appqoe action appqoe-act-primd -priority MEDIUM
Done
> add appqoe policy appqoe-pol-primd -rule "HTTP.REQ.HEADER("User-Agent").CONTAINS("Android")" -action appqoe-act-primd
Done
> sh appqoe policy appqoe-pol-primd
        Name: appqoe-pol-primd
        Rule: HTTP.REQ.HEADER("User-Agent").CONTAINS("Android")
        Action: appqoe-act-primd
        Hits: 0

Done
<!--NeedCopy-->

Parameters for configuring an AppQoE policy

  • name. A name for the AppQoE policy. The name can begin with a letter, number, or the underscore symbol, and can consist of from one to 127 letters, numbers, and the hyphen (-), period (.) pound (#), space ( ), at sign (@), equals (=), colon (:), and underscore (_) symbols. You should chose a name that helps identify the type of action.
  • rule. A Citrix ADC expression that tells the appliance which connections it should handle.
  • action. The AppQoE action to perform when a connection matches the policy.

To configure an AppQoE policy by using the configuration utility

  1. Navigate to App-Expert > AppQoE > Policies.

  2. In the details pane, do one of the following:

    • To create a new policy, click Add.
    • To modify an existing policy, select the policy, and then click Edit.

  3. If you are creating a new policy, in the Create AppQoE Policy dialog, in the Name text box, type a name for your new policy.

    The name can begin with a letter, number, or the underscore symbol, and can consist of from one to 127 letters, numbers, and the hyphen (-), period (.) pound (#), space ( ), at sign (@), equals (=), colon (:), and underscore (_) symbols. You should chose a name that helps identify the purpose and effect of this policy.

    If you are modifying an existing policy, skip this step. You cannot change the name of an existing policy.

  4. In the Action drop-down list, choose the AppQoE action to perform when the policy matches a connection. Click the plus (+) to open the Add AppQoE Action dialog and add a new action.

  5. In the Rule text box, either enter the policy expression directly, or click New to create a policy expression. If you click New, perform the following steps:

    1. In the Create Expression dialog box, click Add.

    2. In the Add Expression dialog box, select a common expression from the Frequently Used Expressions drop-down list, or use the Construct Expression drop-down lists to create the expression that defines which traffic to filter.

      If you choose to create your own expression, you start by selecting the first term from the first drop-down list on the left side of the Construct Expression area. The choices in that list are:

      • HTTP: All traffic to port 80 and port 443.
      • SYS:
      • CLIENT:
      • SERVER:
      • ANALYTICS:
      • TEXT:

      The default choice is HTTP. After you make a choice in the first drop-down list (or accept the default), you can choose the next term in your expression from the drop-down list to the right of it. The terms in that list and other lists that follow change depending on your previous choices; the lists offer only terms that are valid choices. Continue to select terms until you have finished the expression.

    3. When you have created the expression that you want, click OK. The expression is added in the Expression text box.

  6. Click Create. The expression appears in the Rule text box.
AppQoE policies
August 20, 2024
Contributed by: 
C C S
August 20, 2024
Contributed by: 
C C S

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.