Comments
-
> ... Is that happening for you? It looks like the disk volumes I was testing with are in an Unknown state, for reasons other than my up/down check. I'll find other test cases. Thanks again!
-
Inner/outer is like one subroutine that calls another. I needed to pass the innermost return code back to the outermost calling routine. As mentioned in the Java app thread, the inner code was easier (for me) to get working since paths with spaces can ended up being parsed wrong. The exit routine I found that worked is (no…
-
I tried putting the environment variables and logic into the SolarWinds script window but ran into roadblocks. Since I had to write the PowerShell wrapper around the Java call and test it on a target client machine, I ended up simply calling that wrapper script remotely from SolarWinds, as in: e:\bin\javacode.ps1 It's not…
-
So I have the output correct (ones and zeroes) but the exit codes are not right. Outer shell:[E:\bin\GVSW.ps1 $global]Inner shell:[cd e:\binE:\"Program Files (x86)"\CA\"Workload Automation AE"\JRE_WA\bin\java GVSW $global] I need to pass the inner exit code to the outer shell, and then out to the monitor call. Right…
-
I am starting down a similar path. > Classpath and Path variables are set to point at JRE\bin Here's what worked for me (at least in the PowerShell window): $env:Path = $env:Path + ";[path to java bin]" $env:CLASSPATH = "e:\ [etc etc etc] .jar"
-
We will check that out. Do you happen to know if that 'widget' will populate the database columns in the NodeStatistics table? That is where I noticed no values except from the Linux/SNMP feeds.