Configure ActiveGate launcher

ActiveGate launcher is a watchdog process that starts a virtual machine for your ActiveGates. The customizable ActiveGate launcher configuration file is enabled as of ActiveGate version 1.154.

The launcher configuration is separate from the ActiveGate configuration. It's stored in two configuration files:

deskgateway.ini, the main configuration file. On Linux, this file is located in the launcher subfolder of the installation directory. On Windows, it's stored directly in the installation folder.
launcheruserconfig.conf, which includes a customizable configuration and is stored in the ActiveGate configuration folder:

On Linux: /var/lib/desk/gateway/config/launcheruserconfig.conf
On Windows: C:\ProgramData\desk\gateway\config\launcheruserconfig.conf

You should not modify the main configuration file deskgateway.ini, as this file won't be preserved during upgrades. Note that the main configuration file deskgateway.ini contains a reference that denotes the location of the customizable configuration file launcheruserconfig.conf.

The following modifications to launcheruserconfig.conf are preserved during upgrades:

Memory limit settings (-memorylimit.absolute and -memorylimit.percentage)
JVM settings (settings beginning with -D)
Port range settings (settings begining with -portrange=)

The JVM parameters must be preceded with the -vmargs flag, just like in the main configuration file.

Here are some example entries in the customizable file launcheruserconfig.conf:

# Xmx settings 80% of available RAM + 0 MB
-memorylimit.absolute=0
-memorylimit.percentage=80
-vmargs
-Dhttp.proxyHost=127.0.0.1
-Dhttps.proxyHost=127.0.0.1
-Dhttp.proxyPort=8080
-Dhttps.proxyPort=8080

By default, the ActiveGate launcher will utilize ports above 50000. Certain deployments may require you to configure a different port. To specify the port range that the ActiveGate launcher should use, add or modify the -portrange property in the launcheruserconfig.conf file. For example:

-portrange=50100:50100