JMX Access to Standalone EAP 6: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
=WildFly Endpoint= | |||
==WildFly Endpoint Authentication== | |||
=JMX Client= | |||
==JMX Client Classpath== | |||
==URL== | |||
==Authentication== | |||
Revision as of 17:06, 18 October 2016
External
- Accessing JMX with jconsole over SSL on EAP 6 https://access.redhat.com/solutions/632773
Internal
Overview
WildFly Endpoint
WildFly Endpoint Authentication
JMX Client
JMX Client Classpath
URL
Authentication
JBoss Remoting provides the transport of the JSR-160 Java Management Extensions (JMX) Remote API compliant implementation of a JMXConnector that can be used by standard monitoring applications to access the JMX bus. A JMX client must be configured to connect to the