Plan the Machine Agent Configuration

Splunk AppDynamics provides multiple ways to configure the Machine Agent. As part of planning your installation, determine which options work best in your environment:

  • Controller-info.xml
  • System properties
  • Environment variables

See Configure the Machine Agent.

Collect Configuration Information

Determine your configuration requirements and collect the necessary information. See Machine Agent Configuration Properties.

Planning Item Description
Determine your installation scenario

For new installations, see Machine Agent Installation Scenarios.

For upgrades, see Upgrade the Machine Agent.

Location of the startup script

You add startup arguments and system properties in the startup script. If you are using a Java service wrapper, you need to know the location of the wrapper configuration. See Where to Specify Machine Agent Configuration.

Memory and CPUSee Machine Agent Requirements and Supported Environments.
Connecting the agent to the Controller

You need to know the Controller host, Controller port, and account access key where you want your metrics to be reported. The account access key is generated at the Controller installation time and is located on the Splunk AppDynamics Administration Console.

(Optional) SSL Communications

If you plan to use SSL to communicate with the Controller, see Enable SSL for Machine Agent. SSL-related properties include:

  • Controller SSL Enabled Property
  • Controller Keystore Password
  • Controller Keystore Filename
  • Force Default SSL Certificate Validation
Proxy Settings

If you plan to connect to the Controller using a proxy server, you need to know the Proxy host, Proxy port, and the path to the Proxy Password file.

Multi-tenant mode or SaaS Installations

In addition to the Account Access property, use the Account Name property to configure multi-tenant mode or SaaS account Information. This information is provided in the Welcome email from the customer support Team. You can also locate this information in the <controller_home>/initial_account_access_info.txt file.

Deploying from a common directorySee Deploy Multiple Machine Agents From a Common Directory.
Extension considerationsIf you plan to use a number of extensions in your environment, see the "Extension Considerations" section in Machine Agent Requirements and Supported Environments.
Enabling Server Availability and Service Availability MonitoringServer Availability requires a separate license. See Enable Server Visibility.