You can install agents on a machine by using the UI only if Smart Agent is installed on the same machine.

Perform the following to install the supported agents:

  1. Click Home > Agent Management > Manage Agents
  2. Click Install Agent in the right pane
  3. Select the type of agent and then click Next
  4. Select one of the following to specify the location for deploying the Agent, then click Next.
    • Select from List: You can select the host on which Smart Agent is installed from the list, then click the left arrow to list it under selected table. You can select multiple hosts.
      You can add multiple agents for a single host and multiple hosts can be selected by repeating this step.

    • Import from CSV file: You can upload a CSV file with required columns such as HostName, SmartAgentID, Application, Tier, Node, and Installation Directory.
  5. Select Custom Prefix if you want a prefix to be added to the application, node and tier names, else proceed with specifying the application details.
  6. Configure the agent attributes on the Set Agent Attributes page, then click Install.
    1. You can select the download source. The source can be the AppDynamics download portal (Using AppDynamics Portal), your local directory (Using Local Directory), or your custom HTTP server (Custom HTTP URL).
      If you select:
      • Using AppDynamics Portal, select the appropriate install version.
      • Custom HTTP URL, and if your HTTP server requires authentication, configure smart agent to use basic authentication. See Configure Authentication for Custom Artifact Location.
      • Using Local Directory, specify Local Directory as the path where you have downloaded the zip file.
    2. You can select Additional Configuration to add more configuration details. Use the agent specific custom configurations to specify in Custom Configuration. For the list of keys that you can use, see Custom Configuration. 
      For .NET MSI, you can configure only Custom AD_Setup file content. See Additional Configuration for .NET MSI.

  7. Check the install status in Tasks in Progress.
    You can search for the specific host and check the log file. After the task is completed the task is added to the History tab.

    The log file is generated after the task is complete.

Configure Basic Authentication for Custom Artifactory Location

You require to configure Smart Agent to use basic authentication if your HTTP server requests authentication. When you configure Smart Agent to use basic authentication, it communicates with the HTTP sever, such as Nexus, Artifactory, or any custom HTTP server.

To configure basic authentication, include the following variables in the [AnsibleConfig].EnvVars section of the Smart Agent config.ini file:

  • ENABLE_CUSTOM_HTTP
  • CUSTOM_HTTP_USERNAME
  • CUSTOM_HTTP_PASSWORD

For example,

[AnsibleConfig]
ExtraVars = create_appdynamics_user=false,add_ansible_install_env_var=false,check_pkg_dependencies=false,download_script=py
EnvVars = ANSIBLE_STDOUT_CALLBACK=appdynamics.agents.smartagent_callback,ENABLE_CUSTOM_HTTP=true,CUSTOM_HTTP_USERNAME=<username>,CUSTOM_HTTP_PASSWORD=<password>
CODE

If you are using Smart Agent CLI, specify the variables before running the appd binary:

sudo env ENABLE_CUSTOM_HTTP=true CUSTOM_HTTP_USERNAME=<username> CUSTOM_HTTP_PASSWORD=<password> ./appd install …
CODE

You can specify the agent_source_location as the extra variable that administrator can specify for the custom URL when using the Smart Agent CLI.

sudo env ENABLE_CUSTOM_HTTP=true CUSTOM_HTTP_USERNAME=<username> CUSTOM_HTTP_PASSWORD=<password> .
/appd install <agent-type> —extra-vars agent_source_location=<path-to-agent-zip-from-custom-url>
CODE


Custom Configuration

You can add additional custom configurations for a required agent under Additional Configuration>Custom Configuration to apply those for the agent installation.

Apache Web Server Agent Configurations

For the list of all the supported custom configurations for Apache Web Server Agent, see Ansible Configuration for Apache Agent.

Java Agent Configuration

For the list of all the supported custom configurations for Java Agent, see Ansible Configuration for Java Agent.

Machine Agent

For the list of all the supported custom configurations for Machine Agent, see Ansible Configuration for Machine Agent.

.NET MSI Agent Configuration

You can include the following setting as the additional configuration for .Net MSI applications under Additional Configuration:

Custom AD_Setup file content: This is the content of AD_Setup file that will be used during the .NET MSI installation. The format of this content is a template that accepts the variables like controller host, port, and so on. The following is an example of a minimal valid ad_setup file with all possible variables:

<?xml version="1.0" encoding="utf-8"?>
<winston>
<appdynamics-agent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <controller host="{{.ControllerHostName}}" port="{{.ControllerPort}}" ssl="false" enable_tls12="false">
    <account name="{{.AccountName}}" password="{{.AccountAccessKey}}"/>
    <application name="{{.ApplicationName}}" />
  </controller>
  <machine-agent />
  <app-agents>
    <IIS>
      <automatic />
    </IIS>
  </app-agents>
</appdynamics-agent>
</winston>
CODE

For more information about AD_Setup file content, see Unattended Installation for .NET.

Node.js Agent

For the list of all the supported custom configurations for Node.js Agent, see Ansible Configuration for Node.js Agent.

PHP Agent

For the list of all the supported custom configurations for PHP Agent, see Ansible Configuration for PHP Agent.

Python Agent

For the list of all the supported custom configurations for Python Agent, see Ansible Configuration for Python Agent.