This page provides a high-level view of using the Enterprise Console to install the AppDynamics platform, including the Controller and Events Service.

See Discovery and Upgrade Quick Start for the upgrade quick start guide.

About these Steps

The process described in this page uses the Enterprise Console to perform the following tasks:

  • Install a Demo Controller and embedded Events Service.
  • Install an Events Service that runs on hosts that are separate from the Controller.
  • Switch the Controller to a high availability pair. 

This quick start is intended to introduce you to the Enterprise Console and AppDynamics platform. Before you start, review the requirements pages for the platform components. 

Install the Enterprise Console

  1. Install the Enterprise Console with the following command: 

    Linux

    ./platform-setup-64bit-linux.sh

    Windows

    platform-setup-64bit-windows.exe

    When the installation wizard launches, complete it to install the Enterprise Console. For more information about how to install the Enterprise Console, see Install the Enterprise Console.

  2. Verify that the Enterprise Console successfully installed by opening the GUI using the host and port you specified during installation: 

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

    9191 is the default port.

  3. Complete the installation process with the GUI or command line.

GUI Installation Quick Start

After you install the Enterprise Console, you can complete the platform installation process with the GUI. The following steps describe how to install a Controller with an embedded Events Service. It then describes how to scale up the Events Service to run on a separate host. To install a Controller with a scaled-up (unembedded) Events Service, see Custom Install. 

You can install the Events Service on a separate host directly by selecting a Custom Installation at step 2.

  1. Open a browser and navigate to the GUI: 

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

    9191 is the default port.

  2. Select Express Install to install a Controller and Events Service on a shared host. 
  3. In the Add a Host section, choose Use Enterprise Console Host. This option installs a Controller with an embedded Events Service on the same host as the Enterprise Console.
  4. Choose Demo as the Controller profile if you are just getting to know the system.  
  5. Fill out the Controller configuration fields as indicated. See Express Install for details.  
    You now have a running, testable system and can deploy agents. Next, we'll walk you through the steps for scaling up the Events Service. A scaled-up deployment is strongly recommended for installations meant for something other than for demonstration or exploratory purposes. 

Scale Up the Events Service

In this step, you expand your platform to use a scaled-up Events Service deployment. It is important to note that data is not migrated from an embedded instance to a scaled-up instance.  

  1. In the Enterprise Console UI home page, click on the Platform you created previously. 
  2. Click Hosts in the left navigation menu.
  3. Add a least three hosts for a scaled-up Events Service, providing a host name and an SSH credential that enables the Enterprise Console to access the host.
  4. When finished, go to the Events Service page. 
  5. From the more menu ( ... ), choose Scale Up Events Service.  
  6. In the Scale Up Events Service dialog, choose the Prod profile and select the hosts you created previously from the Host drop-down menu.  
  7. Click Submit. 
  8. Now set up a load balancer for the Events Service hosts, as described in Load Balance Events Service Traffic. 
  9. When done configuring the load balancer, you need to indicate to the Controller the addressable URL for the Events Service. In the Controller Administration Console, set these Controller properties:
    • Set appdynamics.non.eum.events.use.on.premise.events.service to true.
    • Set appdynamics.analytics.server.store.url to the URL of the Events Service as exposed at the load balancer. For example, appdynamics.analytics.server.store.url=http://es-master-host:9080/.

Set Up Controller High Availability

Now that you have a running Controller and Events Service, try setting up high availability for the Controller.

Before proceeding, see Set Up a High Availability Deployment. Specifically, follow the steps indicated in the section on configuring Controller High Availability pair environment in for prerequisites.  

Once you have fulfilled the prerequisites, follow these steps:

  1. In the Enterprise Console UI home page, click on the Platform you created previously. 
  2. Click Hosts in the left navigation menu.
  3. Add a single new host. Provide a hostname and an SSH credential that enables the Enterprise Console to access the host. 
  4. When finished, go to the Controller page. 
  5. Click Add Secondary Controller.
  6. Provide the same passwords as the primary database and Controller root password, and click Submit. 

Now you have two Controllers running in passive-active high availability mode. To complete the configuration, you need to set up a load balancer, so that you can easily switch traffic between the Controllers. See Use a Reverse Proxy. After configuring a load balancer, you would need to specify the URL address for reaching the Controller pair in the Enterprise Console UI by clicking Configurations > Controller Settings > Appserver Configurations, and specifying the URL in the External URL field.  

You now have a functioning platform, consisting of Controller pair and a scaled up Events Service instance.

Install the EUM Server

If using EUM, you can continue by installing an EUM Server. The EUM Server is installed separately, not with the Enterprise Console.

Follow the steps below to get started:

  1. Read an overview of the EUM Server in EUM Server Deployment.
  2. Learn to install and configure the EUM Server by following the instructions in Install a Demo EUM Server.
  3. Install the EUM Server for production.