posted 9 years ago
In that case you would need to first where your JMX application is going to live, will it also be a standalone java application or will that be deployed to some container.
Then to monitor the desktop application is pretty similar to monitoring an application deployed in a server. In both instances you need to make sure that the java command was started with options that enable JMX (remote) monitoring.
You would only be able to access MBeans exposed by the Java runtime in a standalone application (what you would normally see using jconsole) so if you need extra info/methods to be exposed you would have to change the application you are monitoring to add the required mbeans.