On this page: Search AppDynamics Platform topics:
On this page:
Search AppDynamics Platform topics:
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.
The following table describes how the components work together in the AppDynamics platform.
|Product Feature||Components Involved|
|Application Performance Management||App Server Agents attach to monitored applications and send data to the Controller via connection .|
|Server Visibility||Machine Agents reside on monitored servers and report data to the Controller via connection .|
|Application Analytics||The Analytics Dynamic Service (formerly called the Analytics plugin) on the via connection . The Analytics Agent is bundled with the Machine Agent but can be installed and run individually as well.App Server agent communicates with a local Analytics Agent instance. One or more Analytics Agents in a deployment send data to the Events Service|
|Database Visibility||The Database Agent connects by JDBC to monitored databases. The agent sends data to the Controller (via connection ), which uses the Events Service to store certain types of data.|
|End User Monitoring||For an on-premises EUM installation, you configure a connection to the web and mobile real user monitoring agents to the on-premises via connection . The EUM Server sends data to the Events Service cluster via connection .EUM Server|
The following table lists and describes the traffic flow between AppDynamics platform components.
|AppDynamics users through the web GUI, REST API, Database Agent, Application Server Agent, and Machine and Analytics Agents||Controller||APM/Database Metrics||HTTP(S)||8090/8181|
|Analytics Agent||Events Service Cluster||Log and Transaction Analytics Event Data||HTTP(S)||9080/9081|
|Real User Monitoring (RUM) Agents||End User Monitoring (EUM) Server||EUM Beacon Data||HTTP(S)||7001/7002|
|Controller||EUM Server||EUM Metric Data||HTTP(S)||8090/8181|
|Controller||Events Service Cluster||Analytics Event Data||HTTP(S)||9080/9081|
|EUM Server||Events Service Cluster||EUM Event Data||HTTP(S)||9080/9081|
|EUM Server||Controller||MySQL database connection (install time only)||TCP||3388|
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