Related pages:

You can choose Express Install on the Install page when you first use the Enterprise Console or when you want to create a new platform. This install option provides you with a quick and simple way to install a fresh single node Controller and embedded Events Service.

This page guides you through the steps to perform an Express Install. Before you install the Controller with the Enterprise Console, verify that the Enterprise Console is running and the host machine meets the requirements for the Controller.

If you use the GUI to install the Controller, you can create the platform at the same time. If you use the command line, you must create the platform prior to installing the Controller. For more information, see Administer the Enterprise Console. Express Install does not give you the option to choose the version you would like to install, and instead automatically installs the latest version of each service. If you would like more control over your installation, see Custom Install.

Install the Platform Using GUI

Express Install is the quickest way to get started with setting up your own Cisco AppDynamics On-Premises Platform. You can use it to install the Controller and an Events Service on a single host.

After you install the Enterprise Console, you can complete the platform installation process with the GUI:

  1. Check that you have fulfilled the Enterprise Console prerequisites before starting.

  2. Open a browser and navigate to the GUI: 

    http(s)://<hostname>:<port>

    9191 is the default port.

  3. Select Express Install to install a Controller and Events Service on a shared host.

  4. Enter a Name and the Installation Path for your platform.

    The Controller cannot be installed on a different drive using the Enterprise Console for Windows. 

    The Installation Path is an absolute path under which all of the platform components are installed. The same path is used for all hosts added to the platform. Use a path which does not have any existing Cisco AppDynamics On-Premises components (Controller, Events Service, etc.) installed under it.
    The path you choose must be writeable, i.e. the user who installed the Enterprise Console should have write permissions to that folder. Also, the same path should be writeable on all of the hosts that the Enterprise Console manages.

    Example path: /home/appduser/appdynamics/product

  5. Add a host by entering host machine-related information: Host Name, Username, and Private Key. To add the Enterprise Console host, click Add Enterprise Console Host, which will automatically populate the text field with the hostname of the Enterprise Console machine. You do not need to provide a credential. The Controller and Events Service will be installed on the same host as the Enterprise Console.

    If the Controller is to be installed on a Windows machine, the Enterprise Console should be on the same machine. This is because Windows hosts are not supported on the Enterprise Console.

    If you use the Enterprise Console host to install the Controller, then no Username or Private Key is required. You can also install the Controller and Events Service on a remote host. In that case, the Username and Private Key of the remote host would be required.

    As of OpenSSH version 7.8, the ssh keys generated are in OpenSSH format using Ed25519. However, the Enterprise Console expects the ssh keys to be formatted using the older pem format.

  6. Install the Controller:
    1. Select a Profile size for your Controller. See Controller System Requirements for more information on the sizing requirements.
    2. Enter the required Username and Passwords. The default Controller Admin Username is admin.
  7. Click Install.

After clicking Install you can monitor the status of your platform creation jobs on the Jobs page, which include Add Hosts, Controller Install, and Events Service Install Jobs. Note that the Controller Install Job takes a considerably longer time to complete than the other two jobs. When the jobs successfully complete, you can check the status of your platform, obtain the URL of the Controller, update platform configurations, and manage the lifecycle of your services.

See Install the Events Service on Linux for additional setting requirements and to learn how to scale up an embedded Events Service.