JMX Access to Standalone EAP 6: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 14: Line 14:
=WildFly Endpoint=
=WildFly Endpoint=


A generic JMX client must connect to  
A generic JMX client must connect to [[WildFly_Management_Interfaces#The_Native_API_Endpoint|the native endpoint of the standalone instance's management interface]].
 
The network interface and port binding for the endpoint are specified as "management-native" socket binding:
 
<pre>
...
<interfaces>
    <interface name="management">
        <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
    </interface>
  ...
</interfaces>
 
...
 
<socket-binding-group name="standard-sockets" ...>
    ...
    <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
</socket-binding-group>
...
</pre>
 
<blockquote style="background-color: Gold; border: solid thin Goldenrod;">
:<br>If the standalone instance runs with a specific port offset, the management endpoint port value must account for that offset.<br><br>
</blockquote>


==WildFly Endpoint Authentication==
==WildFly Endpoint Authentication==

Revision as of 18:22, 18 October 2016

External

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 Remoting Concepts - Remoting and JMX Access. 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.

WildFly Endpoint

A generic JMX client must connect to the native endpoint of the standalone instance's management interface.

The network interface and port binding for the endpoint are specified as "management-native" socket binding:

...
<interfaces>
    <interface name="management">
        <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
    </interface>
   ...
</interfaces>

...

<socket-binding-group name="standard-sockets" ...>
    ...
    <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
</socket-binding-group>
...

If the standalone instance runs with a specific port offset, the management endpoint port value must account for that offset.

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