AppDynamics Application Intelligence Platform
By default, AppDynamics enables the App Agent for .NET only for IIS worker processes. This topic describes how to edit the config.xml file to enable the agent for standalone applications.
Before you enable the App Agent for .NET for standalone applications, you must install the agent. We recommend using the AppDynamics Agent Configuration utility to perform basic configuration tasks.
Run the AppDynamics Agent Configuration utility to generate a config.xml. See Configure the App Agent for .NET.
Even though the Configuration Utility only instruments IIS Applications, it is useful to create the config.xml and specify Controller connection properties.
If you have previously instrumented app agents for IIS applications, don't run the configuration utility. You already have a config.xml.
Use the configuration utility to do the following:
Choose Manual for the method of tier generation and assignment. Don't assign assign any tiers for any IIS Applications. This disables instrumentation for all IIS applications.
Once you have configured the Controller properties for the App Agent for .NET, instrument your standalone application by adding an xml element for it to the config.xml.
Edit the config.xml file as an administrator. See Where to Configure App Agent Properties.
If you haven't instrumented IIS applications, the file contains minimal configurations for Controlller connectivity and the machine agent. Verify the Controller properties and the Business Application name
If you have already instrumented IIS applications, you will see their configurations under the IIS element.
Add the Standalone Applications block as a child of the App Agents element. Create a Standalone Application element for each standalone application you want to instrument. Use the Tier element to assign the instrumented application to a tier in the Controller. See App Agent for .NET Configuration Properties
Set the Standalone Application element executable attribute to the executable file name. Do not include the full path to the executable.
For example, if the full path to the standalone application is C:\Program Files\MyApplication\MyStandaloneApp.exe, set the executable element to "MyStandaloneApp.exe". The file extension is optional, so "MyStandaloneApp" also works.
This sample config.xml demonstrates instrumentation for a standalone application:
Restart the standalone application.