-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
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 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 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
-
Configuring authentication, authorization, and auditing policies
-
Configuring Authentication, authorization, and auditing with commonly used protocols
-
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
-
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
-
Use Case 1: Configuring DataStream for a primary/secondary Database Architecture
-
Use Case 2: Configuring the Token Method of Load Balancing for DataStream
-
-
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 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
-
Authentication and authorization
-
-
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
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)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
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.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Use Case 1: Configure DataStream for a primary/secondary database architecture
A commonly used deployment scenario is the primary/secondary database architecture where the primary database replicates all information to the secondary databases.
For primary/secondary database architecture, you might want all WRITE requests to be sent to the primary database and all READ requests to the secondary databases.
The following figure shows the entities and the values of the parameters that you need to configure on the appliance.
Figure 1. DataStream Entity Model for Primary/Secondary Database Setup
In this example scenario, a service (Svc_mysql_1) is created to represent the primary database and is bound to a load balancing virtual server (Lb_vsr_mysql_primary). Three more services (Svc_mysql_2, Svc_mysql_3, and Svc_mysql_4) are created to represent the three secondary databases, and they are bound to another load balancing virtual server (Lb_vsr_mysql_secondary).
A content switching virtual server (Cs_vsr_mysql_1) is configured with associated policies to send all WRITE requests to the load balancing virtual server, Lb_vsr_mysql_primary. All READ requests are sent to the load balancing virtual server, Lb_vsr_mysql_secondary.
When a request reaches the content switching virtual server, the virtual server applies the associated content switching policies to that request. After evaluating the policies, the content switching virtual server routes the request to the appropriate load balancing virtual server, which sends it to the appropriate service.
The following table lists the names and values of the entities and the policy configured on the Citrix ADC appliance.
Entity Type | Name | IP Address | Protocol | Port | Expression |
---|---|---|---|---|---|
Services | Svc_mysql_1 | 198.51.100.5 | MYSQL | 3306 | NA |
Svc_mysql_2 | 198.51.100.6 | MYSQL | 3306 | NA | |
Svc_mysql_3 | 198.51.100.7 | MYSQL | 3306 | NA | |
Svc_mysql_4 | 198.51.100.8 | MYSQL | 3306 | NA | |
Monitor | lb_mon1 | NA | MYSQL-ECV | NA | mysql.res.atleast_rows_count(1) |
Load balancing virtual servers | Lb_vsr_mysql_primary | 198.51.100.201 | MYSQL | 3306 | NA |
Lb_vsr_mysql_secondary | 198.51.100.202 | MYSQL | 3306 | NA | |
Content switching virtual server | Cs_vsr_mysql_1 | 198.51.100.161 | MYSQL | 3306 | NA |
Content switching policy | Cs_select | NA | NA | NA | MYSQL.REQ.QUERY.COMMAND.contains("select") |
Table 1. Entity and Policy Names and Values
To configure DataStream for a primary/secondary database setup by using the command line interface
At the command prompt, type
add db user user1 -password user1
add service Svc_mysql_1 198.51.100.5 mysql 3306
add service Svc_mysql_2 198.51.100.6 mysql 3306
add service Svc_mysql_3 198.51.100.7 mysql 3306
add service Svc_mysql_4 198.51.100.8 mysql 3306
add lb monitor lb_mon1 MYSQL-ECV -sqlQuery "select * from table1;" -evalrule "mysql.res.atleast_rows_count(1)" -database "NS" -userName "user1"
add lb vserver Lb_vsr_mysql_primary mysql 198.51.100.201 3306
add lb vserver Lb_vsr_mysql_secondary mysql 198.51.100.202 3306
bind lb vserver Lb_vsr_mysql_primary svc_mysql_1
bind lb vserver Lb_vsr_mysql_secondary svc_mysql_2
bind lb vserver Lb_vsr_mysql_secondary svc_mysql_3
bind lb vserver Lb_vsr_mysql_secondary svc_mysql_4
add cs vserver Cs_vsr_mysql_1 mysql 198.51.100.161 3306
add cs policy Cs_select –rule "MYSQL.REQ.QUERY.COMMAND.contains(\"select"\)"
bind cs vserver Cs_vsr_mysql_1 Lb_vsr_mysql_primary
bind cs vserver Cs_vsr_mysql_1 Lb_vsr_mysql_secondary –policy Cs_select –priority 10
bind service Svc_mysql_1 -monitorName lb_mon1
bind service Svc_mysql_2 -monitorName lb_mon1
bind service Svc_mysql_3 -monitorName lb_mon1
bind service Svc_mysql_4 -monitorName lb_mon1
<!--NeedCopy-->
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.