Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



  1. 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.      
  2. 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   

  3. Direct the agent to connect to the Controller by SSL (HTTPS) by setting the controller-ssl-enabled value to true. See Enable SSL for Java.
  4. Identify the business application, tier, and node that this the monitored JVM belongs to in the AppDynamics application model using these settings:
    • application-name 
    • tier-name 
    • node-name 

    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:

  5. 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.
    • account-name 
    • account-access-key
    This information is provided in the Welcome email from the AppDynamics Team when you acquired the Controller. For a multi-tenant on-premise Controller, you can find this information in
  6. See Java Agent Configuration Properties and configure an additional properties required in your environment.