AppDynamics Application Intelligence Platform
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.
Before you configure the App Agent for .NET, you must install the agent. Use the AppDynamics Agent Configuration utility to perform basic configuration tasks.
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.
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.
When prompted, choose Manual for the method of tier generation and assignment.
Currently the configuration utility only supports mapping one business application per server.
Once you have configured the Controller properties for the App Agent for .NET, instrument your .NET Applications in the config.xml.
Open the config.xml file as administrator and edit the file.
Copy the Controller Applications block and paste it as a child element of the Controller element. Replace any existing
Add an Application element for each of the business applications in the Controller.
In this example, Ticket Search is the default business application:
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.
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.
For Windows services, add the Windows Services block as a child of the App Agents element. For more information, see Windows Services Element.
For standalone applications, add the Standalone Applications block as a child of the App Agents element. For more information, see Standalone Applications Element.
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.
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.
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.
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.
<application name="MyDotNetApplication" default="true"/>
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.
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.
Required: For one application in multiple application configurations
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">