JMX Access to Standalone EAP 6: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
=Overview= | =Overview= | ||
JBoss Remoting provides the transport of the [[JSR 160 Java Management Extensions (JMX) Remote API|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. | |||
* Identify the WildFly interface | |||
* Describe authentication | |||
* Describe client configuration | |||
** Classpath | |||
** URL | |||
** Authentication | |||
<font color=red> | |||
JBoss Remoting provides the transport of the [[JSR 160 Java Management Extensions (JMX) Remote API|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 | |||
</font> | |||
Revision as of 17:05, 18 October 2016
External
- Accessing JMX with jconsole over SSL on EAP 6 https://access.redhat.com/solutions/632773
Internal
Overview
- Identify the WildFly interface
- Describe authentication
- Describe client configuration
- 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