See Also
A load balancer is required in an Enterprise pool that has more than one Enterprise Edition server. The load balancer performs the critical role of delivering scalability and high availability across multiple servers that are connected to a centralized database on the Office Communications Server, Back-End Database. After you have prepared your environment and have installed and configured SQL Server for Office Communications Server, but before you create Domain Name System (DNS) records for your pool, configure a load balancer with the appropriate settings for your Enterprise pool (that is, if you need to deploy a load balancer).
 Note: |
|---|
| A load balancer is not required if you deploy only one Enterprise Edition server in your pool. If you are deploying a pool that has a single Enterprise Edition server connected to the Back-End Database, skip to Create and Verify DNS Records for Your Server or Pool. |
Only one load balancer is required for a pool that has more than one Enterprise Edition server, but you can optionally create two logical load balancers—one for the Front End Servers and one for the Web Components Server—if you deploy Enterprise Edition in an expanded configuration. If you want to employ two logical load balancers, you can configure two virtual IP (VIP) addresses on one physical load balancer, or you can configure two separate physical load balancers.
Load Balancer Settings
Configure the load balancer for your Enterprise pool
using the documentation according to the settings described in the
“Prerequisites for a Load Balancer Connecting to a Pool” section of
|
Note: |
|---|
| If you deploy a load balancer for computers that are running
applications such as Conferencing Attendant, Conferencing
Announcement Service, Response Group Service, and Outside Voice
Control, you must also configure the load balancer with the ports
used by each application, as described in
|