Configuring your ActiveGate includes tasks such as opening communication ports, setting up a proxy or reverse proxy, configuring a Java or custom trusted store, configuring memory dumps, and ensuring connectivity.
In certain Dynatrace deployments, you need to tell the ActiveGate to ignore the Managed cluster address and instead use the provided address of the reverse proxy. You may have to configure a single ActiveGate in support of multiple monitoring environments. Also, because Dynatrace components communicate through SSL using ciphers to encrypt HTTP requests, you also have to configure ciphers on your ActiveGate.
For most configuration settings (like connectivity, proxy, or network zones), you can use the properties file.
For settings applied with each ActiveGate startup (like set memory limits, Java process parameters, and port ranges), you can use the launcher file.
- To check the ports you need to open for your ActiveGates, see Which network ports does ActiveGate use?
- To determine the ActiveGate default directories, names of services, and installer files, see Where can I find ActiveGate files?
- To set up a proxy for private synthetic, monitoring or communication of AWS/VMware/Azure, monitoring Cloud Foundry or Kubernetes, Dynatrace Server communication or for excluding hosts from proxy communication, see Setting up a proxy for ActiveGate
- To set up communication from the Managed cluster back to the ActiveGate via the reverse proxy, see Setting up reverse proxy for ActiveGate
- To customize ActiveGate launcher (set memory limits, JVM settings, port ranges), see Configure ActiveGate launcher
- To configure ActiveGate using a properties file (configure dbAgent, connectivity, proxy, ports, ciphers, memory dumps, aws/vmware/synthetic monitoring, dump storage directory, capabilities), see Configure ActiveGate
- To configure ciphers for SSL communication on your ActiveGate, see How to configure ciphers on ActiveGate
- To configure a Java or custom trusted store, see Configure trusted root certificates on ActiveGate
- To configure a single ActiveGate in support of multiple monitoring environments, see Configure an Environment ActiveGate for multi-environment support
- To configure ActiveGate to use a custom certificate or create a self-signed
PKCS#12certificate file for testing, see Configure custom SSL certificate on ActiveGate