AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

Skip to end of metadata
Go to start of metadata

Multiple business application support in the App Agent for .NET requires manually editing the config.xml to use a schema that the .NET Agent configuration utility doesn't currently support.

If you follow these instructions to configure multiple application support, you can't use the configuration utility to make configuration changes afterward. If you launch the configuration utility on a server where you've configured multiple application support, the utility will prompt you to delete the configurations.

Take me directly to the Sample Configuration.

Previous versions of the App Agent for .NET required that monitoring data for all .NET applications running on a Windows host report to one business application in the Controller. This topic describes how to configure the App Agent for .NET to register different applications on the same Windows host with multiple business applications in the Controller.

To learn more about AppDynamics business applications, see Logical Model.

Preparing to Configure Multiple Business Applications

Before you configure the App Agent for .NET, you must install the agent. Use the AppDynamics Agent Configuration utility to perform basic configuration tasks.

  1. Identify how you want to organize your business applications and identify the business application names.

    For example, consider a Windows host running IIS. The IIS instance serves two applications for two separate customers: Ticket Search and Travel Search. The applications perform similar functions, but it makes sense to monitor them separately because they function independently. In this case, create two business applications based upon the application name: Ticket Search Engine and Travel Search Engine.

    (info) AppDynamics doesn't correlate business transaction activity across business applications. If a tier in the first business application makes an exit call to a second tier in another business application, the second tier displays as an un-instrumented backend in the first business application.

  2. Map your IIS applications or application pools, Windows services, and standalone applications to tiers in the different business applications.

    For example, map the TicketSearch site to the Ticket Search Web tier in the Ticket Search Engine business application. Map the TravelSearch site to the Travel Search Web tier in the Travel Search Engine business application.
       
  3. If you have not already done so, install the App Agent for .NET. See Install the App Agent for .NET.

  4. Run the AppDynamics Agent Configuration utility to generate a config.xml and configure the Controller connection. See Configure the App Agent for .NET

  5. When prompted, choose Manual for the method of tier generation and assignment.

    Currently the configuration utility only supports mapping one business application per server.

Configuring the App Agent for .NET for Multiple Business Applications

Once you have configured the Controller properties for the App Agent for .NET, instrument your .NET Applications in the config.xml.

  1. Open the config.xml file as administrator and edit the file.

  2.  Copy the Controller Applications block and paste it as a child element of the Controller element. Replace any existing <applications> or <application> elements:

        <!--Configure multiple business applications-->
        <applications>
          <application name="ApplicationName1" default ="true"/>
          <application name="ApplicationName2"/>
        </applications>
  3. Add an Application element for each of the business applications in the Controller.

    • Edit the name attribute for the Application elements to match the business application name in the Controller. If the application doesn't exist yet, the Controller creates it.
    • Set the default attribute to "true" for one Application element. If the agent can't find a match for the business application name in the IIS application, Windows service, or standalone application configuration, the tier reports to the default business application.

    In this example, Ticket Search is the default business 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">
        <!--Configure multiple business applications-->
        <applications>
          <application name="Ticket Search" default ="true"/>
          <application name="Travel Search"/>
        </applications>
      </controller>
    ...
  4. Add configuration elements for the IIS applications or application pools, Windows services, or standalone applications to instrument.

    For IIS applications, add the IIS Applications block as a child of the IIS element. Replace any existing <applications> element. For more information, see IIS Applications Element.

     Show IIS Application configuration.
    <applications>
         <application path="/" site="FirstSite" controller-application="Application1">
             <tier name="FirstSite Tier"/>
         </application>
         <application path="/" site="SecondSite" controller-application="Application2">
             <tier name="SecondSite Tier"/>
         </application>
    </applications>

    For IIS application pools, add the IIS Application Pools block as a child of the IIS element. Replace any existing <application-pools> element. For more information, see IIS Application Pools Element.

     Show IIS Application Pool configuration.
    <application-pools>
        <application-pool name="MyAppPool1" controller-application="Application1">
            <tier name="App1 AppPool Tier"/>
        </application-pool>
        <application-pool name="MyAppPool2" controller-application="Application2">
            <tier name="App2 AppPool Tier"/>
        </application-pool>
    </application-pools>

    For Windows services, add the Windows Services block as a child of the App Agents element. For more information, see Windows Services Element.

     Show Windows service configuration.
    <windows-services>
        <windows-service name="Service1" controller-application="Application1">
            <tier name="App1 Service Tier"/>
        </windows-service>
        <windows-service name="Service2" controller-application="Application2">
            <tier name="App2 Service Tier"/>
        </windows-service>
    </windows-services>

    For standalone applications, add the Standalone Applications block as a child of the App Agents element. For more information, see Standalone Applications Element.

     Show standalone application configuration.
    <standalone-applications>
        <standalone-application executable="App1.exe" controller-application="ApplicationName1">
            <tier name="App1 Standalone Tier"/>
        </standalone-application>
        <standalone-application executable="App2.exe" controller-application="ApplicationName2">
            <tier name="App2 Standalone Tier"/>
        </standalone-application>
    </standalone-applications>
  5. Configure your application elements as follows:
    • Add the corresponding element for each IIS application or application pool, Windows service, or standalone application to instrument. For information on specific elements see App Agent for .NET Configuration Properties.
    • For each application element set the controller-application attribute to the name of the corresponding business application. If you omit the controller-application attribute, the agent adds the application to a tier in the configured default business application.
    • Set the Tier element name attribute to the business application tier name.
       
  6. After you complete configuration, save the changes to config.xml.

  7. Restart the AppDynamics.Agent.Coordinator service.

  8. Restart IIS applications or application pools, Windows services, or standalone applications.

  9. As your applications begin processing traffic, the agent registers them with the Controller. Log on to the Controller to see that your applications have registered with the corresponding business application.

