-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
Apply Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
-
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
-
Install a Citrix ADC VPX instance on Linux-KVM platform
-
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
-
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
-
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
-
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
-
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Deploy a Citrix ADC VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Configure a Citrix ADC VPX instance to use SR-IOV network interface
-
Configure a Citrix ADC VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a Citrix ADC VPX instance on Microsoft Azure
-
Network architecture for Citrix ADC VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Configure a Citrix ADC VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
-
Configure address pools (IIP) for a Citrix Gateway appliance
-
Upgrade and downgrade a Citrix ADC appliance
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
On-premises Citrix Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
Authentication and authorization for System Users
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Citrix ADC Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
-
-
Synchronizing Configuration Files in a High Availability Setup
-
Restricting High-Availability Synchronization Traffic to a VLAN
-
Understanding the High Availability Health Check Computation
-
Managing High Availability Heartbeat Messages on a Citrix ADC Appliance
-
Remove and Replace a Citrix ADC in a High Availability Setup
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.
Este artigo foi traduzido automaticamente.
这篇文章已经过机器翻译.放弃
Translation failed!
Configuring policies for application units
For an AppExpert application, you can configure policies for Compression, Caching, Rewrite, Responder, and Application Firewall. The templates that you download from the Citrix Community web site provide you with a set of policies that fulfill the most common application management requirements. You might want to fine-tune or customize these policies. If the set of policies provided for a given application unit does not include policies for a particular feature, you can create and bind your own policies for that feature.
If you create an AppExpert application without using a template, you must configure all the policies that the web application needs.
The GUI uses various icons to indicate whether or not policies are configured for a feature. For an application unit, if a policy is configured for a given feature, an icon that represents the feature is displayed. For example, if a compression policy is configured for an application unit, a compression icon is displayed in the Compression column for the application unit. For features for which no policy is configured, an icon depicting a plus sign (+) is displayed.
Note: When configuring policies for application units, you might need to configure policies and expressions that are either in the classic or default syntax. Additionally, when you configure default syntax policies, you might need to specify parameters such as Goto expressions and invoke policy banks.
For information about configuring policies and expressions in both formats, see Policies and Expressions.
Configuring compression policies
You can use either classic policies or advanced policies to configure compression, but you cannot bind compression policies of both types to the same application unit.
To configure a compression policy for an application unit:
- Navigate to AppExpert > Applications.
- In the details pane, in the row for the application unit you want to configure, click the icon provided in the Compression column.
- In the Configure Compression Policies dialog box, do one or more of the following, depending on the configuration tasks you want to perform:
-
Click Switch to Default Syntax if you want to configure a default syntax compression policy. If you want to bind or configure classic compression policies, and if you are in the default syntax view, you can click Switch to Classic Syntax to return to the classic policy view and begin modifying bound classic policies or create and bind new classic compression policies.
Important: This setting also determines what policies are displayed when you want to insert a policy. For example, if you are in the default syntax view, when you click Insert Policy, the list that appears in the Policy Name column will include only default syntax policies. You cannot bind policies of both types to an application unit.
-
If you want to configure classic policies, click either Request or Response, depending on whether you want the policy to be evaluated at request-time or at response-time.
You can configure both request-time and response-time classic compression policies for an application unit. After evaluating all of the request-time policies, if no match is found, the appliance evaluates response-time policies.
-
To modify a compression policy that is already bound to the application unit, click the name of the policy, and then click Modify Policy. Then, in the Configure Compression Policy dialog box, modify the policy, and then click OK.
For information about modifying a compression policy, see Compression.
-
To unbind a policy, click the name of the policy, and then click Unbind Policy.
-
To modify the priority assigned to a policy, double-click the priority value, and then enter a new value.
-
To regenerate assigned priorities, click Regenerate Priorities.
-
To insert a new policy, click Insert Policy and, in the list that is displayed in the Policy Name column, click New Policy. Then, in the Create Compression Policy dialog box, configure the policy, and then click Create.
For information about modifying a compression policy, see Compression.
-
If you are configuring a default syntax expression, do the following:
- In the Goto Expression column, select a Goto expression.
- In the Invoke column, specify the policy bank that you want to invoke if the current policy evaluates to TRUE.
-
- Click Apply Changes, and then click Close.
Configuring Caching Policies
You can use only default syntax policies and expressions to configure Caching policies.
To configure Caching policies for an application unit:
- Navigate to AppExpert > Applications.
- In the details pane, in the row for the application unit you want to configure, click the icon provided in the Caching column.
- In the Configure Cache Policies dialog box, do one or more of the following, depending on the configuration tasks you want to perform:
-
Click either Request or Response, depending on whether you want the policy to be evaluated at request-time or at response-time.
You can configure both request-time and response-time Caching policies for an application unit. After evaluating all of the request-time policies, if no match is found, the appliance evaluates response-time policies.
-
To modify a Caching policy that is already bound to the application unit, click the name of the policy, and then click Modify Policy. Then, in the Configure Cache Policy dialog box, modify the policy, and then click OK.
For information about modifying a Caching policy, see Integrated Caching.
-
To unbind a policy, click the name of the policy, and then click Unbind Policy.
-
To modify the priority assigned to a policy, double-click the priority value, and then enter a new value.
-
To regenerate assigned priorities, click Regenerate Priorities.
-
To insert a new policy, click Insert Policy and, in the list that is displayed in the Policy Name column, click New Policy. Then, in the Create Cache Policy dialog box, configure the policy, and then click Create.
For information about modifying a Caching policy, see Integrated Caching.
-
In the Goto Expression column, select a Goto expression.
-
In the Invoke column, specify the policy bank that you want to invoke if the current policy evaluates to TRUE.
-
- Click Apply Changes, and then click Close.
Configuring rewrite policies
You can use only default syntax policies and expressions to configure Rewrite policies.
To configure Rewrite policies for an application unit:
- Navigate to AppExpert > Applications.
- In the details pane, in the row for the application unit you want to configure, click the icon provided in the Rewrite column.
- In the Configure Rewrite Policies dialog box, do one or more of the following, depending on the configuration tasks you want to perform:
-
Click either Request or Response, depending on whether you want the policy to be evaluated at request-time or at response-time.
You can configure both request-time and response-time Rewrite policies for an application unit. After evaluating all of the request-time policies, if no match is found, the appliance evaluates response-time policies.
-
To modify a Rewrite policy that is already bound to the application unit, click the name of the policy, and then click Modify Policy. Then, in the Configure Rewrite Policy dialog box, modify the policy, and then click OK.
For information about modifying a Rewrite policy, see Rewrite.
-
To unbind a policy, click the name of the policy, and then click Unbind Policy.
-
To modify the priority assigned to a policy, double-click the priority value, and then enter a new value.
-
To regenerate assigned priorities, click Regenerate Priorities.
-
To insert a new policy, click Insert Policy and, in the list that is displayed in the Policy Name column, click New Policy. Then, in the Create Rewrite Policy dialog box, configure the policy, and then click Create.
For information about modifying a Rewrite policy, see Rewrite.
-
In the Goto Expression column, select a Goto expression.
-
In the Invoke column, specify the policy bank that you want to invoke if the current policy evaluates to TRUE.
-
- Click Apply Changes, and then click Close.
Configuring responder policies
You can use only default syntax policies and expressions to configure Responder policies.
To configure Responder policies for an application unit:
- Navigate to AppExpert > Applications.
- In the details pane, in the row for the application unit you want to configure, click the icon provided in the Responder column.
- In the Configure Responder Policies dialog box, do one or more of the following, depending on the configuration tasks you want to perform:
-
To modify a Filter policy that is already bound to the application unit, click the name of the policy, and then click Modify Policy. Then, in the Configure Responder Policy dialog box, modify the policy, and then click OK.
For information about modifying a Responder policy, see Responder.
-
To unbind a policy, click the name of the policy, and then click Unbind Policy.
-
To modify the priority assigned to a policy, double-click the priority value, and then enter a new value.
-
To regenerate assigned priorities, click Regenerate Priorities.
-
To insert a new policy, click Insert Policy and, in the list that is displayed in the Policy Name column, click New Policy. Then, in the Create Responder Policy dialog box, configure the policy, and then click Create.
For information about modifying a Responder policy, see Responder.
-
In the Goto Expression column, select a Goto expression.
-
In the Invoke column, specify the policy bank that you want to invoke if the current policy evaluates to TRUE.
-
- Click Apply Changes, and then click Close.
Configuring Application Firewall Policies
You can configure both classic and default syntax policies and expressions for Application Firewall. However, if a policy of one type is already bound globally or to a virtual server that is configured on the appliance, you cannot bind a policy of the other type to an application unit. For example, if a default syntax policy is already bound either globally or to a virtual server, you cannot bind a classic policy to an application unit.
To configure Application Firewall policies for an application unit:
- Navigate to AppExpert > Applications.
- In the details pane, in the row for the application unit you want to configure, click the icon provided in the Application Firewall column.
- In the Configure Application Firewall Policies dialog box, do one or more of the following, depending on the configuration tasks you want to perform:
-
Click either Classic Expression or Advanced Expression depending on the type of expression you want to configure for the Application Firewall policy.
Important: This setting also determines what policies are displayed when you want to insert a policy. For example, if you select Advanced Expression, when you click Insert Policy, the list that appears in the Policy Name column will include only default syntax policies. You cannot bind policies of both types to an application unit. This option is not available if a policy of either type is already bound either globally or to a virtual server.
-
To modify an application firewall policy that is already bound to the application unit, click the name of the policy, and then click Modify Policy. Then, in the Configure Application Firewall Policy dialog box, modify the policy, and then click OK.
For information about modifying a application firewall policy, see Policies.
-
To unbind a policy, click the name of the policy, and then click Unbind Policy.
-
To modify the priority assigned to a policy, double-click the priority value, and then enter a new value.
-
To regenerate assigned priorities, click Regenerate Priorities.
-
To insert a new policy, click Insert Policy and, in the list that is displayed in the Policy Name column, click New Policy. Then, in the Create Application Firewall Policy dialog box, configure the policy, and then click Create.
For information about modifying a application firewall policy, see Policies.
-
- Click Apply Changes, and then click Close.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.