Many ActiveGate configuration settings (for example, connectivity and proxy settings, ciphers, or memory dump settings), are stored in the custom.properties and launcheruserconfig.conf configuration files, which are located in the ActiveGate configuration directory. The properties listed in the property files are applicable for both Environment ActiveGates and Cluster ActiveGates.
Specify custom communication ports on which ActiveGate listens for traffic from OneAgent. Open these ports in a firewall, if a firewall is in use.
See the webserver section in ActiveGate configuration.
Set up a proxy for ActiveGate, for communicating with the Dynatrace Cluster, or for use by ActiveGate modules, for specific monitoring needs—such as for Synthetic Monitoring or monitoring of AWS/VMware/Azure, Cloud Foundry, or Kubernetes.
See Set up a proxy for ActiveGate.
Set up a reverse proxy or a load balancer, on the path from an ActiveGate to the Dynatrace Cluster. This allows your ActiveGate to connect to any available node of the Cluster, spreading the load between the nodes.
See Reverse proxy or load balancer for ActiveGate.
Specify trusted certificates in a trusted key store, to be used by ActiveGate for connections where ActiveGate is the client: ActiveGate connects to other Dynatrace components (clusters, servers) or third-party systems (such as VMware, Cloud Foundry, Kubernetes or OpenShift) using SSL-secured channels. The root CA certificate store shipped with Java is sometimes insufficient to cover all required use cases. Therefore you can provide a customized list of trusted root certificates, and configure ActiveGate to combine them with the defaults.
See Trusted root certificates for ActiveGate.
Specify a custom certificate to be served by ActiveGate: Connection to ActiveGate, from OneAgents or REST API, takes place over an encrypted HTTPS channel. ActiveGate provides an authentication certificate to all connecting clients. While OneAgent instances may ignore the validity of ActiveGate certificates (depending on configuration), connections from browser clients (such as the RUM JavaScript) do verify that the hostname listed in the certificate is correct, before they send data.
See Custom SSL certificate for ActiveGate.
Specify ciphers to be used by ActiveGate for secure communication.
See Cipher configuration for ActiveGate.
Enable multiple ActiveGate modules to run separate monitoring processes.
See ActiveGate modules.
Configure a single ActiveGate to support multiple environments.
See Multi-environment deployment of ActiveGate.
To pass custom parameters to the ActiveGate Java process, specify the parameters in the launcher configuration file launcheruserconfig.conf.
See Custom parameters for the ActiveGate Java process.
Set ActiveGate memory limits: Memory usage limits for ActiveGate can be specified in the configuration as relative (percentage of available RAM) and absolute figure.
See ActiveGate memory limits.