PDFs

On this page:

 

Search AppDynamics Platform topics:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
12 rates
This section provides information on installing, configuring, and administering an on-premises AppDynamics Platform deployment. 

Installation Overview

Before you install the platform, review the requirements for the components you plan to install and prepare the host machines. The requirements vary based on the components you deploy and the size of your deployment.

You can perform the Controller and EUM Server installations using a package installer that supports interactive GUI or console modes, along with silent, response file installation. For the Events Service, you first install the AppDynamics Platform Administration Application. You then use the Platform Administration Application to deploy the Events Service as a single node or a cluster. 

You can get the software for installing the platform components from the AppDynamics download site. See Download AppDynamics Software for more information.

On-Premises Deployment Architecture

An on-premises AppDynamics Platform installation consists of several separately installed and configured components. These include the Controller, MySQL database, Events Service, and optionally the End User Monitoring (EUM) Server. 

 The following diagram depicts the components of a complete on-premises AppDynamics Application Intelligence Platform deployment. It shows how the components interact to fulfill application, database, infrastructure, end user monitoring, and more.

Depending on the scale of your deployment, your requirements, and the products you are using, your own deployment is likely to consist of a subset of the components shown in the diagram. 

Platform Components

The following table describes how the components work together in the AppDynamics platform.

Product FeatureComponents Involved
Application Performance Management App Server Agents attach to monitored applications and send data to the  Controller via connection A.
Server Visibility Machine Agents reside on monitored servers and report data to the 7 Controller via connection A.
Application AnalyticsThe Analytics Dynamic Service (formerly called the Analytics plugin) on the App Server agent communicates with a local Analytics Agent instance. One or more Analytics Agents in a deployment send data to the Events Service via connection B. The Analytics Agent is bundled with the Machine Agent but can be installed and run individually as well.
Database VisibilityThe  Database Agent connects by JDBC to monitored databases. The agent sends data to the 7Controller (via connection A), which uses the 8Events Service to store certain types of data.
End User MonitoringFor an on-premises EUM installation, you configure a connection to the web and mobile real user monitoring agents to the on-premises 9 EUM Server via connection C. The EUM Server sends data to the 8 Events Service cluster via connection F.

Platform Connections

The following table lists and describes the traffic flow between AppDynamics platform components.

Connection
Source
Destination
Traffic
Protocol
Default Port(s)
A1 AppDynamics users through the web GUI, 2 REST API, 3 Database Agent, 4 Application Server Agent, and 5Machine and Analytics Agents7 ControllerAPM/Database MetricsHTTP(S)8090/8181
B5 Analytics Agent8 Events Service ClusterLog and Transaction Analytics Event DataHTTP(S)9080/9081
C6 Real User Monitoring (RUM) Agents9 End User Monitoring (EUM) ServerEUM Beacon DataHTTP(S)7001/7002
D7 Controller9 EUM ServerEUM Metric DataHTTP(S)8090/8181
E7 Controller8 Events Service ClusterAnalytics Event DataHTTP(S)9080/9081
F9 EUM Server8 Events Service ClusterEUM Event DataHTTP(S)9080/9081
G9 EUM Server7 ControllerMySQL database connection (install time only)TCP3388

Data Storage Location

Data is stored in the following locations:

  • APM configuration and metric data in the on-premise Controller MySQL database
  • EUM configuration and metric data in the on-premise Controller MySQL database 
  • EUM event data in the Events Service
  • Transaction and log analytics data in the Events Service 

 

  • No labels