[jboss-jira] [JBoss JIRA] (HAWKULARQE-71) Test Hawkular Java Agent

[Sunil kondkar (JIRA)]

    [ https://issues.jboss.org/browse/HAWKULARQE-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408320#comment-13408320 ] 

Sunil kondkar commented on HAWKULARQE-71:
-----------------------------------------

EAP6 is not discovered in CFME when installed on openshift with below image:
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-6/eap64-openshift:1.5
Reference bug: https://bugzilla.redhat.com/show_bug.cgi?id=1452118

> Test Hawkular Java Agent
> ------------------------
>
>                 Key: HAWKULARQE-71
>                 URL: https://issues.jboss.org/browse/HAWKULARQE-71
>             Project: Hawkular QE
>          Issue Type: Task
>            Reporter: Hayk Hovsepyan
>            Assignee: Sunil kondkar
>            Priority: Minor
>
> There is a new Java Agent (HJA) that you can run in any JVM (including
> but not limited to EAP-based projects). You do so by passing in a
> "-javaagent" command line option to your JVM (e.g. java
> -javaagent=hawkular-javaagent.jar=config=config.yaml -jar my-app.jar
> ...yadda...). There are two additional properties you must set in
> standalone.conf if you want to run it inside an EAP JVM. The README will
> have the details.
> This new HJA is configured with a yaml file that largely mimics all the
> standalone.xml data that HWFA has. There is no ${x} support in the YAML
> file right now.
> This new HJA can talk to any EAP or WildFly server over the DMR management
> API. It can do deployments to your EAP/WildFly servers and monitoring of
> EAP/WildFly subsystems just like HWFA can.
> This new HJA can talk to any JMX server just like HWFA can (it will talk to
> the local MBeanServer or, if remotely monitoring a JMX server, it will talk
> to it over Jolokia/REST API).
> This new HJA can NOT run directly inside of a Host Controller due to
> https://issues.jboss.org/browse/WFCORE-2526 - however, you can run HJA
> externally in its own JVM (e.g. java -jar hawkular-javaagent.jar
> config=config.yaml) and have its config.yaml point to a remote Host
> Controller and you'll get the same functionality.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)