Configure Gateway Administrator for Failover and Load Balancing
After you have created a cluster that includes multiple Gateway Administrative servers, you can use DNS to support failover and load balancing between the members of that cluster. Using DNS, you can create a symbolic host name that can be used to connect to any of the servers in your cluster. For example if you have created a cluster that includes fxgserver1, fxgserver2, and fxgserver3, you can set up a DNS entry with the alias GatewayAdministratorCluster, and add each of the servers in the cluster to that entry.
Once you have created the DNS alias, you will need to configure the FileXpress Secure Shell proxy to connect to the DNS alias (GatewayAdministratorCluster in this example). If one FileXpress Gateway server is not running, the proxy will connect to another server configured for the DNS entry, and failover support is achieved.
You can also use the DNS service to achieve load balancing support. Since data replication automatically occurs between all servers in the cluster, the FileXpress Secure Shell Proxy receives the same user and transfer site information regardless of which instance of the Gateway Administrator it is connected to.
Before you begin
To create an alias (common name) to connect to any server in a cluster
Once you have created the alias, you need to configure the FileXpress Proxy to connect to this alias. The following procedure shows how to do this if you have a single FileXpress Proxy system. See Configure Multiple FileXpress Proxy Servers if you have more than one.
To configure the FileXpress Proxy to connect to the alias host name
After you have configured a DNS alias to point to a cluster of Gateway Administrator servers, you should only use the non-clustered name of a member of the cluster to access the Gateway Administrator web pages as described below. Web session information is stored in memory, and is not replicated across clusters, so if the web browser switches from one member of a cluster to another during a single browsing session, the session will fail.
If you use a load balancer in front of the Gateway Administrator cluster for scalability, then sticky sessions should be enabled on the load balancer so that a web browsing session stays on the same server.
To access the Gateway Administrator web interface after configuring a DNS alias