JMX Access to Standalone EAP 6: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
=Overview= | =Overview= | ||
A generic JMX client connects to a standalone EAP 6 instance | A generic JMX client connects to a standalone EAP 6 instance using [[WildFly_Management_Interfaces#The_Native_API_Endpoint|the native endpoint of the standalone instance's management interface]]. | ||
port (by default 9999), | |||
[[Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access]] | |||
=WildFly Endpoint= | =WildFly Endpoint= | ||
Revision as of 18:09, 18 October 2016
External
- Accessing JMX with jconsole over SSL on EAP 6 https://access.redhat.com/solutions/632773
Internal
Overview
A generic JMX client connects to a standalone EAP 6 instance using the native endpoint of the standalone instance's management interface.
port (by default 9999),
Remoting_WildFly_Subsystem_Concepts#Remoting_and_JMX_Access
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