-
-
-
Load balancing with Citrix ADC
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!
Load balancing with Citrix ADC
This article guides you through the deployment of a Workspace Environment Management (WEM) server group containing two or more infrastructure servers in all active load balanced configurations. The article provides details of how to configure a Citrix ADC appliance to load balance incoming requests from the WEM administration console and the WEM agent.
You can listen on these WEM ports with Citrix ADC:
- Administration port (by default, 8284)
- Agent service port (by default, 8286)
- Cached data synchronization port (by default, 8288)
Suppose you want to deploy a WEM server group containing two infrastructure servers (infrastructure server 1 and infrastructure server 2). Perform the following steps:
-
Log on to the Citrix ADC management GUI and then click Configuration.
-
Navigate to Traffic Management > Load Balancing > Servers > Add and then click Add to add infrastructure server 1. Repeat to add infrastructure server 2.
-
Navigate to Traffic Management > Load Balancing > Service Groups and then click Add to create a service group for the administration console service.
- Protocol. Select TCP.
- Cache Type. Select SERVER.
-
On the Load Balancing Service Group page, click No Service Group Member.
-
On the Create Service Group Member page, select Server Based, click the right arrow, and then select infrastructure server 1. Repeat steps 3 through 5 for infrastructure server 2.
- Port. For example, type 8284 for the administration console.
-
Follow steps 3 through 5 to create service groups for the agent service and cache synchronization service.
- Port. For the agent service port, type 8286. For the cached data synchronization port, type 8288.
-
Navigate to Traffic Management > Load Balancing > Virtual Servers and then click Add to add a virtual server for the administration console service.
- Protocol. Select TCP.
- IP Address Type. Select IP Address.
- IP Address. Type the Virtual IP. For details, see Configuring Citrix ADC-owned IP addresses.
- Port. For example, type 8284 for the administration console.
-
Click No Load Balancing Virtual Server Service Group Binding.
-
On the Service Group Binding page, click the right arrow, select the corresponding service group, and then click Bind.
-
Follow steps 7 through 9 to create virtual servers that listen on the agent service port and the cached data synchronization port.
- Port. For the agent service port, type 8286. For the cached data synchronization port, type 8288.
Share
Share
In this article
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 I DO NOT AGREE to exit.