Custom Configuration

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

If you require to use a non-root user and group for installing the supported agents, specify the following in Custom Configuration:

user: <username>
group: <groupname>

Apache Web Server Agent Configurations

For the list of all the supported custom configurations for Apache Web Server Agent, see Apache エージェントの Ansible 設定.

Java Agent Configuration

For the list of all the supported custom configurations for Java Agent, see Java エージェントの Ansible 設定.

Machine Agent

By default, Machine Agent runs as a service. To run it as a process, specify the following in Custom Configuration:

start_as_process: true
start_as_service: false

For the list of all the supported custom configurations for Machine Agent, see マシンエージェントの Ansible 設定.

To install and start Machine Agent automatically, you require the autostart_agent setting.

On the Set Agent Attributes page, you can configure the autostart_agent setting in Custom Configuration:


Setting	Description
`autostart_agent: true`	This is the default setting. This installs and starts the Machine Agent automatically. When the agent is configured to run as a service, these are the requirements: Windows: admin privileges are required on Windows to start Machine Agent as a service. Linux: root privileges are required to install Machine Agent as a system service. If Smart Agent runs as a non-root user, Machine Agent is installed as a user service that runs under the same user account as the Smart Agent.
`autostart_agent: false`	Installs the Machine Agent, but does not run the agent. When the agent is configured to run as a service, the service is not created. To create the service later, run the InstallService.vbs. `cscript <machine_agent_install_dir>\InstallService.vbs <jvm_options>`

Note: Custom extensions specified in the monitor.xml file are retained during both installation and upgrade processes.

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

For more information about AD_Setup, see .NETの無人インストール.

Note: For the .Net Agent installation through the Custom HTTP, Install Version is a required field.

Node.js Agent

For the list of all the supported custom configurations for Node.js Agent, see Node.js エージェントの Ansible 設定.

PHP Agent

For the list of all the supported custom configurations for PHP Agent, see PHP エージェントの Ansible 設定.

Python Agent

For the list of all the supported custom configurations for Python Agent, see Python エージェントの Ansible 設定.