Re: Unsure of how to configure standalone .net processes

Hi,

The sintax is right, you need to take care of the command-line attribute:

<standalone-application executable="D:\sikoms\applications\SIKWindowsServices\SIKWindowsServices.exe" command-line="-x">

You need to provide de attribute to distinguish between different services provided by the same application executable, in the same path. If your services are in different paths, do not include command-line.

As the docs says, run the following from an elevated rights cmd.exe:

tasklist /m "mscor*"

Verify your services are in the list. If not, they aren't .NET services, so they couldn't be instrumented.

Then take a look at the command line of the service (using services.msc) and complete the entry in config.xml. Restart the AppDyn Coordinator service and the service to be instrumented. Wait 1, 2 minutes to the controller to get updated, your new tier is created and visible on the GUI.

An example of multiple services in one tier, with different paths:

<standalone-applications><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR2\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR3\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application><standalone-application executable="E:\SNET\ACME\Programs\TEF\IFR4\ACMETIFR.exe"><tier name="OPS-TIFR"/></standalone-application></standalone-applications>

Your last resort is looking at the agent log, it will tell you what's going on inside it.

Hope it helps, regards,

Luis