AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

Child pages
  • Enable the App Agent for .NET for Standalone Applications

AppDynamics Inc.

Skip to end of metadata
Go to start of metadata

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.

Preparing to Configure the App Agent for .NET 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.

  1. If you have not already done so, install the App Agent for .NET. See Install the App Agent for .NET
  2. 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.

    (info) 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:

    • Change the location of the Logs directory and assign permissions.
    • Configure and test connectivity to the Controller.
    • Set the Business Application for the agent.

    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.

Configuring the App Agent for .NET for Standalone 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.

  1.  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

    <?xml version="1.0" encoding="utf-8"?>
    <appdynamics-agent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <controller host="mycontroller.mycompany.com" port="8090" ssl="false">
        <application name="My Business Application" />
      </controller>
      <machine-agent />
      <app-agents>
        <IIS>
          <applications />
        </IIS>
      </app-agents>
    </appdynamics-agent>
    

    If you have already instrumented IIS applications, you will see their configurations under the IIS element.

  2. 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

    <standalone-applications>
       <standalone-application executable="MyStandaloneApp.exe">
         <tier name="Standalone Tier" />
       </standalone-application>
       <standalone-application executable="MyOtherStandaloneApp.exe">
         <tier name="Standalone Tier" />
       </standalone-application>
    </standalone-applications>
    

    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:

    <?xml version="1.0" encoding="utf-8"?>
    <appdynamics-agent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <controller host="mycontroller.mycompany.com" port="8090" ssl="false">
        <application name="My Business Application" />
      </controller>
      <machine-agent />
      <app-agents>
        <IIS>
            <applications />
        </IIS>
        <standalone-applications>
          <standalone-application executable="MyStandaloneApp.exe">
            <tier name="Standalone Tier" />
          </standalone-application>
        </standalone-applications>
      </app-agents>
    </appdynamics-agent>
    
  3. Restart the AppDynamics.Agent.Coordinator.
  4. Restart the standalone application.

    If your standalone application does not implement any of the frameworks we instrument by default, you must configure a POCO entry point for a class/method in your application for the agent to begin instrumentation. See Supported Environments and Versions for .NET and POCO Entry Points.

Learn More