Automating the world one-liner at a time…
Dale Lane of IBM announced that the latest version of the IBM PowerShell Library for WebSphere MQ now supports administering remote queue managers. You can read the details and see a couple of examples HERE. Kudos to Dale and that team! What this allows you to perform operations on multiple remote queue managers.
Some of you might ask, "Why not just wait and let PowerShell V2 do the remoting for you?". I wanted to address that issue in this blog.
First lets start with the conclusion: It is perfectly fine for Cmdlets to do their own remoting!
So let's lay it out.
So with all that, why would a cmdlet ever do their own remoting? There are lots of reasons including:
So if you are a team developing cmdlets, you are free to rely upon us to take care of your remoting needs in the V2 timeframe. Grab the CTP and kick the tires to get that in focus. But, if you already have your own remoting solution, feel free to write cmdlets that leverage that as well.
Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
PingBack from http://msdnrss.thecoderblogs.com/2008/01/17/managing-remote-websphere-mq-via-powershellshould-cmdlets-do-their-own-remoting-2/
Many thanks for your continued support with this. I remember you helping me out when I first <a href="http://hursleyonwmq.wordpress.com/2007/02/12/websphere-mq-scripting-using-powershell/#comment-47">started playing with PowerShell for WebSphere MQ</a> and it has been much appreciated.