RHQ does not have a JConsole-type JMX mbean browser. The JMX support is used to interact with the mbeans backing metrics or operations defined in RHQ plugins. For EAP 6.1 there is the AS7 plugin which should discover and report on the appserver. It provides robust RHQ support for managing EAP6.
Thanks for the reply. I am 100% sure the AS7 plugin doesn't report any mbeans either.
The only to view mbeans is via importing a new JMX Server, the JMX template doesn't reflect to the new jmx remoting protocol since JBoss 7.1+. So I figured out to use JDK5 template and change the connection URL to service:jmx:remoting-jmx://XXXX.com:4447, and it worked out of the box. (only JDK5 template would work in this case.). The JMX plugin code needs to be updated to add template support of the jsr-160 the jmx remoting protocol to talk to JMX servers in a jvm.