Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
Recently, I'm trying to standardize our instrumentation process. I was checking the folder directory of AppDynamics Java Agent and found out that there are two javaagent.jar. One on the root directory, and another one inside the version folder.
Solved! Go to Solution.
Thanks for posting your question on the Community. I found this AppD Docs page that discusses the Java Agent Directory structure https://docs.appdynamics.com/display/PRO45/Java+Agent+Directory+Structure
Note: Be sure to look at the sidebar navigation when viewing this documentation as there could be other useful pages nested.
If you gain any insight from that documentation, can you please share what you learned back on this post. This helps keep the knowledge sharing alive in the community.
Ryan, AppDynamics Community Manager
Hi @Ryan.Paredez !
Thank you for your reply! I have checked the link you gave and found out the following:
So to answer my previous questions:
1. What's the difference between the top-level javaagent.jar and the one inside the version folder?
The top-level javaagent.jar "bootstraps" the one inside the version folder.
2. Thinking of the long term, there might be times that we need to update the java agent on the target host. When updating the java agent, we might need to update environment variables, config files, and other critical metrics. With this, is there a possible way to point to the java agent using a standard (non-changing) directory?
It might be possible to just point to the javaagent.jar on root directory.
To further validate my understanding, by term "bootstraps", does it mean it calls the java agent inside the version folder? Also on this statement: "The configuration files in this directory are used by an agent if a more specific version of the configuration file does not exist in the version-specific conf directory"; going back to my question number 2. I can still point to the root javaagent.jar, then use the configuration folder on the root directory?