- In the Welcome screen click Next.
The license agreement displays.
- Scroll down to the bottom and accept the license agreement, then click Next.
- Click Yes to grant or No to deny AppDynamics permission to collect usage data statistics from your controller.
The data collected helps AppDynamics improve its products and services.
- Set the path of the Controller installation directory in the Destination directory field, then click Next.
- Enter the password for the database user that the Controller will use to access the database where it stores its data. The installer creates a user account named root in the database with the password you specify.
- In the Application Server Host Name field type the host name (or IP address), or accept the default.
- Verify the port numbers to be used by the Controller. To change a default port, click Edit Ports and enter the new port number.
Note that the installer checks the availability of each port on the target machine before suggesting it. If a default port number is already in use, it chooses the next highest available number for the port. For example, if the usual default port of 8090 for the Controller application server is taken, the installer suggests 8091. You only need to edit a default port number if you know it will cause a future conflict or if you have some other specific reason for choosing another port.
Examine the default configuration of the internal Controller ports and modify the settings as necessary if other services are bound to these ports. Then click Next.
- Verify the displayed configured settings and click Back if you want to change any of them. Click Next to continue.
- Choose single-tenant or multi-tenant mode for the Controller, then click Next.
See Controller Tenant Mode for more information about these modes.
- Enter the password for the root user account in the Controller.
The Controller root user is a special type of administrative account that has global privileges in the Controller. The root user credentials let you access the global AppDynamics administration console, where you can create and manage AppDynamics accounts and configure other Controller-wide settings. See Access the Administration Console for more information about the console.
- Configure initial account settings, as follows:
- If you selected single-tenancy mode, enter the username and password for the administrator of the built-in account.
- If you selected multi-tenancy mode:
- Enter a name for the initial account in the system, along with a username and password for the administrator for the initial account.
- Review and record the settings for the initial account settings and click Next.
You will need to configure the App Agents with this account key and account name to associate the application with a particular account.
- Select the Controller performance profile that matches your requirements, then click Next.
Note that only Demo and Small profile deployments are available for installation on 32-bit systems. When you click Next, the installer checks your system for minimum requirements and warns you if any are not met.
- In the data directory settings, enter the path to the MySQL data directory and to the Elastic Search data directory and then click Next.
The Controller stores configuration and metric data in the directory indicated in the MySQL data directory field. You can accept the default location or enter another location for the data. The Elastic Search data directory is used by Database Monitoring features. If you are storing MySQL data outside the default location, say in a separate disk partition, it is likely that the Elastic Search data directory would need to be put in the same location. If you are not sure whether you will use database monitoring, you can keep the default location for now and change the data directory location later, if needed, in the events_service\analytics-processor\conf\analytics-all.properties file.
- Select the high availability configuration for the Controller or Not Applicable if you are not enabling HA for this Controller. Then click Next. For more information see Manage Controller High Availability.