D
dbeavon
Guest
Based on investigating your JMX api in Jconsole and comparing to your REST api in oemanager, it seems that the PASOE team has invested quite a bit more of their time on the JMX side of things. It also seems that there may be some redundant work going on in the oemanager webapp. I am not a Java programmer by any stretch, but I was wondering if you have considered using Jolokia to wrap your JMX api and make it available via REST as well. That way it would be more easily accessible and we wouldn't have to rely on duplicated efforts (both on the programming side of things and in your documentation). I was first aware of JMX when using the Jboss AMQ product which allows us to perform JMX management functions via REST url's. Initially I had believed that JMX was inherently a REST-ful interface based on HTTP. Now that I have seen JMX *without* Jolokia, it is clear that the REST portion is not always an integral component of JMX (but it probably should be). Here are some Jolokia links. As a powershell user it would help greatly if your JMX api was accessible via REST: Jolokia – Overview stackoverflow.com/.../connect-to-jmx-using-powershell
Continue reading...
Continue reading...