AppDynamics Application Intelligence Platform
This topic describes how to perform a silent installation of the Controller using a response file. A response file installation does not require user interaction.
Before performing a silent install of the Controller, read the system requirements and prerequisites:
After ensuring that your system meets the requirements, you can perform the installation.
On Linux, enter:
On Windows, open a command prompt window as administrator and enter:
In the sample commands, the -q switch directs the installer to run in unattended mode, while -varfile points to the response file to use.
To view other options for unattended installation, pass only the -h switch to the installer.
Configure your installation using these response file settings:
Server host name or IP address that AppDynamics agents and the AppDynamics UI use to connect to the Controller. Note that "localhost" and "127.0.0.1" are not valid settings.
The primary HTTP port for the application server. If not specified, the installer uses the default, 8090.
The database port. If not specified, the installer uses the default, 3388.
The application server's administration port. If not specified, the installer uses the default, 4848.
The application server's JMS port. If not specified, the installer uses the default, 7676.
The application server's IIOP port. If not specified, the installer uses the default, 3700.
The secure HTTP port for the application server. If not specified, the installer uses the default, 8181.
The performance profile type for the instance: demo, small, medium, large, or extra-large. See Controller Hardware Requirements for information about how the types correspond to sizes.
The tenancy mode: single or multi. Single tenancy is recommended for most installations. See Controller Tenant Mode for more information.
The high availability mode for this instance: primary, secondary, or notapplicable. If not specified, defaults to notapplicable, which means that HA is not enabled.
Your AppDynamics account name. Ignored if controllerTenancyMode=single.
Your AppDynamics account access key. Ignored if controllerTenancyMode=single.
The Controller root user password. The root user is a Controller user account with privileges for accessing the system Administration Console. New in 3.8.4 This password is used for the admin user of the built-in Glassfish application server as well. The Glassfish admin user lets you access the Glassfish console and the asadmin utility.
The root user password repeated for validation purposes.
The username of the initial administrator account in the Controller UI. Ignored if controllerTenancyMode=multi. See AppDynamics Administrator.
Usernames and password cannot include the @ character. Also, if this account will be used to access the REST API, additional limitations on the use of special characters in usernames apply. See Configure Users for more information.
The password for the admin user. You will need this to log into the AppDynamics web UI, where you can create other administrative users and change the password. Ignored if controllerTenancyMode=multi.
The admin user password repeated. Ignored if controllerTenancyMode=multi.
Directory in which to install the Controller. If not specified, it is installed into the default directory of the target environment, such as AppDynamics/Controller under the user's home on Linux systems.
Set to true or false to specify whether to permit data statistics collection from your controller.
The password of the user account that the Controller uses to access its MySQL database.
To avoid a script execution issue, do not use the "!" character in this password.
The path to the Controller's data directory.
The path to the Elastic Search file store. Elastic Search is used by Database Monitoring features. By default, the directory is located in the Controller home. However, if you are putting the MySQL data directory in an alternate location, such as on a separate partition, the Elastic Search data directory would likely need to be put there as well.
The following listings show sample response files for Linux and Windows systems.
The following sample shows a response.varfile for Linux systems:
On Windows, you need to escape the colon and backslashes in the directory paths in the response file.
The following sample shows a response.varfile for Windows systems: