AppDynamics Administration (5.24 MB)

AppDynamics Pro DocumentationVersion 3.8.x

AppDynamics Administration

AppDynamics Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Release Notes for AppDynamics Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Agent - Controller Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Install and Upgrade AppDynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Quick Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Install the Pro Trial Controller on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Install the Pro Trial Controller on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Quick Install for the App Agent for Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Quick Install for the App Agent for .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Quick Install for the App Agent for PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Quick Install for the Standalone Machine Agent . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Supported Environments and Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Install the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Controller System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Controller Sizing FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Measuring Disk Performance Using a Script . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Install the Controller on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Install libaio on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configure File Descriptor Limits on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Configure Swappiness on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Install the Controller on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Install the Controller as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Install an On-Premise Controller Silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Controller Install and Admin FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Install Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Name Business Applications, Tiers, and Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Install App Agents from the AppDynamics Download Zone . . . . . . . . . . . . . . . . . 136 Automate Multi-Agent Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Install the Standalone Machine Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Configure the Machine Agent to Automatically Start on Linux . . . . . . . . . . . . . 141 Configure the Machine Agent to Automatically Start on Windows . . . . . . . . . . 143

Controller Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Connect the Controller and Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Upgrade the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Uninstall the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Migrate the Controller between Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Administer the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Access the AppDynamics UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Access the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Start or Stop the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Controller Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Modify GlassFish JVM Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 User Authentication and Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Administrative Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Configure Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Configure Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Configure Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

View Predefined Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Configure Custom Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Assign Roles to Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Configure Authentication Using LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Configure Authentication Using SAML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Disable SAML Authentication for an Account . . . . . . . . . . . . . . . . . . . . . . . . . . 194 SAML Configuration for OneLogin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Controller Data and Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Controller Data Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Controller Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Controller Disk Space and the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Database Size and Data Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Export and Import Business Application Configurations . . . . . . . . . . . . . . . . . . . . . . . 210

Controller Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Internationalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Controller Tenant Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Customize System Event Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Controller Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Controller Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Administer Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Metrics Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

App Agent Node Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 App Agent Node Properties Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

App Agent Node Properties Reference by Type . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Manage App Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Administer Machine Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Machine Agent Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Modify Machine Agent Data Collection Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Machine Agent Install and Admin FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Configure Multiple Standalone Machine Agents for One Machine for Java . . . . . . 268 Supported Environments and Versions (Standalone Machine Agent) . . . . . . . . . . 270

Remove Unused Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Agent Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Overview of Agent Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 Request Agent Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Agent to Controller Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Deploy AppDynamics in the Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Implement Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Controller SSL and Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Configure the Security Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Controller Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Deploy with a Reverse Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Controller High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Manage Controller High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Controller HA Failover and Failback Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Automating HA Controller Failover and Failback . . . . . . . . . . . . . . . . . . . . . . . 320

Controller High Availability FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Provisioning Controllers in High Availability Mode by Script . . . . . . . . . . . . . . . . . 324

Setting Up an SSH Key for Controller Provisioning . . . . . . . . . . . . . . . . . . . . . 327 Configure the SMTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

AppDynamics for Large Enterprises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Configuring a Controller Environment for the Large Enterprise . . . . . . . . . . . . . . . 331

Automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Workflow Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Create a Workflow and Workflow Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Add Tasks for Workflow Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Available Task Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

Custom Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Cloud Computing Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Compute Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Create Your Own Compute Cloud Connector . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Machine Images and Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Supported Compute Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Copyright AppDynamics 2012-2014 Page 5

AppDynamics AdministrationThis section provides information on installing, setting up, and administering the AppDynamicsController, App Agents, and Machine Agents. This information is targeted for systemadministrators and installers of the AppDynamics Pro products.

Administration Topics

This section covers the following topics:

Release Notes for AppDynamics ProInstall and Upgrade AppDynamicsAdminister the ControllerAdminister AgentsDeploy AppDynamics in the EnterpriseAutomation

Administration Topics for SaaS Controller

While some topics in this section apply to on-premise Controllers exclusively, many topics arerelevant to AppDynamics Pro SaaS users as well. In particular these pages, along with their childpages, are likely to be of interest to administrators and account owners for AppDynamics ProSaaS Controllers:

Agent - Controller Compatibility MatrixInstall AgentsConnect the Controller and AgentsAccess the AppDynamics UIUser Authentication and PermissionsInternationalizationAdminister AgentsExport and Import Business Application ConfigurationsAutomationAppDynamics for Large Enterprises

Release Notes for AppDynamics Pro

3.8.x Updates3.8.5 Updates

App Agent for .NETWeb EUMResolved Issues in 3.8.5


3.8.4 UpdatesControllerApp Agent for .NETApp Agent for PHPResolved Issues in 3.8.4

3.8.3 UpdatesControllerMobile APMAgent for Node.jsResolved Issues in 3.8.3

3.8.2 UpdatesEnd User Monitoring and ControllerWeb EUMApp Agent for PHPApp Agent for JavaResolved Issues in 3.8.2

3.8.1 UpdatesControllerMobile APMWeb EUMApp Agent for JavaApp Agent for .NETResolved Issues in 3.8.1Security Notes for 3.8.1

New and Enhanced Features in 3.8Online Documentation WikiEnd User Monitoring Updates

New Mobile APMWeb EUM

Controller UpdatesUser Interface

BrowsersSnapshot Waterfall ViewCustom DashboardsIntegrations

AppDynamics for DatabasesCompute CloudsREST API

Installation and Platform ChangesApp Agent for Java UpdatesApp Agent for .NET UpdatesApp Agent for PHP UpdatesApp Agent for Node.JS BetaAppDynamics Pro Trial Edition Changes

Agent-Controller Compatibility MatrixSecurity Notes


SSL Certificate Monitoring ExtensionController Notes

Installation Notes for the ControllerUpgrade Notes for the ControllerNon-English Language Setting Workaround

Mobile APM NotesApp Agent for Java NotesApp Agent for .NET NotesResolved Issues in 3.8.0.x

Resolved Issues in 3.8.0Resolved Issues in 3.8.0.1

This topic covers release information for AppDynamics Pro versions 3.8.x.

If you are reading this in PDF format, many links will open in the product documentation wiki. AppDynamics continuously improves its product documentation. The most current release notesare on the wiki at .Release Notes for AppDynamics Pro

3.8.x Updates

3.8.5 Updates

App Agent for .NET

The App Agent for .NET disables correlation of ThreadPoolQueueUserWorkItem for theCLR4 by default. Enable it using the node property. See async-tracking Enable Thread

.Correlation for .NET

Web EUM

Browser usage percentages displayed in browser usage screen previously couldoccasionally be off by up to 5%. The values are now correct.

Resolved Issues in 3.8.5

Component Summary

.NET Agent Disable thread correlation with async fixed.

Agent HIgh CPU by creating custom exit point fixed.

Controller Harden Controller Installer.

Controller Package and Deploy the attributions andlicenses txt file in Controller home.

Controller Event reactor's event queues no longer getstuck under certain error conditions.

Controller Event Reactor fails to properly calculate thelastRsdEvaluatedId fixed.

http://docs.appdynamics.com/display/PRO14S/Enable+Thread+Correlation+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Enable+Thread+Correlation+for+.NET


Controller EUM and Mobile APM HRs no longer fail toadd the respective entities on runtime leads toNPE in controller log.

Node.js Agent Fixed 100% CPU usage.

Node.js Agent Fixed App Crash: Headers already sent.

PHP Agent Fixed PHP BT metrics not reported afterdetecting 100 BT names.

PHP Agent Fixed curl_exec not detected if url does nothave a scheme.

PHP Agent Fixed NuSOAP exit calls detected but notcorrelated with a downstream Java tier.

PHP Agent Fixed excludes don't work when more thanone exclude rule is present.

3.8.4 Updates

Controller

The password you enter during installation for the Controller root user is now used for theGlassfish application server administrator as well. Previously, the password for this user wasa preset value and not configurable at installation. This change does not affect upgrades.For more information, see .Administrative UsersThe transaction detection REST API call for importing or exporting auto detected entrypoints now applies to all auto detected entry point configurations in the Controller,regardless of the app agent they were configured with. Previously, only auto detected entrypoint configurations for the App Agent for Java could be imported and exported using thiscommand; now Java, , PHP, and Node.js auto detected entry point configurations are.NETalso exported or imported. See .Import and Export Transaction Entry Point ConfigurationsThe Linux version of the modifyJvmOptions utility now prevents you from adding a Javaoption that has the same name as an existing option in the domain.xml file. Previously, itpermitted adding an option with the same name as an existing option as long as their valueswere different. In practice, this often resulted in unintended redundant entries indomain.xml. You must now remove the existing option before adding an option with thesame name. Also, a new command for the Linux version of the utility has been added. Itprints the existing options in domain.xml. To use it, enter:

./modifyJvmOptions.sh list

For more information about modifyJvmOptions, see . Modify GlassFish JVM Options

App Agent for .NET

The App Agent for .NET automatically discovers entry points for ASP.NET web forms with

http://docs.appdynamics.com/display/PRO14S/Import+and+Export+Transaction+Detection+Configuration+for+.NET


the Async property set to "true" in the .Page directiveIf you use Areas to organize your MVC application, the agent includes the Area name inbusiness transaction name. See .Identify MVC Transactions by Controller and ActionUse custom expressions enable to name transactions using for getter chain(s) HttpRequestproperties and methods. See .To use a custom expression on the HttpRequestUse the REST API to import and export .NET transaction detection configurations. See Impo

.rt and Export Transaction Detection Configuration for .NET

App Agent for PHP

The App Agent for PHP supports TNSNAMES.ora for discovery of Oracle backends. Previous versions of the agent did not fully support TNSNAMES.ora.


Component Summary

.NET Agent 404 calls no longer register a new businesstransaction when MVC Controller cannot befound

.NET Agent Improved support for applications usingWeakReference

.NET Agent Resolved a memory leak related toAzureBlobExitInterceptor

.NET Agent Improved business transaction support forASP.NET 4.0 pages that use the Pageproperty of Async="true"

.NET Agent, Controller Resolved an issue with ADO.NET DB exit callsauto-resolving to the tier

Agent Resolved an issue with EOFException on SunRMI JRMP result stream

Agent Now delay AMX booting for GlassFish

Agent Fixed naming of business transactions forcustom match rules of type Servlet that useURI segment naming such that resulting nameis patterned after ./.../

Agent, Controller No longer correlate when cross-Controllerrequests are detected

Controller Resolved a minor issue that caused anIllegalArgumentException: inconsistent range

http://msdn.microsoft.com/en-us/library/vstudio/ydy4x04a(v=vs.100).aspxhttp://docs.appdynamics.com/display/PRO14S/Identify+MVC+Transactions+by+Controller+and+Action#IdentifyMVCTransactionsbyControllerandAction-BusinessTransactionNamingConventionhttp://docs.appdynamics.com/display/PRO14S/Getter+Chains+in+.NET+Configurationshttp://msdn.microsoft.com/en-us/library/system.web.httprequest.aspxhttp://docs.appdynamics.com/display/PRO14S/ASP.NET+Entry+Points#ASP.NETEntryPoints-TouseacustomexpressionontheHttpRequesthttp://docs.appdynamics.com/display/PRO14S/Import+and+Export+Transaction+Detection+Configuration+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Import+and+Export+Transaction+Detection+Configuration+for+.NET


Controller Information point method names are no longertruncated at 100 characters; now support up to500

Controller For new installations, the app serveradministration account password is now thesame as the Controller root user password

PHP Agent The agent now supports OCI8 and aconnection method which uses the file"tnsnames.ora"

PHP Agent The RPM installer no longer sets the PHPagent log to /agent.log

PHP Agent Resolved a NullPointerException in proxy logsduring agent startup

Android Agent, iOS Agent, UI Resolved a UI problem displaying data for iOSand Android

Web EUM Fetching all Browser Snapshots for extendedperiods, like a month, could take a very longtime, particularly when the underlying data issparse. The requests for this functionalityhave been optimized and response time ismuch improved.

3.8.3 Updates

Controller

The installation and upgrade procedures have changed as follows: During upgrade, the installer attempts to restart the Controller and database. If itcannot complete the restart within the timeout period, it exits and rolls back thechanges. By default, the installer now waits 30 minutes for the startup to complete(previously the timeout was 10 minutes). If the Controller or database take longer tostart up (most likely due to a large amount of data in the database), you can increasethe timeout before running the upgrade. To increase the timeout, edit the/.install4j/response.varfile by adding the ad-timeout-in-minproperty (for example, ad-timeout-in-min=50, to increase the timeout to 50 minutes). Instead of rolling back changes, if the timeout expires, the installer exits without rollingback changes. This gives you an opportunity to troubleshoot the issue and remediatebefore retrying the install or upgrade. You will need to revert the disk changesmanually by restoring from the backed up copy of the installation and data directoriesbefore retrying the upgrade. See Upgrade the Controller for more information.

Red Hat Enterprise Linux (RHEL) and CentOS operating systems versions 6.3, 6.4, and 6.5have been certified as supported platforms for the Controller. For the complete list ofsupported environments, see . Supported Environments and Versions


In the Controller UI, custom match rules for entry points now show a priority field with defaultset to 0.

Mobile APM

A new version of the AppDynamics plugin for Gradle-based builds of the Android agent(supporting Gradle 1.10 and Android Tools versions 0.7.3,0.8.3, and 0.9.2) is now available.See .Instrument an Android Application

Agent for Node.js

Distributed transaction correlation for the Agent of Node.js is supported. See Distributed.Transactions for Node.js


Component Summary

App Agent for .NET Uninstalling the agent no longer results in acmd prompt on Windows

App Agent for .NET Resolved issue that could cause the .NETagent to not report properly

App Agent for Java Improved correlation support using RemoteActors on Akka version 2.3.1

App Agent for Java Resolved issue with monitoring a Sybasestored procedure

App Agent for Java Resolved issue with extraneous error messagewhen an already registered rule exceptionfrom JDBCRuleApplier is applied

App Agent for Java Resolved a potential issue that could result inlonger startup times for a server

App Agent for Java Resolved a potential NPE in Agent Proxy

App Agent for Java Resolved a issue that could result in a customrule to stop working after upgrading to 3.8

App Agent for Node.js Added distributed transaction correlation

Controller Resolved issue with showing most expensivecalls for stalled business transactions

Controller Resolved a problem with health rule messagesshowing an incorrect JMX metric name

Controller Resolved an issue with missing tier flow mapdata for current time range

Controller Resolved a caching error that could causemetric gaps

http://docs.appdynamics.com/display/PRO14S/Instrument+an+Android+Applicationhttp://docs.appdynamics.com/display/PRO14S/Distributed+Transactions+for+Node.jshttp://docs.appdynamics.com/display/PRO14S/Distributed+Transactions+for+Node.js


Controller Linux controller installer no longer fails if /tmpis mounted with the 'noexec' option

Controller Resolved a potential issue that could result ina user's inability to login to AppDynamicsthrough SAML Authentication

Controller Resolved inconsistency with GC time spentand counts

Controller Resolved upgrade timeout/rollback issue

UI Reduced load time for Flash UI components

UI Widget series now use different colors whenadding new series

UI Updated a confusing error message whenexporting an application

UI Resolved issue with page dashboard graphsnot showing up when there is no data in thetime range

UI Improved the formatting of numeric metrics inPage Dashboards

UI Browser snapshot grid and mobile networkrequest snapshot grids now format datesconsistently

3.8.2 Updates

End User Monitoring and Controller

An on-premise Controller with End User Monitoring (EUM) enabled needs to be able to connect tothe EUM Cloud aggregator. If the Controller needs to make external connections through anauthenticating proxy, you can now specify credentials for the Controller to pass to the proxy.

You configure the credentials using two new Controller Java options:

appdynamics.controller.http.proxyUserappdynamics.controller.http.proxyPasswordFile

The value of proxyPasswordFile should be the location and name of the file that contains the plaintext password associated with the user identified by proxyUser. For more information, see Set Up

. and Configure Web EUM

Web EUM

End User Response time is displayed in the Metric Browser in terms of percentiles (for thisrelease, P90), regardless of the Controller used.

App Agent for PHP

http://docs.appdynamics.com/display/PRO14S/Set+Up+and+Configure+Web+EUMhttp://docs.appdynamics.com/display/PRO14S/Set+Up+and+Configure+Web+EUM


The App Agent for PHP now supports:

PHP Web Service as a entry point.This entry point requires a 3.8.2 Controller.If you have distributed business transactions that call Java, .NET, or Node.js tiers froma PHP Web Service entry point, you must upgrade the app agents for those tiers to3.8.2 to get full stack traces in the distributed call graphs.

NuSOAP as a PHP Web Service framework.OCI8 as a database exit point.NuSOAP as a Web Service exit point.

App Agent for Java

Sun JRMP support is disabled by default. You should test Sun JRMP support in stagingbefore using it on production systems. Enable Sum JRMP support by setting the app agent

. This property defaults to false.node property, jrmp-enabled=true


Component Summary

.NET Agent Installer Error using MsiExec fixed

Agent Disable Sun JRMP by default

Agent Automatic BT identification with parametersshould be deferred in certain cases

Agent JAX-WS BT not detected as WS BT fixed

Agent Java Agent failure to connect to controller overSSL fixed

Controller Don't enforce a 6 minute window on eventhistory

Controller HR evaluations/Alerts stuck at the same stage fixed

PHP Agent Implemented support for Oracle's OCI8

PHP Agent Implemented NuSOAP entry point detection

PHP Agent Implemented NuSOAP exit point detection

PHP Agent PHP agent causes file_get_contents withcustom context to fail fixed

3.8.1 Updates


Controller

SAML group-to-role mapping The Controller now automatically maps groups for a user as identified in SAML responses toroles in the UI. See . Configure Authentication Using SAMLMySQL version updateThe version of MySQL included with the Controller has been updated from version 5.5.16 to5.5.37. For Controller upgrades, the installer applies the new MySQL version to yourupgraded instance.

Mobile APM

The following mobile metric names have changed:Network Request Error is re-named HTTP Error.Network Connection Error is re-named Network Error.

The crashed file and crashed line items in the crash snapshot lists have been combined intoa single item.

Web EUM

If a Web EUM instrumented page is associated with a server-side app agent, the cookie that theserver-side app agent sets is now named ADRUM_BT instead of ADRUM_X_Y_Z as in previousversions.

App Agent for Java

HTTP Proxy authentication support The App Agent for Java now supports user name and password authentication to an HTTPproxy server. New app agent node property can be used when a class iscapture-spring-bean-namesmapped to multiple spring bean names to display the class name instead of the spring beanname. See .App Agent Node Properties Reference

App Agent for .NET

The App Agent for .NET has updated support and configuration for correlation of .NETremoting. See .Enable Correlation for .NET Remoting


Component Summary

App Agent for .NET Fixed a problem with the agent parsing IIS6hierarchies

App Agent for .NET Fixed a problem detecting IBM WebSpheremessage queue exit points

App Agent for .NET Fixed a problem with automatic injection of theEUM Footer

App Agent for .NET Create a white list based agent

http://docs.appdynamics.com/display/PRO14S/Enable+Correlation+for+.NET+Remoting


App Agent for Java Added support for HTTP proxy authentication

App Agent for Java Improved Akka support for Scala with closuremethods

App Agent for Java Fixed a problem with service endpoints on aJAX-RS based web service

App Agent for Java Fixed a problem with some node propertiesnot being set

App Agent for PHP Fixed a problem with a segmentation fault inApache 2

App Agent for PHP Improved cookie handling

Controller Fixed a problem with a repeating snapshotaffecting metric registration

Controller Added support for SAML group assertions

Controller Fixed a problem where the upgrade processcreated a domain.xml with disabled httplisteners

Controller Fixed a database connection problem duringupgrade

Controller Improved top-level End User Experiencedashboard load time

Controller Fixed a problem with exporting applications

Controller Improved URL information for SaaS alerts

Controller, UI, Mobile Fixed a checkbox for enabling mobile APM

Controller Improved TLS-1.2 Only (HTTPS) support

Controller Fixed an installation problem on Win32 relatedto database shutdown

Controller Fixed a problem affecting the MySQL DataDictionary

UI Fixed a problem with importing dashboards

UI Renamed the "Network Connection Error"metric to "Network Error"

UI, Web EUM Retained filter when navigating from pagedashboard to browser snapshot

UI Updated terminology for HTTP errors andnetwork errors


UI, Web EUM Page Dashboards no longer show negativenumbers for related normal businesstransaction calls

Web EUM Improved cookie handling

Security Notes for 3.8.1

The default security protocol used by the on-premise Controller has changed. For enhancedsecurity, the Controller's secure listener now uses TLS 1.1 and TLS 1.2 instead of TLS v1.0and SSLv3.

If using the Controller with an older version of the App Agent for Java or .NET framework,you need to be aware of security compatibility implications of the change.

This issue affects you if you have upgraded the Controller to 3.8.1 or later and still have anyof the following deployed in your environment:

App Agents for Java version 3.8.0 or earlier (see Agent - Controller Compatibility for details on SSL compatibility by version)Matrix

App Agents running on .NET Framework versions earlier than 4.5

If you are affected by this issue, AppDynamics recommends that you upgrade theenvironment, as follows:

For App Agent for Java, upgrade to the latest version of the App Agent for JavaFor .NET, recompile the application to use the .NET Framework 4.5 and enableTLSv1.2 on the host machine.

If upgrading agents or framework is not possible, you can re-enable TLS v1.0 and SSLv3 onthe Controller. For instructions on reenabling the security protocols, see Configure the

. Security ProtocolThis release includes an updated version of MySQL. The update to MySQL 5.5.37 fixesseveral security issues in MySQL.

New and Enhanced Features in 3.8

The following components have new and enhanced features in release 3.8:

Online Documentation Wiki

The online documentation for 3.8 is now publicly available and does not require a login. It can nowbe indexed by the major search engines. To make comments on the topics, please login with yourstandard AppDynamics account.

End User Monitoring Updates

New Mobile APM

AppDynamics introduces the new Mobile APM Agent so you can monitor mobile applicationson the iOS and Android platforms.


See .Mobile APM

Web EUM

New waterfall page dashboards. See .Page, Ajax, and Iframe DashboardsNew waterfall browser snapshots. See .Browser SnapshotsMore network timing information. See .Web EUM MetricsHealth rules for Pages, Ajax requests, iframes are now easier to create. See . Health RulesThe main JavaScript agent file, adrum.js, now available in a hosted option via Amazon CDN. See .Using a Hosted Version of the JavaScript Agent

Controller Updates

User Interface

The fonts, colors, and many icons have changed.There is a new Home Page. See .AppDynamics Home Page The following top-level icons and menu options are now:

Settings: The Settings menu is represented by this icon.

User: User menu is represented by this icon , . The Logout User option islocated in this menu.The My Preferences option has moved from the Settings menu to the User menu.See .Dashboards

: Not all UI changes are currently reflected in the documentation.Note

Browsers

Support for IE 8.x is deprecated.

Snapshot Waterfall View

New user interface for viewing business transaction snapshots. See .Transaction Snapshots

Custom Dashboards

Export and Import: You can now export a Custom Dashboard to a file and import it into

another Controller environment. See .Use a Custom Dashboard

HTML5-based UI for the Dashboard Editor.The icons used on the dashboards are refreshed.

Policies and Alerts

New Health Rule templates for creating health rules, covering more entities. See Health.Rules

Ability to create health rules based on custom metrics over multiple entities. See Configure.Health Rules

http://docs.appdynamics.com/display/PRO14S/Mobile+APMhttp://docs.appdynamics.com/display/PRO14S/Page%2C+Ajax%2C+and+Iframe+Dashboardshttp://docs.appdynamics.com/display/PRO14S/Browser+Snapshotshttp://docs.appdynamics.com/display/PRO14S/Web+EUM+Metricshttp://docs.appdynamics.com/display/PRO14S/Health+Ruleshttp://docs.appdynamics.com/display/PRO14S/Options+in+Using+Manual+Injection+for+the+EUM+JavaScript+Agenthttp://docs.appdynamics.com/display/PRO14S/AppDynamics+Home+Pagehttp://docs.appdynamics.com/display/PRO14S/Dashboardshttp://docs.appdynamics.com/display/PRO14S/Transaction+Snapshotshttp://docs.appdynamics.com/display/PRO14S/Use+a+Custom+Dashboardhttp://docs.appdynamics.com/display/PRO14S/Health+Ruleshttp://docs.appdynamics.com/display/PRO14S/Health+Ruleshttp://docs.appdynamics.com/display/PRO14S/Configure+Health+Ruleshttp://docs.appdynamics.com/display/PRO14S/Configure+Health+Rules


