Comments on: Operations Manager Cross-Platform Authoring: Invoke Action Monitor

By: KongYing

KongYing — Thu, 05 May 2011 01:40:38 +0000

hey, I have the same question as you asked. I am wondering whether you finally resolve the problem utilizing complex WSMan StdOut output in Scom ? I am really instrested in this issue. Could you share your ideas with me? Thaks a lot!

By: KongYing

KongYing — Thu, 05 May 2011 01:35:16 +0000

nice article!
I am working on your tutorial as you provided. I also need some examples to figure out utilizing complex WSMan StdOut output in Scom.Could you provide some to me? Thanks a lot!

By: Ryan Taylor

Ryan Taylor — Tue, 08 Mar 2011 23:53:50 +0000

I have attempted to use your guide to create a custom MP for ActiveMQ on a Red Hat Server. The first thing I did was create my script to get the StdOut. I have that script working as such.

winrm invoke ExecuteShellCommand http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_OperatingSystem?__cimnamespace=root/scx @{command=”/opt/progress/fuse-message-broker-5.3.0.3/bin/activemq-admin query -QQueue=SearchIndex.Service1.Request | grep QueueSize”;timeout=”60″} -username:rtaylor -password:Hailey13 -auth:basic -r:https://qtvslax1lmsq001.taservs.net:1270/wsman -skipCACheck -encoding:UTF-8

With a return of

ReturnCode = 0
StdOut = QueueSize = 101

StdErr
ReturnValue = true

PERFECT! I figured authoring this with the Authoring Console was going to be easy. No such luck. I added the reference to the Unix.Library and though the reference ID and token match I cannot move on to the next part of the tutorial. ManagementPack not found in the store is the actual message. Your help would be appreciated!

By: AFed

AFed — Tue, 23 Mar 2010 13:33:02 +0000

I join question about StdOut to PS script parser

By: PaulD

PaulD — Tue, 16 Mar 2010 20:33:29 +0000

yes, please, it would be great. you should see my email as blog owner.

By: Kristopher Bash

Kristopher Bash — Thu, 11 Mar 2010 14:40:02 +0000

If you need examples, I can provide some.

By: PaulD

PaulD — Tue, 09 Mar 2010 20:35:55 +0000

hmmmm, i forgot about posh modules and tried to accomplish this task using vbs/js modules or even thought about writing our own c# probe module to process wsman output.
nice idea, need to test it

By: Kristopher Bash

Kristopher Bash — Fri, 05 Mar 2010 01:16:44 +0000

I will be posting more on this subject soon, as I am currently working on some SCX management packs relying heavily on processing WSMan StdOut data after it is returned, and I intend to blog about the MP’s. I think the best approach in this case would be to follow your WSMan invoker module with a PowerShell Property Bag probe module. Pass the StdOut data item as a parameter to the PowerShell probe, and then parse the StdOut with the PS script and return it as a property bag. This would allow you to deal with multiple instances of one data item in a discovery scenario (just pipe the StdOut data to a PS foreach-object loop), or handle multiple data values simultaneously (each as a distinct property in the property bag).

By: PaulD

PaulD — Thu, 04 Mar 2010 09:30:30 +0000

hey, nice article.

do you have any thoughts how to utilize complex WSMan StdOut output in Scom ? Say, produce 3 perf. counters.