Is there any restriction on controller file name controller-info.xml?

[Nandy.S]

Is there any restriction on controller file name controller-info.xml?

We are passing the controller file from our custom UI where user uploads the controller file.

We just wanted to know whether AppDynamics expects the controller file name should be controller-info.xml

or it can be any file name which can be passed to start the AppDynamics Java Agent at the backend?

[Eric.Miller]

I'm no expert, but I'm pretty sure the javaagent.jar file expects it to be controller-info.xml. Not sure if it helps but I think there is a way to pass information as systems properties in the command line, something like:-javaagent <AGENT_HOME>/javaagent.jar=uniqueID=<YOUR_JVM_NAME>

[Sam.Hosseini]

Hi Nandy.S,

The AppDynamics Java Agent requires a valid controller-info.xml file to be present with the correct filename in the agent installation directory (conf and verXXX/conf directories).

We do not have a method of specifying a different file name for this configuration file, so trying to install the agent with a different named .xml configuration file is not supported.

However, you can specify the java agent configuration properties other ways, such as using environment variables or java system properties.

Please see the links below which cover these topics in detail:

https://docs.appdynamics.com/display/PRO45/Install+the+Java+Agent

https://docs.appdynamics.com/display/PRO45/Java+Agent+Directory+Structure

https://docs.appdynamics.com/display/PRO45/Java+Agent+Configuration+Properties

https://docs.appdynamics.com/display/PRO45/Use+Environment+Variables+for+Java+Agent+Settings

https://docs.appdynamics.com/display/PRO45/Use+System+Properties+for+Java+Agent+Settings

https://docs.appdynamics.com/display/PRO45/Automate+Java+Agent+Deployment

Regards,

Sam