New JVM crash event. See .Configure Policies

Integrations

AppDynamics for Databases

Improved JDBC Correlation with Oracle Databases for the App Agent for Java withAppDynamics For Databases 2.8. From a business transaction snapshot flow map, you canlink to AppDynamics for Databases to the exact SQL that was running during the originatingsnapshot.

Compute Clouds

Compute cloud extensions are no longer packaged with AppDynamics. Download cloudconnector extensions from the .AppDynamics Exchange

REST API

Usernames that contain certain characters are not authenticated for REST API calls. See In.valid Characters for Usernames

Installation and Platform Changes

The bundled JDK is updated to version 1.7.Database user password changes:

Previously the installer generated the password that the Controller uses to log in to theMySQL database automatically. The Controller installer now presents a prompt for theController's database user password. The default storage location of the database password has changed to/db/.rootpw. The Controller can retrieve the database user password using other mechanism aswell, including from an environment variable or from a command line prompt.

See for more information. See forController Data and Backups Upgrade the Controllerupgrade information relating to the database user password.

App Agent for Java Updates

Developer Monitoring LevelDevelopers can choose to relax monitoring constraints to capture more informationabout their applications while in development. Safeguards are in place to ensure anautomation switch back to Production monitoring when the number of transactionstracked exceeds specified limits. See .Monitoring in a Development Environment

MBean Browser EnhancementsMBean Browser now allows invocation of mBean operations, supports the viewing andediting of complex attributes, and a new JMX entry in the left navigation menu allowsanother point of entry to JMX Metrics and the MBean Browser. See Monitor JMX

.MBeansJVM Guard

Automated detection of JVM Crashes. Create an event that detects and reports on theJVM crashes, then for example, initiate an action, such as JVM restart. See JVM

http://docs.appdynamics.com/display/PRO14S/Configure+Policieshttp://community.appdynamics.com/t5/AppDynamics-eXchange/idb-p/extensionshttp://docs.appdynamics.com/display/PRO14S/Use+the+AppDynamics+REST+APIhttp://docs.appdynamics.com/display/PRO14S/Use+the+AppDynamics+REST+APIhttp://docs.appdynamics.com/display/PRO14S/Monitoring+in+a+Development+Environmenthttp://docs.appdynamics.com/display/PRO14S/Monitor+JMX+MBeanshttp://docs.appdynamics.com/display/PRO14S/Monitor+JMX+MBeanshttp://docs.appdynamics.com/display/PRO14S/JVM+Crash+Guard


.Crash GuardService Endpoints

Create tier-level entry points for capturing service KPIs. See Service Endpoint.Monitoring

SSL chain validation through controller-info.xml property. For more information, see Enable SSL and for Java App Agent For Java.

New Frameworks support. For more information, see Supported Environments and Versionsfor Java.

Akka

Apache Synapse. To enable correlation, set node property,"enable-soap-header-correlation=true". For more information about this new nodeproperty, see Enable Soap Header Correlation.

Apple WebObjects

Coherence JMX metrics preconfigured. For more information, see Configure JMX Metricsfrom MBeans and Monitor JMX MBeans.

Google Web Toolkit (GWT)

Infinispan

Mule ESB support improvements

Play for Scala

Java RMI over JRMP

Tighter Integration with AppDynamics for Databases Oracle CollectorsFrom a Transaction Snapshot Flow Map, where the exit call is to an Oracle database,you can link to AppDynamics for Databases 2.8 to see and analyze the exact SQLthat was running at the time of the transaction snapshot. To enable this functionality,for the node containing the Oracle database, you must set the App Agent for Javanode property jdbc-dbcam-integration-enabled=true. For more information, see Integrate and Use AppD4DB with AppDynamics Pro.

See .Supported Environments and Versions

App Agent for .NET Updates

The App Agent for .NET automatically detects MVC 5 business transactions withoutadditional configuration.The App Agent for .NET automatically discovers RabbitMQ remote services. Monitor

.RabbitMQ Backends for .NETYou can configure the App Agent for .NET to discover HTTP, Web Services, and WCFasync remote services. .Monitor Async Transactions for .NETOracle ODP.NET database backends integrate with AppDynamics for Databases. See Monit

.or Oracle Backends for .NET with AppDynamics for DatabasesAn updated installer package removes the requirement to uninstall for future upgrades andincludes integrated user access control. .Install the App Agent for .NET

See .Supported Environments and Versions

http://docs.appdynamics.com/display/PRO14S/JVM+Crash+Guardhttp://docs.appdynamics.com/display/PRO14S/Service+Endpoint+Monitoringhttp://docs.appdynamics.com/display/PRO14S/Service+Endpoint+Monitoringhttp://docs.appdynamics.com/display/PRO14S/Enable+SSL+for+Javahttp://docs.appdynamics.com/display/PRO14S/Enable+SSL+for+Javahttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Supported+Environments+and+Versions+for+Javahttp://docs.appdynamics.com/display/PRO14S/Supported+Environments+and+Versions+for+Javahttp://docs.appdynamics.com/display/PRO14S/App+Agent+Node+Properties+Reference#AppAgentNodePropertiesReference-EnableSoapHeaderCorrelationhttp://docs.appdynamics.com/display/PRO14S/Configure+JMX+Metrics+from+MBeanshttp://docs.appdynamics.com/display/PRO14S/Configure+JMX+Metrics+from+MBeanshttp://docs.appdynamics.com/display/PRO14S/Monitor+JMX+MBeanshttp://docs.appdynamics.com/display/PRO14S/App+Agent+Node+Properties+Reference#AppAgentNodePropertiesReference#jdbc-dbcam-integration-enabledhttp://docs.appdynamics.com/display/PRO14S/Integrate+with+AppDynamics+for+Databaseshttp://docs.appdynamics.com/display/PRO14S/Integrate+with+AppDynamics+for+Databaseshttp://docs.appdynamics.com/display/ADDB/Integrate+and+Use+AppD4DB+with+AppDynamics+Prohttp://docs.appdynamics.com/display/PRO14S/Monitor+RabbitMQ+Backends+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Monitor+RabbitMQ+Backends+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Monitor+Async+Transactions+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Monitor+Oracle+Backends+for+.NET+with+AppDynamics+for+Databaseshttp://docs.appdynamics.com/display/PRO14S/Monitor+Oracle+Backends+for+.NET+with+AppDynamics+for+Databaseshttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+.NET


App Agent for PHP Updates

The App Agent for PHP supports the PHP Command Line Interface (CLI) as an entry point.See .Configure PHP Command Line Interface (CLI) Entry PointsThe App Agent for PHP supports PHP tiers in distributed business transactions both asoriginating tiers and as downstream tiers. See .Distributed Transactions for PHPThe App Agent for PHP supports RabbitMQ as an exit point. See Monitor RabbitMQ

.Backends for PHP

App Agent for Node.JS Beta

AppDynamics introduces the beta version of the new App Agent for Node.JS. See AppDyna.mics for Node.js Beta

AppDynamics Pro Trial Edition Changes

Previously, when the trial license expired for the AppDynamics Pro trial, it meant that you could nolonger use the AppDynamics Pro instance. Now when the trial license expires, the AppDynamicsPro trial transitions to the free edition of the product, AppDynamics Lite.

For more information about the free edition of the product, see AppDynamics Lite.

Agent-Controller Compatibility Matrix

The Controller supports older Agents. Newer Agents will not work with an older Controllerversion. See the .Agent - Controller Compatibility Matrix

Security Notes

The following section lists general security information for AppDynamics. For release-specificsecurity information, see the update notes for that release.

SSL Certificate Monitoring Extension

The SSL Certificate Monitoring Extension is a new extension on the that rAppDynamics eXchangeeports the expiration date of SSL certificates on the machine as a metric to the Controller. Theextension reports the certificate expiration date metric for the domains and at the interval youconfigure.

For more information, see the listing.SSL Certificate - Monitoring Extension

Controller Notes

