Red Hat Bugzilla – Bug 847280
Docs are missing instructions on how to configure EAP 6 instances in a domain to allow the JON agent to connect to them
Last modified: 2014-10-23 08:30:03 EDT
Description of problem:
is missing instructions on how to configure instances in a domain to allow the JON agent to connect to them
Version-Release number of selected component (if applicable):
The below should be added to that chapter:
Instances in a JBoss EAP 6 domain do not have the http interface enabled by default
With "instanceName" the actual name of the instance, execute these CLI commands
# create a local interface for JON
# add the http interface, change "ManagementRealm" if not using the default
This doesn't seem to be an accurate BZ. By default, EAP 6, even in domain mode, is already configured for use with JON. Additionally, there is no special configuration for EAP to make JON work. JON is simply using the HTTP management interface which is exposed by default.
I suggest for documentation purposes that we simply mention that the JBoss AS 7 plug-in uses the HTTP management interface for managing and monitoring JBoss AS 7 and if the HTTP management interface has been removed or disabled, the plug-in will not be able to connect and therefore no management or monitoring capability will be supported. An example of configuring the management interface could be included but it should be the default interface as originally configured with EAP and be unrelated to JON itself.
Bumping to 3.1.2.