<JavaAgent-Home>\version xxx\confdirectoryand edit
Controller hostname or IP address
The same host you use to access the AppDynamics Controller's browser-based UI (for example
SaaS Controller Host:
On-premises Controller Host:
Controller HTTPS port
The same port you use to access the AppDynamics Controller's browser-based UI:
SaaS Controller Port:
On-premises Controller Port:
Specify whether to connect with SSL (HTTPS) or not
The Agent only connects to the Controller using SSL when you enable this property. Otherwise, it connects using HTTP. If you set <Controller-ssl-enabled> to “true”, then set the controller-port property to the Controller's HTTPS (see step “b”, above).
The logical business application name that the JVM node belongs to, and NOT the deployment name (EAR, WAR, JAR) on the application server.
For example, if monitoring a portal application or "Acme eCommerce", you could name a business application "Acme Portal". If a business application of that name doesn't exist, the Controller will create one.
The logical business tier this node belongs to. For example, a tier could be 'Acme frontend' or 'Acme Backend Service'. If your JVM/app server startup script contains a system property you want to use for the tiername (e.g., '-Dserver.tier'), you can use expressions like
The name for this access node, which must be unique within the business application, e.g., 'weblogicinstance23', or 'hweb24'. If your JVM/appserver startup script contains a system property you want to use for the node name (e.g.,
If you’re running in single-tenant mode (the default), you don’t need to configure this value.
The account access key
—javagaentargument is appended to the startup command for the JVM. The argument should indicate the location of the Java Agent JAR file:
To validate that the Machine Agent is reporting on the Controller, navigate to Settings, then AppDynamics Agents. Click the AppServer Agents tab.