On this page:
Though the Enterprise Console can run on the same host as the Controller and, if installed, the embedded Events Service, it is recommended that you install it on a separate host. However, in any case, the machine you choose to run the Enterprise Console must meet the requirements for all the components that run on that machine, as outlined below. While they may run on the same machine, the Enterprise Console runs on a separate MySQL instance than the Controller. This allows the Enterprise Console to manage the Controller's instance, independent from the Controller host, creating a lightweight setup that consumes less memory.
|If you do install the Enterprise Console on the Controller machine, it needs to be in a separate directory. This is because the Enterprise Console data directory needs to be in a separate folder from the Controller data directory. If the Controller is installed in |
You also need to avoid port conflicts with the Controller database, which is 3388 by default, whereas the Enterprise Console database is 3377 by default.
The Enterprise Console installation path you choose must be writeable, i.e. the user who installed the Enterprise Console should have write permissions to that directory.
The Enterprise Console prevents multiple users from running commands at the same time. If a second user attempts to run a command while another command is in progress, the second command is not completed and an error message appears indicating that another command is in progress. To avoid such conflicts, the Enterprise Console should generally be used by a single user at a time.
You can enable HTTPS for the Enterprise Console during installation. See HTTPS Support for the Enterprise Console for more information.
|Cross platform (OS) installation, e.g., installing the Enterprise Console on Linux and the Controller on Mac or Windows, is not supported.|
When installing the Enterprise Console on an AWS host, you must add the values for the following host names and IP addresses to the SAN:
Public DNS (IPv4)
IPv4 Public IP
The host must have enough disk space for the Enterprise Console and a platform, which includes a Controller. There is no need for additional memory for the Enterprise Console when it shares the same host as the Controller. However, when the Enterprise Console host is not shared with the Controller host, then it requires additional disk and memory space. See Enterprise Console Requirements and Prepare the Controller Host to make sure you meet the minimum space requirements.
On systems that run Linux, you must have cURL and netstat installed. Linux systems must also have the libaio library installed. This library provides for asynchronous I/O operations on the system.
The following table shows how to install libaio on some common flavors of the Linux operating system.
|Red Hat and CentOS|
Run the following command: yum install libaio
Run the following command: sudo apt-get install libaio1
|Fedora||Install the libaio RPM from the Fedora website: yum install libaio, or yum install numactl|
|Debian||Use a package manager such as APT to install libaio (as described for the Ubuntu instructions above).|
Before starting, get the Enterprise Console installer version appropriate for your target system. You can get the installer from the AppDynamics download site. When ready, follow these steps to install the Enterprise Console:
Run the following commands:
You can run the installer as non-root or root.
It is recommended that you right-click the .exe file and select Run as Administrator.
After the GUI launches, use it to complete the installation. In Linux, you may also follow the steps in the installation wizard to complete the console installation.
|If you install the Enterprise Console on AWS, use the public DNS for the Enterprise Console host name when prompted.|
To use the silent installation method, add the -q option, the response file, and destination directory to the command to run the installer. For example, in Linux, run the following command:
./platform-setup-64bit-linux.sh -q -varfile ~/response.varfile
It is recommend that, if possible, you provide an absolute path as the installation path specified as the
dir argument value, and not a relative path as shown in the example.
For a Windows system:
platform-setup-64bit-windows.exe -q -varfile c:/response.varfile
After the Installation
After you install the Enterprise Console, you can use the following methods to install the AppDynamics Platform:
After installing the Enterprise Console, you can select from the Express Install or Custom Install of the platform, which includes the option to install a Controller. For more information about those options, see Enterprise Console.
For information on installing the Controller or Events Service in unattended mode or via the command line, see Enterprise Console Command Line.
Access the GUI for the Enterprise Console with the following URL:
Specify the port and hostname you used when you installed the Enterprise Console. The default port is 9191. This port needs to be exposed from your firewall rules so you can access the port from any place. See Port Settings for more information.
With the GUI, you can install and manage the components of the AppDynamics platform, including tasks such as adding hosts or credentials, installing a Controller, and monitoring jobs.
If you cannot access the GUI, verify that the host name and port number are correct. Additionally, ensure that the Enterprise Console is running.
The first time you access the GUI, the Enterprise Console shows the following options for installing the AppDynamics Platform:
Custom: Select this option to customize your installation, including installing or upgrading the Controller and Events Service on separate hosts. By installing the Events Service on a separate host, you can create a 1 or 3+ node Events Service based on your needs. Installing an Events Service on a separate host with the Enterprise Console is only supported on Linux. If you want to install the Events Service on a separate host on Windows, see Install the Events Service on Windows.
The Events Service is installed by default with a Custom Installation unless you choose to unselect the Install Events Service option.
Discover and Upgrade: When performing a custom installation, you have the option to discover and upgrade an existing AppDynamics deployment, such as a Controller or Events Service. For example, if you use the package installer to install the Controller in a previous version of AppDynamics, you can use the discover and upgrade option to add the Controller to the AppDynamics platform that the Enterprise Console manages. The application will then upgrade the Controller to the same version of the Enterprise Console. Verify that the Controller and MySQL are running before you attempt to discover and upgrade them.
This section provides troubleshooting information for issues that may arise during Enterprise Console installation.
If your Enterprise Console installation fails on a Red Hat system, it may be due to an install4j issue. If the default font has been changed, the JRE cannot interpret it, leading to a "could not display the GUI" error. You can fix this error by running the installation with
-VdisableEULA=true and creating the file
/etc/fonts/local.conf with the following contents:
If your installation becomes stuck at displaying the license agreement on the console, then the EULA may be having issues with special characters. To fix this issue, add the
-VdisableEULA=true flag to your installation command or response.varfile. For example:
./platform-setup-64bit-linux.sh -c -VdisableEULA=true
If the Enterprise Console installation fails with an error "on rename of the directory," it may be due to an antivirus scan. Stopping the antivirus scan on the machine fixes the issue. You should also exclude the Enterprise Console directory from the scan if it sits outside of the Controller directory. See Prepare Windows for the Controller for more information.
For full-screen viewing, click Installing Enterprise Console.