Install the Controller if you are not using the AppDynamics SaaS Controller Service. If youare using the SaaS Controller, skip the Controller installation.

http://docs.appdynamics.com/display/PRO14S/Configure+PHP+Command+Line+Interface+%28CLI%29+Entry+Pointshttp://docs.appdynamics.com/display/PRO14S/Distributed+Transactions+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Monitor+RabbitMQ+Backends+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Monitor+RabbitMQ+Backends+for+PHPhttp://docs.appdynamics.com/display/PRO14S/AppDynamics+for+Node.js+Betahttp://docs.appdynamics.com/display/PRO14S/AppDynamics+for+Node.js+Betahttp://docs.appdynamics.com/display/PRO14S/AppDynamics+Litehttp://community.appdynamics.com/t5/AppDynamics-eXchange/idb-p/extensionshttp://community.appdynamics.com/t5/AppDynamics-eXchange/SSL-Certificate-Monitoring-Extension/idi-p/8628


Obtain the Controller for your operating system from the .AppDynamics Download CenterKnown Issue: you may see an exception about a missing apache .jar file in the logs onstartup. It is harmless. Known Issue: in some instances an exception may occur when exporting an applicationconfiguration.Known Issue: installing or upgrading the Controller on any Windows system that does notuse English as its system language will fail. For the workaround, see Non-English Language

.Setting WorkaroundKnown Issue: After an upgrade of an on-premise Controller to version 3.8.1 or later, AppAgents that use SSL may not be able to connect to the Controller. See Security Notes for

for more information. 3.8.1

Installation Notes for the Controller

Before you install or upgrade the Controller, validate the hardware requirements as listed at . The sizing requirements have been updated and nowController System Requirements

include recommendations based on metrics per minute in addition to the number of nodes inthe installation. Features such as monitoring asynchronous threads and End UserMonitoring increase the number of metrics per minute flowing to the Controller.AppDynamics strongly recommends that you install the Controller on a dedicated machinefor adequate stability and performance.The disk space requirements differ for each of the Controller performance profiles. Verify thedisk space requirements for your performance profile at .Controller System RequirementsIf installing on Windows, note the operational and configuration guidelines listed in Install the

for preventing the possibility of Controller data corruption due toController on Windowsconflicts with existing Windows processes. Also note the workaround if installing orupgrading a Windows machine that does not use English for its regional settings, see Non-E

.nglish Language Setting Workaround

Upgrade Notes for the Controller

For all major upgrades, AppDynamics recommends that you upgrade both the Controllerand Agents. This ensures that you get all the latest Agent features and fixes. If you are upgrading both the Controller and the Agents, first upgrade the Controller thenupgrade the Agents. Make sure that you have saved a backup of the following files before starting the upgradeprocedure:

/db/db.cnf

/appserver/glassfish/domains/domain1/config/domain.xml

/conf/controller-info.xml

If you are applying the upgrade by passing a response file to the installer, you must pass theresponse file generated by the installer at first installation. This response file is at.install4j/response.varfile under the Controller home directory. Make sure that the settings inthe file reflect any configuration changes you have made since installation. A known issue prevents you from changing the database port number at upgrade time if

http://download.appdynamics.com/


1. 2. 3.

4. 5.

using a response file. If you set a different database port in the response file,response.varfile, from the one used by the Controller, the installation times out whileattempting to start the database.

For more information, see .Upgrade the Controller

Non-English Language Setting Workaround

When installing or upgrading the Controller on Windows systems that use a regional and languagesetting other than English (United States), the Controller installation or upgrade fails. The errormessage may indicate that the Controller database failed to start or that the setup processes failedto reach the Controller. The error occurs when the installer is attempting to start the Controller, andcauses the installer to abort the installation or upgrade.

To work around this issue:

Change the regional and language setting on the system to English (United States).Perform the upgrade or installation. When the upgrade or installation is finished, edit the\bin\controller.bat and replace the following line:

