Configure the Java Agent

Note: Configuration files often contain sensitive information, such as access keys, HTTP authentication details, proxy settings, or OAuth credentials. To ensure security, restrict access to these files to the necessary user. Assign ownership of the configuration directory to the JVM owner and apply strict permissions to the configuration files by running the following command:
chmod -R 700 <agent_home>/<version_number>/conf

If you downloaded the agent from the Agent Download Wizard in the Controller, you can skip to the next section, as the agent is already configured.

To configure the settings manually (or verify the wizard settings):

  1. Edit the versioned configuration file:
    <agent_home>/<version_number>/conf/controller-info.xml
    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-premises 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 the Java Agent.
  4. Identify the business application, tier, and node that this the monitored JVM belongs to in the Splunk AppDynamics application model using these settings:
    • application-name
    • tier-name
    • node-name
    In a self-service Trial edition of Splunk AppDynamics Pro, the agent uses a default naming scheme, see Java Agent. You can use automatic naming with a standard edition of Splunk AppDynamics Pro by adding this property: <auto-naming>true</auto-naming>
  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.
    See Java Agent Configuration Properties and configure any additional properties required in your environment.
    • account-name
    • account-access-key
    This information is provided in the Welcome email from the Splunk AppDynamics Team when you acquired the Controller. For a multi-tenant on-premises Controller, you can find this information in <controller_home>/initial_account_access_info.txt
The following shows a controller-info.xml:
<controller-info>
    <controller-host>192.168.1.20</controller-host>
    <controller-port>8090</controller-port>
    <application-name>ACMEOnline</application-name>
    <tier-name>InventoryTier</tier-name>
    <node-name>Inventory1</node-name>
</controller-info>