Bug 847280
Summary: | Docs are missing instructions on how to configure EAP 6 instances in a domain to allow the JON agent to connect to them | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Tom Fonteyne <tfonteyn> |
Component: | Documentation | Assignee: | Deon Ballard <dlackey> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | JON 3.1.0 | CC: | dlackey, loleary |
Target Milestone: | --- | ||
Target Release: | JON 3.1.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
JON 3.1 with JBoss EAP 6 plugin
|
|
Last Closed: | 2013-03-01 00:34:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom Fonteyne
2012-08-10 12:13:27 UTC
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. Mass closure. |