On this page:

 

Search AppDynamics Platform topics:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
17 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.

For the Controller and Events Service, you first need to install the AppDynamics Enterprise Console. You then use the application to deploy the Controller and Events Service. Note that the Events Service can be deployed as a single node or a cluster. The Enterprise Console is the installer for the Controller and Events Service, and you can use it to manage the entire lifecycle of new or existing AppDynamics Platforms and components.

You cannot use the Enterprise Console to perform the EUM Server installation. Instead, you must use a package installer that supports interactive GUI or console modes, or a silent response file installation.

Follow these tasks before you start the installation process for the AppDynamics Platform:

  • Review the Platform Requirements.
  • Verify the Enterprise Console host meets the requirements to host the application and the Controller since they share the same host by default for Express Install. You do have the option to install the Enterprise Console on a different host than the Controller's.
  • On Linux, verify that you have assigned execute permissions to the installation script with the following command:

    chmod 775 platform-setup-64bit-linux.sh

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

AppDynamics Platform Components and Tools

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 AppDynamics Enterprise Console is a GUI and command-line based application that can manage the installation, configuration, and administration of the Controller and Events Service.

For the EUM Server, you must continue to use the package installer to deploy the EUM Cloud.

After you install the platform, you can configure and manage different components with component-specific scripts. Based on how you deploy the platform, you might use a combination of the Enterprise Console and package installers to install and manage the various components of the platform.

On-Premises Deployment Architecture

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.

You can find a more detailed diagram, as well as a SaaS architecture diagram on PDFs.

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 G. The optional Custom EUM Geo Server stores EUM Geo Resolution data taken via connection .

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 Cluster

Log and Transaction Analytics

Event Data

HTTP9080
C6 Real User Monitoring (RUM) Agents9 End User Monitoring (EUM) ServerEUM Beacon DataHTTP(S)7001/7002
D6 Real User Monitoring (RUM) Agents Custom EUM Geo ServerEUM Geo Resolution Mapping DataHTTP(S)80/443
E7 Controller9 EUM ServerEUM Metric DataHTTP(S)

7001

7002 (demo mode only)

F7 Controller8 Events Service ClusterAnalytics Event DataHTTP(S)9080/9081
G9 EUM Server8 Events Service ClusterEUM Event DataHTTP(S)9080/9081
The default port 9081 is the Admin port (HTTP).

Data Storage Location

Data is stored in the following locations:

  • APM 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 
  • EUM Geo Resolution data in the on-premise GeoServer.

Installation and Upgrade Overview

The installation and upgrade process for the AppDynamics platform consists of pre-installation steps where you prepare the network and host machines for installation, installation tasks, and post-install steps to complete the required configuration. The Planning Your Deployment provide a high-level review of the steps required.

After this process, you can perform optional configurations and administrative tasks described in Secure the Platform

To start the installation or upgrade process, see Platform Requirements for information about requirements and pre-installation tasks.


 

  • No labels