Accessing WildFly JMX Bus Remotely with novaordis-jmx: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 12: | Line 12: | ||
==JBoss 6 Classpath== | ==JBoss 6 Classpath== | ||
JBoss 6 exposes the JMX bus over its remoting protocol, so the JMX client needs JBoss remoting support in its classpath. | JBoss 6 exposes the JMX bus over its remoting protocol, so the JMX client needs JBoss remoting support in its classpath, which is available in <tt>${JBOSS_HOME}/bin/client/jboss-cli-client.jar</tt>. | ||
<pre> | <pre> | ||
Revision as of 19:29, 18 June 2017
Internal
Overview
The WildFly JMX bus can be accessed programmatically using standard JMX remoting API, as described in the Remote Access to a JMX Server section. novaordis-jmx is a library that provides a thin layer of functionality in top of the client-side JMX remoting API, with the intention to facilitate programmatic JMX access to a remote JMX bus. Note that novaordis-imx is NOT necessary for programmatic JMX access, but its code introduces a certain degree of convenience, and it can be used as an example for direct use of the JMX remote API.
Classpath
JBoss 6 Classpath
JBoss 6 exposes the JMX bus over its remoting protocol, so the JMX client needs JBoss remoting support in its classpath, which is available in ${JBOSS_HOME}/bin/client/jboss-cli-client.jar.
java ... -cp ...:${JBOSS_HOME}/bin/client/jboss-cli-client.jar:...