Installing the distributed front-end server#

Starting in HCL™ Launch 7.0.3, you can install a distributed front-end server. The front-end server supports high availability and fault tolerance to ensure success of your application delivery process.

You must have a standard HCL Launch server installed.

The below image is a recommended approach for managing large volumes of traffic coming through your instances. End-user HTTP traffic can be routed through a load balancer, that can then be handed out to the Distributed Front-End Servers. If the front-end server cannot directly service the request, it makes a request to the backend load balancer to handle. The front-end server proxy URL is based on Agent External URL configured on the System Settings page.

Distributed front-end server communication

A front-end server does not participate in agent communication, workflows, emails, notification services, or cleanup. When connected to a front-end server, you can still do everything that you would be able to do on a normal HCL Launch server. Requests for services that are not available on a front-end server will proxy a request to the backend.

The following property must be enabled on the backend servers in


Add back end servers to Network>Cluster in either one of the back end servers or in load balancer.

Specify the -frontend flag when running the installer. Add the flag to the installation file with the command install-server.bat -frontend on Windows or ./ -frontend on Linux and Unix systems.

Note: The front-end server must have the same shared filesystem as the High-Availability setup. For more information, see Setting up clusters of servers.


Derby is not a database option when installing the distributed front-end server.

Parent topic: Installing the server