This file should exist for each of your JVM instances(SASServer1_1, 2_1, 12_1, etc):
config/Lev1/Web/WebAppServer/SASServerX_X/bin/setenv.sh
In there, you will find the following line:
CLASSPATH="$CATALINA_BASE/lib/log4j.jar:$CATALINA_BASE/lib:$CATALINA_BASE/conf:$JRE_HOME/../lib/tools.jar
Append the path to your .jar file to this classpath so that it looks like this:
CLASSPATH="$CATALINA_BASE/lib/log4j.jar:$CATALINA_BASE/lib:$CATALINA_BASE/conf:$JRE_HOME/../lib/tools.jar:/wherever/your/jar/file/is.jar"
I'm not sure how supported this is, but it should help you assuming you're trying to implement Object Instance Tracking for Java. Also, if you're having capacity or stability issues with ECM, I doubt AppDynamics will give you enough info to do anything useful. For monitoring the actual workload I would recommend you have a look at our workload monitoring product, ESM.
Nik