JMX Access to Standalone EAP 6: Difference between revisions
| Line 10: | Line 10: | ||
=Overview= | =Overview= | ||
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]]. | 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]]. For an in-depth explanation on how that works, see [[]]. Specific JBoss libraries must be added to the generic client's classpath, and we will show how those can be added for Visual VM and jconsole. Also, the access must be secured by adding a specific user and its associated password to the management realm, associated with the native management interface. | ||
Revision as of 18:13, 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. For an in-depth explanation on how that works, see [[]]. Specific JBoss libraries must be added to the generic client's classpath, and we will show how those can be added for Visual VM and jconsole. Also, the access must be secured by adding a specific user and its associated password to the management realm, associated with the native management interface.
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