This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


On this page:

Related Pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
60 rates

This page describes how to get up and running with AppDynamics Application Intelligence Platform quickly. This consists of two general steps:

  • Arranging for a SaaS Controller or installing an on-premise Controller in your environment
  • Deploying AppDynamics app agents to the monitored nodes

If you are using a SaaS Controller, the Controller is installed and administered for you, so you only need to install AppDynamics application agents in your monitored environment. You can jump ahead to Install the Agents for information on installing agents.

Install the On-Premise Controller

The Controller download package includes an installer that gets the Controller installed and running in just a few minutes. The Controller works on Linux or Windows operating system, among other. There are a few pre- and post-installation notes to observe for the different operating systems, as described in the following sections.

These instructions assume you are installing a demonstration or small profile environment (up to 10 monitored nodes or units). For information on installing AppDynamics for a large profile environments, see Installation and Administration

Requirements for Trial and Small Profile Settings

The system requirements for the Controller machine depend upon the number of app agents and the amount of activity in your environment. The requirements for small and demo profiles are:

 

Controller 
performance 
profile
Supported OS platformsCPU # of coresRAMDisk storageDisk I/O 
write/read/random read
Agent CountMetrics Count/minute
DemoLinux (32 & 64-bit) 
Windows (32 & 64-bit)
2 CPU Cores  
1.5 GHz minimum
2 GB50 GB50 MB/sec 
50 MB/sec 
1.5 MB/sec
up to 55 K max
SmallLinux (32 & 64-bit) 
Windows (32 & 64-bit)
4 CPU Cores  
1.5 GHz minimum
4 GB100 GB50 MB/sec 
50 MB/sec 
1.5 MB/sec
6-1025 K  max

For details on operating system version support and requirements for other profiles, see Controller System Requirements

If you will be adding AppDynamics product modules to the installation, such as an on-premise EUM instance or Database Monitoring, there are additional components to install and typically, additional system resource requirements to observe. See the documentation for those product modules for specific information. 

Network Requirements

AppDynamics requires the following network configurations:

  • Every app agent, and therefore every server on which an agent is installed, needs to be able to communicate with a Controller using HTTP(S) on a port of your choosing (8090 and 8091 are the defaults). For SaaS, use 80 or 443. 
  • The Controller must be able to access the internet on port 443 to enable AppDynamics' End User Monitoring feature, because it retrieves aggregated web view stats from agg.eum-appdynamics.com.
  • AppDynamics for Databases must be able to connect as a JDBC client to the database to be monitored, and be accessible on its HTTP listen port from browsers used to view its UI.

Linux Notes 

  • The Controller requires that libaio be installed on the machine prior to installation. See information on installing libaio on Linux in Configure Linux for the Controller.
  • Make sure the file descriptor limit is set to at least 65535. See information on limiting file descriptors on Linux in Configure Linux for the Controller
  • After downloading the installer, change the access permissions for the installer file to permit execution.

Windows Notes

  • Verify that you have administrative privileges on the Windows machine to launch the Controller installer.
  • The Controller is automatically installed as a Windows service. See Install the Controller for information on starting and stopping the Controller as a service. 

  • After installation, the you should configure virus scanning and indexing on the system to exclude the Controller data directory. See the operational guidelines in Configure Windows for the Controller for more information about excluding the Controller data directory from virus scanning and indexing services on Windows.

Start the Installer

After downloading the installer, run it as follows:

On Microsoft Windows: 

  1. In the Windows Start menu, right-click on the Command Prompt icon and choose Run as administrator

  2. At the command line, navigate to the download directory and execute the installer .exe file. For example: 

    controller_32bit_windows.exe

On Linux:

  1. Open a terminal and, from the command line, navigate to the download directory. 
  2. Run the Controller installer .sh file. For example, from the download directory, enter: 

    ./controller_64bit_linux.sh

    By default the installer tries to start in GUI mode. If the system does not have a GUI desktop, the installer starts in console mode. You can force the installer to start in console mode by passing the -c option to the installer. The following steps assume the installer is in GUI mode.

Once the installer starts, follow the on-screen instructions to complete the installation. The installer presents you with a number of options for the initial configuration of the Controller. For a demonstration or small profile installation, we suggest the following options:

  • For the tenancy mode, you can choose single-tenancy mode. Most installations are single tenancy. If you're not sure which you want to use, you can change your environment to multi-tenancy later.  
  • You'll need to create a few user accounts. These include: 
    • Database user
    • Root user for the Controller
    • Account administrator for the Controller
    The database user is the one that the Controller uses to access the embedded MySQL database. The root user for the Controller can be thought of as a super user for the Controller. That's the account you can use to access global or advanced settings in the Controller. 
  • The account administrator is an administrative account in the Controller UI. This is the user who would normally create additional users in the Controller. 
  • Select the Demo or Small performance profile when offered the choice of profiles. The installer will check your system for minimum requirements based on the profile. 
  • In the High Availability screen, choose Not Applicable for a demonstration installation. 

When you are done with the configuration settings, the installer copies files to the target machine and starts up and configures the Controller and the Controller database. This can take some time. When it's done, the installer presents you a page with a link where you can access the Controller UI.

Click the link and use the credentials you configured during installation for the administrator to log in. To access the UI manually, from a browser go to the follow URL: 

http://<controller_host>:8090

8090 is the default primary port number for the Controller UI (as well as the port used by app agents). If, during installation, you needed to change the port number or the installer discovered that 8090 was taken and suggested another port number (incrementing by 1 until it finds an available port), adjust the URL accordingly.

Install Agents

After you set up your Controller, you can get the agent software from the Download Agent Wizard in the Controller UI. 

In the wizard, you configure a few settings for the agent. Notably you specify the application name, tier name, and node name. If you're not sure what to use for these values, you can bypass the settings for now. If you don't enter values, the agent will provide default values for these settings.

You can now see the activity in your environment in the Controller UI. 

 

  • No labels