How to monitoring an exe file (as dtclient.exe)?
Hi guys.
I've a customer that needs to monitor the client side of a client/server application, with a fat client based in Java. The issue is that the application is an exe file with plugins that are configured with an ini file:
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20120522-1813
-nl
es_ES
--launcher.appendVmargs
-vmargs
-XX:+UnlockDiagnosticVMOptions
-XX:+UnsyncloadClass
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=P:\\pyxis_dumps\\
-Dfile.encoding=UTF8
-Dosgi.requiredJavaVersion=1.6
-Dorg.eclipse.net.core.enableProxyService=false
-Dsun.net.client.defaultConnectTimeout=5000
-Dsun.net.client.defaultReadTimeout=60000
Is pretty similar as dtclient.exe structure... so... Is it possible to hook an agent to this kind of applications? If the answer is yes... where has the agent be deployed? Anybody has hooked the dtclient.exe?
Thanks in advance and best regards
JMI
Hi.
Finally I've hooked the dtclient.exe adding the agent in the dtclient.ini in the path C:\Users\cwes-jiglesia\.dynaTrace\dynaTrace 6.1.0... and it works fine... so i guess that the application of the customer should be similar... the only point is find the correct place to put the agent.
Thanks!
JMI
Hi, David.
I'm trying with the dtclient.exe and the command line that is being executed is this:
"D:\Program Files\dynaTrace\dynaTrace 6.1.0\jre\bin\javaw.exe" -Xmx1536M -XX:MaxPermSize=128M -Djava.library.path=plugins -Dosgi.checkConfiguration=true -Dosgi.bundles.defaultStartLevel=4 -Declipse.registry.nulltoken=true "-Dosgi.instance.area=@user.home/.dynaTrace/dynaTrace 6.1.0/" "-Dosgi.configuration.area=@user.home/.dynaTrace/dynaTrace 6.1.0/client/osgi" -Declipse.product=com.dynatrace.diagnostics.client.productId "-Dosgi.splashPath=platform:/base/plugins/com.dynatrace.diagnostics.client.branding, platform:/base/plugins/com.dynatrace.diagnostics.client.branding.jar" "-Dosgi.bundles=org.eclipse.equinox.common@2:start, org.eclipse.core.jobs@2:start, org.eclipse.equinox.registry@2:start, org.eclipse.core.runtime@2:start, org.eclipse.equinox.app@2:start, org.eclipse.update.configurator@3:start, org.eclipse.equinox.event@start, org.eclipse.equinox.ds@start, org.eclipse.equinox.preferences@start, org.eclipse.core.contenttype@start" -Dorg.osgi.framework.language=en -Dosgi.framework.extensions=com.dynatrace.diagnostics.bootstrap.hook -Dosgi.nl=en_US -Deof=eof -Duser.home=C:\Users\cwes-jiglesia -Dcom.dynatrace.diagnostics.WatchDogTimeout=0 "-Dcom.dynatrace.client.configPath=C:\Users\cwes-jiglesia\.dynaTrace\dynaTrace 6.1.0" -Dcom.dynatrace.client.restartCount=0 "-Dcom.dynatrace.diagnostics.server.ini=C:\Users\cwes-jiglesia\.dynaTrace\dynaTrace 6.1.0\dtclient.ini" -Dosgi.os=win32 -Dosgi.ws=win32 -Dosgi.arch=x86_64 -Dcom.dynatrace.diagnostics.WatchDogPort=50000 -jar "D:\Program Files\dynaTrace\dynaTrace 6.1.0\client\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar" -name dtclient -showsplash -launcher "D:\Program Files\dynaTrace\dynaTrace 6.1.0\dtclient.exe"
If i try to execute it directly, the splash windows is shown, but the dtclient is not starting... also, I've tried to insert the -agenpath in several places... and doesn't work.
Thanks!
JMI
Hi, guys.
I've tried adding the -agentpath:D:\agent\lib\dtagent.dll=name=Pyxis_Clientes_JMI,server=localhost:9998 to the .ini and nothing happens... is like this line is not being recongnized by the javaw.exe launcher.
All the best
JMI
Have you checked the command line in task manager to see if it was passed as an argument? Have you tried inserting after the "vmargs" line or after the "-nl" line (after the "es_ES" line)?
I have instrumented our dtserver in the past for troubleshooting and you basically just add the agentpath in the settings.
For the dtserver, support told me that the agentpath should be added to dtserver.ini right before the line that says "-server".
Disclaimer: Please do not instrument your DT server without involvement from Dynatrace Support...
Never tried this. My guess is that you can add the agent params in the ini file where the JVM memory settings are present.
-Sreerag
