Configure High Availability Web Console and Command Center

You can configure high availability Web Console setups to provide uninterrupted and reliable access to Web Console and Command Center operations.

Before You Begin

Get the right hardware for the Web Server and Web Console hosts.

For a list of supported platforms, see the following pages:
- System Requirements for Web Server.
- System Requirements for Web Console.
For sufficient hardware requirements for the Web Server, see CommCell Sizing.
Set up a load balancer software. For example, NetScaler.

In your CommCell environment, install two Web Servers and two Web Consoles.

Verify that Web Console1 points to Web Server1 and Web Console2 points to Web Server 2.
Configure a common domain name on your load balancer software to access the Web Consoles.
Set up rules on your load balancer software to allow sticky sessions (also called as session affinity and persistent sessions) for the two Web Consoles.

Note

The load balancer will access the Web Consoles through ports 443 (https) and 80 (http).

If the load balancer is using SSL offloading, on each Web Console, update the connector port configuration in the Software_Installation_Directory\Apache\Conf\server.xml file:
1. Optional. Modify the server attribute to reflect the Web Console server used during the user session.
2. To allow your SSL setup work, configure scheme, secure, proxyPort, and proxyName attributes. These attributes force Tomcat to reply in HTTPS on any HTTP requests.
```
<Connector port="80" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="443" server="CV WC1" compression="on" noCompressionUserAgents="gozilla,traviata" compressionMinSize="500" compressableMimeType="text/html,text/json,application/json,text/xml,text/plain,application/javascript,text/css,text/javascript,text/js" useSendfile="false" scheme="https" secure="true" proxyPort="443" proxyName="the.loadbalancer.fqdn" />
```