By default, applications on a single Windows host are mapped to a single business application in the Controller. If needed, you can manually configure the .NET Agent to map different applications on the same Windows host to different business applications in the Controller.
To map applications on a single host to a different business application, you need to edit the
config.xml file manually. The AppDynamics Agent Configuration utility does not offer this configuration option.
After configuring multiple application support as described here, you cannot 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.
Prepare to Configure Multiple Business Applications
Before you configure the .NET Agent, 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.
- 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.
- If you have not already done so, install the .NET Agent. See Install the .NET Agent for Windows
- Run the AppDynamics Agent Configuration utility to generate a config.xml and configure the Controller connection. See Configure the .NET Agent
When prompted, choose Manual for the method of tier generation and assignment.
Currently, the configuration utility only supports mapping one business application per server.
Manually Configure the .NET Agent
Once you have configured the Controller properties for the .NET Agent, instrument your .NET Applications in the config.xml.
config.xmlfile as administrator and edit the file. See 'Where to Configure Agent Properties' on Administer the .NET Agent.
Copy the c
ontroller applicationsblock and paste it as a child element of the
controllerelement. Replace any existing
<application>elements:Show Controller applications code block
applicationelement for each of the business applications in the Controller.
- Edit the
nameattribute for the
applicationelements to match the business application names in the Controller. If the application does not exist yet, the Controller creates it.
- Set the
applicationelement. If the agent cannot 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 the following example,
Ticket Searchis the default business application:Show TicketSearch example
- Edit the
Add configuration elements for the IIS applications or application pools, Windows services, or standalone applications to instrument.
For IIS applications, add the
applicationsblock as a child of the
IISelement. Replace the existing
applicationselement. For more information, see IIS Applications Element.Show IIS Application configuration.
For IIS application pools, add the
application poolsblock as a child of the
IISelement. Replace the existing
application-pools>element. See IIS Application Pools ElementShow IIS Application Pool configuration.
For Windows services or standalone applications, add the
standalone-applicationsblock as a child of the
app-agentselement. See Standalone Applications ElementShow Windows service and standalone application configuration
- 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 .NET Agent Configuration Properties.
- For each application element set the
controller-applicationattribute 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
nameattribute to the business application tier name.
- After you complete configuration, save the changes to the
- Restart the
- Restart IIS applications or application pools, Windows services, and standalone applications.
- 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.
config.xml file demonstrates configuration for multiple business applications in the Controller. Because the Windows service TicketService does not specify a
controller-application attribute, it reports to the default business application,
Ticket Search Engine. All applications in the
TravelAPIPool pool report to the
Travel Search Engine.
Agent Configuration Properties for Multiple Application Support
Multiple business application support includes configuration properties for the .NET Agent. These configuration properties supersede the ones documented in .NET Agent Configuration Properties.
Controller Applications Element
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.
Controller Application Element
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"/>
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.
Application default attribute
Set the application
default attribute to
true for one c
ontroller 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
standalone-application elements accept the
controller-application attribute. Set the value to the
controller application element name. If you do not 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">