JVM appagent installation problem

[CommunityUser]

I believe that there's either a problem in how the downloads are packaged, or a problem with the JVM app agent documentation.

For example, unzipping AppServerAgent-4.0.2.0.zip gives me:

conf/

utils/

ver4.0.2.0/

javaagent.jar

readme.txt

If you look in ver4.0.2.0 it pretty much duplicates what's in the top level, plus a whole lot more files.

If I unzipped this into /var/appdynamics, the install instructions says that this becomes the agent_home and to use "-javaagent:<agent_home>/javaagent.jar".  But this does not work.  You need to use /var/appdynamics/ver4.0.2.0 as the agent_home instead.

I'm guessing it's the packager that's broken since it used to work just fine pre-4.0.

[Arun_Dasetty]

Hi, 

We see the folder structure changes is expected for 4.x agent releases, we expect -javaagent:<agent_dir>/javaagent.jar Or -javaagent:<agent_dir>/ver4.0.0.0/javaagent.jar should work fine as well, Can you confirm the error you see when you used the former format? 

[CommunityUser]

The problem with using "-javaagent:<agent_dir>/javaagent.jar" is that changes to conf/controller-info.xml <agent_dir> don't get completely picked up.  It does not read controller-host and controller-port, although it does read everything else.

You have to change ver4.x/conf/controller-info.xml for it to work.

[Arun_Dasetty]

Hi,

we replicate the issue in local and have filed an internal request for this , thanks again for the pointer on this.

[CommunityUser]

It would also be great if this could revert to the 3.x package structure.  I have scripts that automate the deployment/update and having to figure out the subfolder based on the version number is very annoying.  Especially since the version number doesn't always match the version number of the download exactly (e.g. 4.0.3.0 vs 4.0.3).

[Arun_Dasetty]

Hi,

We see the changes in agent directory have lot related aspects and enhancement and scope for other case, as we see 3.9.x agent is compatable with 4.x controller we request you to go ahead with 3.9.x agent on 4.x UI, hope that is an option for you.

[CommunityUser]

In that case how about a consistent name for the ver4.x subdirectory?

[Arun_Dasetty]

Hi , We understood your concern on automation of using older db agent structure , what i could suggest here is you could hard code the agent version URL to particular download agent version say: https://download.appdynamics.com/onpremise/public/archives/4.0.0.5/AppServerAgent-4.0.0.5.zip and the folder structure after ver4.0.0.5 or the agent version download have same structure after <agent_dir>/<ver> path, hope that information helps.