IF %TIME% == %START_TIMEOUT% (

With:

IF "%TIME%" == "%START_TIMEOUT%" (

This line appears in the :startControllerDB section of the file. Notice the addition of quotesaround both values used in the value comparison. Save your changes. Change the regional and language settings back to its original value.

Mobile APM Notes

Known Issue: the Mobile Geo Dashboard may time out if there are a large number of appsand large amounts of data.The Mobile APM Agent increases the number of metrics reported, which may affect thehardware requirements for an on-premise controller. See .Additional Sizing Requirements

App Agent for Java Notes

Obtain the AppDynamics App Agent for Java download for your system from the AppDynamics:Download Center

For Sun and JRockit JVMs, download AppServerAgent-x.x.x.zip

http://docs.appdynamics.com/display/PRO14S/Controller+System+Requirements#ControllerSystemRequirements-AdditionalSizingRequirementshttp://download.appdynamics.comhttp://download.appdynamics.com


For IBM JVMs, download AppServerAgent-ibm-x.x.x.zip

For more information see:

Install the App Agent for JavaJava Server-Specific Installation SettingsApp Agent for Java Configuration Properties

Known Issues:

The new JVM Guard feature may not consistently report JVM crashes. As of 3.8.3, support for correlation over Sun RMI over JRMP has been temporarilysuspended.

App Agent for .NET Notes

Obtain the AppDynamics App Agent for .NET download for your system from the AppDynamics:Download Center

For Windows 32-bit, download dotNetAgentSetup.msiFor Windows 64-bit, download dotNetAgentSetup64.msi

For more information see:

Install the App Agent for .NETApp Agent for .NET Configuration PropertiesResolve App Agent for .NET Installation and Configuration IssuesConfigure the .NET Machine Agent

Resolved Issues in 3.8.0.x


Controller Fixed a problem with delays in backenddiscover configuration

Controller Fixed a problem with node based health rulesbeing evaluated for a node not in the list

UI, App Agent for PHP Fixed a problem with the RabbitMQ icon notdisplaying

EUMCloud, UI Fixed a problem with alerts when page viewlimit was reached

Resolved Issues in 3.8.0.1

Components Summary

http://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Java+Server-Specific+Installation+Settingshttp://docs.appdynamics.com/display/PRO14S/App+Agent+for+Java+Configuration+Propertieshttp://download.appdynamics.com/http://download.appdynamics.com/http://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/App+Agent+for+.NET+Configuration+Propertieshttp://docs.appdynamics.com/display/PRO14S/Resolve+App+Agent+for+.NET+Installation+and+Configuration+Issueshttp://docs.appdynamics.com/display/PRO14S/Configure+the+.NET+Machine+Agent


App Agent for Java Fixed a problem with some node propertiesnot being set

Controller Improved performance of the EUM dashboard

Controller UI, Fixed a potential issue that preventeddashboards created with 3.7 from beingimport/exported

Agent - Controller Compatibility Matrix

App Agent for Java - Controller CompatibilityApp Agent for .NET - Controller Compatibility App Agent for PHP - Controller CompatibilityApp Agent for Node.js - Controller CompatibilityAppDynamics for Databases - Controller CompatibilitySSL Compatibility Notes for App Agent for Java - ControllerLearn More

App Agent for Java - Controller Compatibility

The Controller supports older Agents. Prior to 3.6.2, newer agents will not work with an olderController. 3.6.2 and newer agents will work with the Controller that has the same major and minorversion (X.x).

The 3.8.x Controller supports the following versions of the App Agent for Java:

3.5.2 - 3.5.73.6.0 - 3.6.73.7.x3.8.x

For the notes on SSL protocol compatibility between versions of the agent and Controller, see SSL. Compatibility Matrix for App Agent for Java - Controller

App Agent for .NET - Controller Compatibility

The Controller supports older Agents. Prior to 3.6.2, newer agents will not work with an olderController. 3.6.2 and newer agents will work with the Controller that has the same major and minorversion (X.x).

The 3.8.x Controller supports the following versions of the App Agent for .NET:

3.5.3 - 3.5.73.6.0 - 3.6.73.7.x3.8.x

https://singularity.jira.com/browse/CORE-27286


App Agent for PHP - Controller Compatibility

The 3.8.x Controller supports the following versions of the App Agent for PHP:

3.7.7 and newer 3.7.x3.8.x

App Agent for Node.js - Controller Compatibility

The 3.8.x Controller supports the following versions of the App Agent for Node.js:

3.8.x

AppDynamics for Databases - Controller Compatibility

The 3.8.x Controller supports the following versions of AppDynamics for Databases:

3.6.0 - 3.6.73.7.x3.8.x

Note: AppDynamics for Databases version 2.7.4 is required for AppDynamics for Databases tocorrelate with the App Agent for PHP.

SSL Compatibility Notes for App Agent for Java - Controller

The following table lists the default security protocol that each version of the Controller and AppAgent for Java use to negotiate secure connections. It also describes when you need to modify thedefault configuration to address any incompatibilities between the default security protocol.

App Agent for Java Controller Security Protocol Mappingand Notes

3.7.x 3.7.x Controller: SSLv3 is default

App Agent: SSLv3 is defaultand not changeable

3.8.0 3.8.0 Controller: SSLv3 is default



3.8.0 3.8.1+ Controller: TLSv1.2 is default


To work with the agent, theController must be changedfrom TLSv1.2 to SSLv3 withthe asadmin command (seefollowing section).

3.8.1 3.8.0 Controller: SSLv3 is default


3.8.1 3.8.1+ Controller: TLSv1.2 is default


To work with the agent, theController must be changedfrom TLSv1.2 to SSLv3 withthe asadmin command (seefollowing section).

3.8.2+ 3.8.0 Controller: SSLv3 is default

App Agent:

For Java 7+ applications,TLSv1.2 is default. Youcan change the agent touse SSLv3. For Java 5/6 applications,SSLv3 is default.

3.8.2+ 3.8.1+ Controller: TLSv1.2 is default

App Agent:

For Java 7+ applications,TLSv1.2 is default. Youcan change the agent toSSLv3. For Java 5/6 applications,SSLv3 is default. You mustenable SSLv3 connectionon the Controller.

For information on changing the default security protocol used by the Controller or agent, see Impl.ement Security


Learn More

Supported Environments and Versions

Install and Upgrade AppDynamics

This section shows you where to go to download and install the AppDynamics Pro software.

Quick InstallationStandard InstallationMore Topics

Quick Installation

For instructions on how to perform a quick, basic installation suitable for small-scale evaluationenvironments, see the instructions. Quick Install

Standard Installation

Before you install see:

ArchitectureLogical ModelDownload AppDynamics Software

On-Premise Controller

Install the ControllerUpgrade the ControllerVerify AppAgent-ControllerCommunication

App Agent for Java

Install the App Agentfor JavaUpgrade the AppAgent for JavaUninstall the AppAgent for Java

App Agent for .NET

Install the App Agentfor .NETUpgrade the AppAgent for .NET

http://docs.appdynamics.com/display/PRO14S/Architecturehttp://docs.appdynamics.com/display/PRO14S/Logical+Modelhttp://docs.appdynamics.com/display/PRO14S/Download+AppDynamics+Softwarehttp://docs.appdynamics.com/display/PRO14S/Verify+App+Agent-Controller+Communicationhttp://docs.appdynamics.com/display/PRO14S/Verify+App+Agent-Controller+Communicationhttp://docs.appdynamics.com/display/PRO14S/Verify+App+Agent-Controller+Communicationhttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Upgrade+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Upgrade+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Uninstall+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Uninstall+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Upgrade+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Upgrade+the+App+Agent+for+.NET


Uninstall the AppAgent for .NET

App Agent for PHP

Install the App Agentfor PHPUninstall the AppAgent for PHPUpgrade the AppAgent for PHP

Machine Agent

Install the StandaloneMachine Agent

More Topics

This section includes the following topics:

Quick InstallSupported Environments and VersionsInstall the ControllerInstall AgentsController LicensesConnect the Controller and AgentsUpgrade the ControllerUninstall the ControllerMigrate the Controller between Machines

Quick Install

On-Premise Only: Install The ControllerInstall Agents for JVMsInstall Agents for .NET CLRsInstall Agents for PHP AppsInstall the Standalone Machine Agent

The following topics describe how to get an instance of AppDynamics up and running quickly. Theagent installs are for app agents from the Agent Download Wizard in the Controller.

If you downloaded the agent from the , see AppDynamics download zone Install App Agents.from the AppDynamics Download Zone

If you are using the Controller on-premise, you must install the latest Controller beforeproceeding with agent installs. For more information contact .AppDynamics Support

http://docs.appdynamics.com/display/PRO14S/Uninstall+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Uninstall+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Uninstall+the+App+Agent+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Uninstall+the+App+Agent+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Upgrade+the+App+Agent+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Upgrade+the+App+Agent+for+PHPhttp://download.appdynamics.com/https://www.appdynamics.com/support/


On-Premise Only: Install The Controller

These steps assume that you want to perform a relatively straightforward installation suitable for asmall-scale evaluation environment, and that you do not require high availability, multi-tenancy, orother features intended for production deployments.

Install the Pro Trial Controller on LinuxInstall the Pro Trial Controller on Windows

Install Agents for JVMs

Quick Install for the App Agent for Java

Install Agents for .NET CLRs

Quick Install for the App Agent for .NET

Install Agents for PHP Apps

Quick Install for the App Agent for PHP

Install the Standalone Machine Agent

Quick Install for the Standalone Machine Agent

To see full installation documentation instead, see and .Install the Controller Install Agents

Install the Pro Trial Controller on Linux

Pre-installation Checklist for LinuxRun the Linux InstallerPost-Installation Checklist for LinuxNext StepsLearn More

This topic describes how to install a trial instance of the AppDynamics Controller on Linux. Thetrial Controller is identical to the full-service Controller, with all the same features, but subject to a15-day trial license. If you are installing a standard Controller see .Install the Controller on Linux

Pre-installation Checklist for Linux

Confirm the operating system requirements at :Controller System RequirementsRedhat Enterprise Linux (RHEL) 6.1, 6.2CentOS 6.1, 6.2Fedora 14


1.

2. 3. 4.

5. 6.

7.

Ubuntu 8, 12Open SUSE 11.xSUSE Linux Enterprise ServerCloud: Amazon EC2, Rackspace, Azure

Confirm browser and Flash support:Mozilla FireFox 6+Internet Explorer 9+Safari 6+Google Chrome 16+The Controller UI requires Flash Player 10 or greater; AppDynamics recommendsversion 11.

Confirm disk space requirements:50 GB

Confirm CPU, RAM and Disk I/O capacity:2 GB RAM2 CPU Cores1.5 GHz minimumDisk I/O: 50 MB/sec write, 50 MB/sec read, 1.5 MB/sec random

The Controller requires that libaio be installed on the machine prior to installation. For moreinformation see .Install libaio on Linux

Make sure the file descriptor limit is set to at least 65535. For more information see Configur.e File Descriptor Limits on Linux

Download the 32-bit or 64-bit Linux installer file from the Downloads tab on the Support. You'll need to register on the web site to get access to the installer download.page

Change the access permissions for the installer file to permit execution.

Make sure that the Controller will be accessible to the application agents and browserclients. If needed, open the firewall to the HTTP port that the Controller will use for HTTP orHTTPS communication, 8090 or 8181, by default.

Run the Linux Installer

At the command line, execute the Controller installer .sh file.By default the installer tries to start in GUI mode. If the system does not have a GUIdesktop, the installer starts in console mode. You can force the installer to start in consolemode by passing the option to the installer. The following steps assume the installer is in-cGUI mode.In the Welcome screen click Next.Scroll to the bottom of the license agreement, click accept and then Next.Click Yes to grant AppDynamics permission to collect usage data statistics from your controller.AppDynamics uses the data to improve the quality of its products and services.

Accept the default installation directory by clicking Next.Enter the password for the database user that the Controller uses to access the bundledMySQL database.

https://www.appdynamics.com/support/https://www.appdynamics.com/support/


7.

8.

9. 10.

11.

12.

Verify the default host name and Application Server Primary Port. Note the primary port number, 8090 by default. You will need this later to log in to theController UI from the browser. Verify the other required ports suggested by the installer and click . The installer checksNextthe availability of the ports before presenting them on the screen. If necessary, click Edit

, modify the defaults, and save your changes to use different ports.Ports

Choose single-tenancy mode for the Controller, then click .NextEnter the password for the Controller root user. This is a built-in account with globaladministrative privileges in the Controller. This user can access certain settings not availableto account administrators, such as data retention settings. Enter a username and password for the account administrator in the Controller and thenclick Next. This user will be able to access the Controller UI and create other users. Note that accounts are used in multi-tenancy Controllers to partition access to monitoredapplications among users. Single-tenancy Controllers only have a single, implicit account.See for more information about the types of administrators.AppDynamics Administrator

Usernames and password cannot include the @ character. Also, if this account willbe used to access the REST API, additional limitations on the use of specialcharacters in usernames apply. See for more information.Configure Users

http://docs.appdynamics.com/display/PRO14S/Administrative+Users#AdministrativeUsers-AppDynamicsAdministrator


12. 13. 14.

1.

2.

3.

Select the Demo performance profile then click .NextSelect the default data directory path then click .NextIn the High Availability screen, select as you are not enabling HA for thisNot Applicable,Controller, and click .Next

The installer begins installing the Controller files. When it's done, it attempts to start the Controller. Youcan verify the installation as described next.

Post-Installation Checklist for Linux

Verify Controller InstallationConfigure Swappiness if the Linux Kernel is Newer than 2.1.10

Verify Controller Installation

When the installer completes the Controller automatically starts.

To verify the success of your installation, open a browser to the URL that you configured for theController.

http://:/controller

For the port, use the Application Server Primary Port configured by the installer, which is 8090 bydefault.

Configure Swappiness if the Linux Kernel is Newer than 2.1.10

For better performance, configure swappiness. For details see .Configure Swappiness on LinuxThis feature is available only for Linux kernel versions greater than 2.1.10.

Verify Controller InstallationConfigure Swappiness if the Linux Kernel is Newer than 2.1.10

Next Steps

Now that you have installed and verified the Controller, you must install agents to instrument andmonitor your application.

Open a browser to the URL that you configured for the Controller.

http://:/controller

Log in with the username and password you specified for the account administrator user instep 10 above.The first time you log in, the Getting Started page appears. Click the tab to get started on installing the app agents. For moreDownload Agent Wizardinformation, see Quick Install for the App Agent for Java.


After installation, make sure to verify that your App Agent and Controller are .talking to each otherOnce that's done, you're ready to into what AppDynamics can do. dig deeper

Learn More

Start or Stop the ControllerSelf-Service Install - App Agents for Java

Install the Pro Trial Controller on Windows

Pre-installation Checklist for WindowsRun the Windows InstallerPost-installation Checklist for WindowsNext StepsLearn More

This topic describes how to install a trial instance of the AppDynamics Controller on Windows. Thetrial Controller is identical to the full-service Controller, with all the same features, but subject to a15-day trial license. If you are installing a standard Controller see .Install the Controller on Linux

Pre-installation Checklist for Windows

Confirm the operating system requirements at :Controller System RequirementsWindows Server 2003Windows Server 2008, Windows Server 2008 R2Windows Server 2012 R1 Standard and Datacenter, Windows Server 2012 R2Standard and DatacenterWindows 7 ProWindows 8

Confirm browser and Flash support:Mozilla FireFox 6+Internet Explorer 9+Safari 6+Google Chrome 16+The Controller UI requires Flash Player 10 or greater; AppDynamics recommendsversion 11.

Confirm disk space requirements:50 GB

Confirm CPU, RAM and Disk I/O capacity:2 GB RAM2 CPU Cores1.5 GHz minimumDisk I/O: 50 MB/sec write, 50 MB/sec read, 1.5 MB/sec random

Verify that you have administrative privileges on the Windows machine to launch theController installer.

Download the 32-bit or 64-bit Windows installer file from the Downloads tab on the Support

http://docs.appdynamics.com/display/PRO14S/Verify+App+Agent-Controller+Communicationhttp://docs.appdynamics.com/display/PRO14S/AppDynamics+Essentialshttp://docs.appdynamics.com/display/PRO14S/Self-Service+Install+-+App+Agents+for+Javahttps://www.appdynamics.com/support/


1. 2.

3.

4.

5. 6.

7.

8. 9.

10.

. You'll need to register on the web site to get access to the installer download.page

Make sure that the Controller will be accessible to the application agents and browserclients. If needed, open the firewall to the HTTP port that the Controller will use for HTTP orHTTPS communication, 8090 or 8181, by default.

Run the Windows Installer

Execute the Controller installer .exe file.In the Welcome screen click Next.

Scroll to the bottom of the license agreement page, click accept and then Next.

Click Yes to grant AppDynamics permission to collect usage data statistics from your controller.AppDynamics uses the data to improve the quality of its products and services.

Accept the default installation directory by clicking Next.Verify the default host name and Application Server Primary Port. Note the primary port number, 8090 by default. You will need this later to log in to theController UI from the browser. Verify the other required ports suggested by the installer and click . The installer checksNextthe availability of the ports before presenting them on the screen. If necessary, click Edit

, modify the defaults, and save your changes to use different ports.Ports

Choose single-tenancy mode for the Controller, then click .NextEnter the password for the Controller root user. This is a built-in account with globaladministrative privileges in the Controller. This user can access certain settings not availableto account administrators, such as data retention settings. Enter a username and password for the account administrator in the Controller and then click Next. This user will be able to access the Controller UI and create other users. Note that accounts are used in multi-tenancy Controllers to partition access to monitored

https://www.appdynamics.com/support/


10.

11.

12.

13.

applications among users. Single-tenancy Controllers only have a single, implicit account. See A for more information about the types of administrators.ppDynamics Administrator

Select the Demo performance profile then click .Next

Select the default data directory path then click .Next

In the High Availability screen, select as you are not enabling HA for thisNot Applicable,Controller, and click .Next

The installer begins installing the Controller files. When it's done, it attempts to start the Controller.You can verify the installation as described next.

Post-installation Checklist for Windows

Verify Controller InstallationConfigure the Controller to Run as a Windows Service Exclude the Controller Data Directory from Virus Scanning and Indexing

Verify Controller Installation

To verify your installation, do one of the following:

Click the link to the Controller provided in the installer's "Finish" screen.


http://:/controller

For the port, use the Application Server Primary Port configured by the installer, which is8090 by default.

Configure the Controller to Run as a Windows Service

By default the Controller is not installed as a Windows service. AppDynamics stronglyrecommends that the Controller runs as a service on Windows.

See for information on configuring the installedInstall the Controller as a Windows ServiceController to run as a service on Windows.

Exclude the Controller Data Directory from Virus Scanning and Indexing

See the operational guidelines in for more information aboutInstall the Controller on Windowsexcluding the Controller data directory from virus scanning and indexing services on Windows.

Verify Controller InstallationConfigure the Controller to Run as a Windows Service

Usernames and password cannot include the @ character. Also, if this account willbe used to access the REST API, additional limitations on the use of specialcharacters in usernames apply. See for more information.Configure Users

http://docs.appdynamics.com/display/PRO14S/Administrative+Users#AdministrativeUsers-AppDynamicsAdministratorhttp://docs.appdynamics.com/display/PRO14S/Administrative+Users#AdministrativeUsers-AppDynamicsAdministrator


1.

2.

3.

Exclude the Controller Data Directory from Virus Scanning and Indexing

Next Steps

Now that you have installed and verified the Controller, you can install agents to instrument andmonitor your application.


http://:/controller

Log in with the username and password you specified for the account administrator user instep 10 above.The first time you log in, the Getting Started page appears. Click the tab to get started on installing the app agents. For moreDownload Agent Wizardinformation, see Quick Install for the App Agent for Java.

After installation, make sure to verify that your App Agent and Controller are .talking to each otherOnce that's done, you're ready to into what AppDynamics can do. dig deeper

Learn More

Install the Controller as a Windows ServiceStart or Stop the ControllerSelf-Service Install - App Agents for .NETSelf-Service Install - App Agents for Java

Quick Install for the App Agent for Java

Before You BeginInstrumenting Your JVM with the App Agent for Java

Download the App Agent for JavaInstall the agent on your app serverApply load to your applicationView your application

Learn More

Use these instructions to install the App Agent for Java using the Agent Download Wizard in theController.

If you downloaded the agent from the AppDynamics download zone, see Install the App Agent forJava.

Before You Begin

1. Confirm you have access to acontroller, the web applicationwhere you monitor yourapplication performance:

http://docs.appdynamics.com/display/PRO14S/Verify+App+Agent-Controller+Communicationhttp://docs.appdynamics.com/display/PRO14S/AppDynamics+Essentialshttp://docs.appdynamics.com/display/PRO14S/Self-Service+Install+-+App+Agents+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Self-Service+Install+-+App+Agents+for+Javahttp://download.appdynamics.com/http://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+Javahttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+Java


If you use a SaaScontroller,AppDynamics sentyou the controllerhost in yourWelcome Email.If you use theon-premisecontroller, yousupplied the hostand port at installtime.

2. Identify the startup script foryou the JVM for yourapplication. To enable theagent, you edit the startupscript.

Show more information on startup scripts...

Instrumenting Your JVM with the App Agent for Java

There are four steps to instrument your JVM and begin monitoring:

1. : Use the Agent Download Wizard to configure and download the agent.Download2. : Unzip the agent on your server and add it to your JVM startup script.Install3. : Restart your application and apply load to activate instrumentation.Apply Load4. : Log on to the Controller to monitor application performance.View Your Application

Download the App Agent for Java

The Agent Wizard walks you through configuration steps and helps you download theDownload agent.

Show me the Download Agent Wizard steps...1. Log on to the Controller and


click the Agent Download tab.Wizard

2. Click , then click Java Next.

3. Click to , then Select JVMclick Next.

4. The Controller Location URLwindow displays theconnection info for theController. Click .Next

Click to enable SSLSSLencryption between the agentand the Controller. Enter theSSL port. For AppDynamicsSaaS, the SSL port is 443.

The download wizard configures theagent with information to connect to theController.


5. Enter an application nameor, click an existing applicationname if one exists. Then click

.Next

For new users, it is OK to usethe default . You canMyAppchange it later when knowmore about how you want toorganize your applications inAppDynamics.

6. Enter a tier name. Then click

.Next

For new users, it is OK to usethe default . You canMyTierchange it later when knowmore about how you want toorganize your applications inAppDynamics.


7. Click Click here to

to download theDownloadApp Agent for Java.

Now you're ready to install the.agent on your app server

Install the agent on your app server

After you download the agent, install it to your app server. The final window of the Agent DownloadWizard includes brief instructions for installing the agent.

Show me the steps to install the agent...1. Log on as an administrator to the machine running your Java application. Unzip theAppServerAgent.zip file.

For example, on Linux unzip the agent to . This is the home/appdynamicsdirectory.


1. 2.

unzip AppServerAgent.zip -d /opt/appdynamics/appagent

2. Edit your startup configuration file to include the App Agent for Java.Show more information on startup scripts...

Now you're ready to restart your application and put some load on it.

Apply load to your application

Restart the JVM.Apply load to your application.

The agent instruments the application code and reports metrics back to the Controller. You'reready to .begin monitoring

View your application

Log on to the Controller to seeyour application in action.

From here, you can install moreagents or you can beginmonitoring your application. Thelinks below will help you getstarted:

Learn More

AppDynamics EssentialsQuick Install for the Standalone Machine Agent

http://docs.appdynamics.com/display/PRO14S/AppDynamics+Essentials


Quick Install for the App Agent for .NET

Before You BeginInstrumenting Your CLR with the App Agent for .NET

Download the App Agent for .NETInstall the agent on your app serverApply load to your applicationView your application

Learn More

Use these instructions to install the App Agent for .NET using the Agent Download Wizard in theController.

If you downloaded the agent from the download zone AppDynamics , see Install the App Agent for.NET.

Before You Begin

1. Confirm you have access to acontroller, the web applicationwhere you monitor yourapplication performance:


http://download.appdynamics.comhttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+.NET


2. Verify you've enabled COM+on your system. See To verify

.COM+ Services are enabled

Instrumenting Your CLR with the App Agent for .NET

There are four steps toinstrument your CLR and beginmonitoring:

1. : Use theDownloadAgent Download Wizard toconfigure and download theagent.2. : Run the MSIInstallinstaller package and theAppDynamics AgentConfiguration utility.3. : Apply loadApply Loadto activate instrumentation.4. :View Your ApplicationLog on to the Controller tomonitor applicationperformance.

Download the App Agent for .NET

The Agent Wizard walks you through configuration steps and helps you download theDownload agent.

http://docs.appdynamics.com/display/PRO14S/Resolve+App+Agent+for+.NET+Installation+and+Configuration+Issues#ResolveAppAgentfor.NETInstallationandConfigurationIssues-ToverifyCOM+Servicesareenabledhttp://docs.appdynamics.com/display/PRO14S/Resolve+App+Agent+for+.NET+Installation+and+Configuration+Issues#ResolveAppAgentfor.NETInstallationandConfigurationIssues-ToverifyCOM+Servicesareenabled


Show me the Download Agent Wizard steps...1. Log on to the Controller andclick the Agent Download

tab.Wizard

2. Click , then click .NET Next.

3. Click to select 32-bit or

, then click 64-bit system Next.

7. Click Click here to

to download theDownloadApp Agent for .NET.

Now you're ready to install the.agent on your app server

The download wizard guides youthrough the download process.


1.

2.

3.

4.

Install the agent on your app server

After you download the agent, install it to your app server. The final window of the Agent DownloadWizard includes brief instructions for installing the agent.

Run the MSI installer package and accept the default settings.

When the installation completes, leave checkedLaunch AppDynamics Agent Configuration. Click Finish.The .NET Agent Configuration utility launches. Proceed through the configuration steps andaccept the default settings.

If you're using a SaaS Self-Service Controller, you must include your account nameand access key in the Controller Configuration window.

In the Application Configuration window, enter a name for your business application inthe New Application field.For new users, it is OK to enter "MyApp". You can change it later when know moreabout how you want to organize your applications in AppDynamics.

For installations, AppDynamics recommends you use tierPro Trial Automaticnaming in the Assign IIS applications to tiers window.

On the Configuration Summary window, leave checked.Restart IIS

The configuration utility restarts IIS, so now you're ready to .put load on your application

Apply load to your application

The agent instruments the application code and reports metrics back to the Controller. You'reready to .begin monitoring

View your application

Log on to the Controller to seeyour application in action.

Detailed Configuration InstructionsFor step by step instructions, see .Configure the App Agent for .NETTo instrument Windows services, see Enable the App Agent for .NET for Windows

.ServicesTo instrument standalone applications, see Enable the App Agent for .NET for

.Standalone Applications

http://docs.appdynamics.com/display/PRO14S/Configure+the+App+Agent+for+.NEThttp://docs.appdynamics.com/display/PRO14S/Enable+the+App+Agent+for+.NET+for+Windows+Serviceshttp://docs.appdynamics.com/display/PRO14S/Enable+the+App+Agent+for+.NET+for+Windows+Serviceshttp://docs.appdynamics.com/display/PRO14S/Enable+the+App+Agent+for+.NET+for+Standalone+Applicationshttp://docs.appdynamics.com/display/PRO14S/Enable+the+App+Agent+for+.NET+for+Standalone+Applications


1.

From here, you can install moreagents or you can beginmonitoring your application. Thelinks below will help you getstarted:

Learn More

AppDynamics Essentials

Quick Install for the App Agent for PHP

Before You BeginInstrumenting Your PHP Application with the App Agent for PHP

Download the App Agent for PHPInstall the agent on your app serverApply load to your applicationView your application

Learn More

Use these instructions to install the App Agent for PHP using the Agent Download Wizard in theController.

If you downloaded the agent from the AppDynamics download zone, see Install the App Agent forPHP.

Before You Begin

Confirm you have accessto a controller, the webapplication where you

http://docs.appdynamics.com/display/PRO14S/AppDynamics+Essentialshttp://download.appdynamics.com/http://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+PHPhttp://docs.appdynamics.com/display/PRO14S/Install+the+App+Agent+for+PHP


1.

2.

3.

monitor your applicationperformance:


Verify you have rootaccess to run the install.Verify support for yourenvironment at SupportedEnvironments and

.Versions for PHP

Instrumenting Your PHP Application with the App Agent for PHP

There are f

Documents

AppDynamics Administration (5.24 MB)