- For more configuration options, see Java Agent Configuration Properties.
- To configure the Java Agent to use SSL, see Enable SSL for Java.
- To configure the Java Agent to connects to the Controller through a proxy, see "Proxy Properties for the Controller" in Java Agent Configuration Properties.
- Edit the versioned configuration file:
The controller-info.xml is one of several approaches available for supplying configuration settings. For others, see Java Agent Configuration Properties.
- Modify the connection settings to the Controller:
- controller-host: Set to the IP address or hostname of the Controller. If the agent needs to connect through a proxy, see "Proxy Properties for the Controller" in Java Agent Configuration Properties.
- controller-port: Set to the primary listening port number on the Controller. By default:
For a SaaS Controller, use 80 for HTTP or 443 for HTTPS
For an on-premise Controller, use 8090 for HTTP or 8181 for HTTPS
- Direct the agent to connect to the Controller by SSL (HTTPS) by setting the
controller-ssl-enabledvalue to true. See Enable SSL for Java.
- Identify the business application, tier, and node that this the monitored JVM belongs to in the AppDynamics application model using these settings:
In a self-service Trial edition of AppDynamics Pro, the agent uses a default naming scheme, see Instrument Java Applications. You can use automatic naming with a standard edition of AppDynamics Pro by adding the following property:
- If the agents connects to a SaaS Controller or other multi-tenant Controller, configure the Account Name. For all Controllers, configure the Account Access Key.
- See Java Agent Configuration Properties and configure an additional properties required in your environment.