Sample Configuration

This sample config.xml demonstrates configuration for multiple business applications in the Controller. Because the Windows service TicketService doesn't specify a controller-application attribute, it reports to the default business application Ticket Search Engine. All applications in the TravelAPIPool report to the Travel Search Engine.

<?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">
    <!--Configure multiple business applications-->
    <applications>
      <application name="Ticket Search Engine" default ="true"/>
      <application name="Travel Search Engine"/>
    </applications>
  </controller>
  <machine-agent />
  <app-agents>
    <IIS>
      <automatic enabled="false" />
      <application-pools>
        <application-pool name="TravelAPIPool" controller-application="Travel Search Engine">
            <tier name="Travel APIs"/>
        </application-pool>
      </application-pools>
      <applications>
        <application path="/" site="TicketSearch" controller-application="Ticket Search Engine">
            <tier name="Ticket Search Web"/>
        </application>
        <application path="/" site="TravelSearch" controller-application="Travel Search Engine">
            <tier name="Travel Search Web"/>
        </application>
      </applications>
    </IIS>
    <windows-services>
        <windows-service name="TicketService">
           <tier name="Ticket Service"/>
        </windows-service>
    </windows-services>
  </app-agents>
</appdynamics-agent>

 

Agent Configuration Properties for Multiple Application Support

This section describes the configuration properties that apply to multiple business application support. These configuration properties are in addition to and supersede the ones documented in Agent Configuration Properties.

Controller Applications Element

The Controller Applications element is a child of the Controller element. It is a container element for all controller applications elements that map to business applications in the Controller.

Required Element: <applications>

Controller Application Element

The Controller Application element is a child of the Controller Applications element. It indicates the name of the logical business application you see in the Controller. When you have more than one Controller Application element, you must set the default attribute to "true" for one of them.

Required Element: <application name="MyDotNetApplication" default="true"/>

Application name attribute

Set the application name attribute to the business application name in the Controller. If the application name does not exist, the Controller creates it when the agent registers.

Type: String
Default: None
Required: Yes

Application default attribute

Set the application default attribute to "true" for one Controller Application element. Instrumented applications without the controller-application attribute register with the default business application in the Controller.

Type: Boolean
Default: false
Required: For one application in multiple application configurations

Controller-Application Attribute

The IIS Application, IIS Application Pool, Windows Service, and Standalone Application elements accept the controller-application attribute. Set the value to the Controller Application element name. If you don't include a controller-application attribute, the application registers with the default business application.

For example, an IIS application:

<application path="/" site="MySite" controller-application="My Business Application">

Type: String
Default: None
Required: No