matta785

Hey thanks SteveK. I couldn't think of a way either but its reassuring what you say is what the path i've been on in the past. Appreciate ya.

Sounds good. If I can't seem to get it working with your doc links, i'll open a support case.

I have the same problem. Any fix? I am using the local agent install running under local system account. I have a handful of servers working, but thats because they have the enormous HP Insight Manager installed locally. 

Okay, this is what i had to do for it to work. From solarwinds: Must have agentless monitor for jmx. Also, know a dedicated port to use in the jmx monitor. On the windows server/websphere server, went into java virtual machine, process definition and added these parameters below what was already there. 8686 is solarwinds…

Good thought. Looked into it, but doesn't seem to be the situation for me. The same node returned a list of processes one hour, and the next time it returned none on the same alert.

I'm trying to use jmx. I'll look more at these links and see what I can figure out.

Thanks for this info. I had found this. I just performed the following and now getting the error of "Network connection failed. Cannot connect to JMX server" when I apply the Websphere (JMX) monitor to it and attempted to test it. While the node shows up and green, the error in red above persists. These changes I've added…