Source: All About Interop
Dino Chiesa is writing about PowerShell CMDLets for WebSphere.
“It seems IBM have been busy doing CmdLets for MQ, and somehow this escaped my attention. Starting back in December 2007, Dale Lane at IBM published a series of posts about the topic of PowerShell CmdLets for MQ. There is also now an official SupportPac for this stuff, it goes by the catchy name of mo74. (direct FTP link here). In IBM-speak, a SupportPac is an add-on to the IBM product (in this case WMQ). Very good to see! Keep in mind that there are different categories of SupportPac and just because it says "support" in the name does not mean it is a "supported" part of the IBM product in the sense that you can call up their support engineers and ask for bugfix on it. mo74 is listed as Category 2, which means it is AS-IS software. SupportPacs can transition from "AS-IS" to a supported part of the product; this happens when customers demand it. Last updated April 16th, mo74 is currently at version 1.6.”
Maybe handy for people looking for way to monitor WebSphere MQ with OpsMgr 2007.
Another source for using PowerShell with remote queue managers can be found here.
Source: Cnet News.com
“Plat'Home, a Linux company from Japan that specializes in combining eco-friendly, small, tough hardware with their own version of Linux, is announcing another in their series of MicroServers. Kanshi BlockS Pro, made to monitor servers and various network applications, is now available in North America.”
Picture by Plat'Home Kanshi Blocks Pro
Would it be possible to use Cross Platform Extentions to monitor this Linux monitoring box? An Linux agent for their SSD/Linux distribution should be created first ;-)
SSD/Linux is the Linux distribution developed by Plat'Home, for use with the MicroServer series. The distribution is optimized to fit on a small internal ROM, while offering all necessary functions for networking and peripheral devices.
The name of the distribution is derived from its place of development, Sotokanda in Tokyo, in imitation of BSD. It is published under a BSD-style open license.
Have you ever wanted to create email notifications for Alerts based on Alert Descriptions? This cannot be done using the E-mail Notification Channel and Subscriptions settings.
This can be done however with the use of the Notification Command Channel with uses a vbscript that sends an email based on the information in the Alert Description. All the logic and sending of the emails is done by a script.
This is probably my last blog post for some weeks because I'm going to enjoy a long holiday ;-)
Here are the steps:
Command line parameters: /c d:\scripts\notificationalertdescriptionv0.1.vbs /desc:"$Data/Context/DataItem/AlertDescription$" /alert:"$Data/Context/DataItem/AlertName$" /source:"$Data/Context/DataItem/ManagedEntityDisplayName$" /sev:"$Data/Context/DataItem/Severity$" /prio:"$Data/Context/DataItem/Priority$" /state:"$Data/Context/DataItem/ResolutionStateName$"
Remark: Don’t forget the " " for the OpsMgr parameters. desc is used in the vbscript as an argument
And now the vbscript that makes this all possible:
Marco Shaw, has published an article about how Windows PowerShell can be used with System Center Operations Manager 2007 on the August Technet Magazine.
Go read this great article about PowerShell and OpsMgr 2007.
He even mentions my PowerShell Event Creator script in his article :-)
I know Marco form my first experiences with PowerShell and PowerGadgets.
Marco Shaw is an IT System Analyst for a Canadian telecommunications company. He has been working in the IT industry for more than 10 years, and he recently received a Windows PowerShell MVP award. Marco is also the Assistant Community Director of the new PowerShell Community Web site at powershellcommunity.org. He blogs at marcoshaw.blogspot.com.
Source: SCOMNIVORE at myITforum.com
Vin DiPippo has written a great article about about some important concepts regarding how scripts are processed by OpsMgr.
“Returning to the main topic, anyone that is a script developer has a particular paradigm in mind. The script is written and runs as written. If you've ever seen constructions that use the $...$ selectors inline (e.g. SomeVar = "$MPElement...$"), you might have assumed that there was something special about the script execution environment that somehow resolves those. The reality is that those resolutions are done before the script is ever executed. Therefore, we have a very tricky paradigm on our hands: the execution environment is completely standard, but the script body itself is "refined" by OpsMgr before it is embodied in an actual file and run. “
All together a great article that I’ve put in in my OneNote OpsMgr KB articles Notebook. As you should do too!
I know this is not a topic you normally find on this weblog, but I’m thinking about buying a new EEE PC for some days now. Even had some discussion on Twitter about the EEE PC and the MSI Wind. Still haven’t made up my mind, but today I stumbled on this funny cartoon from XKDC about a New Pet.
Do you think I need a new pet? We already got some gold fishes and I always have to clean the aquarium. Maybe not such a good idea after all.
In the last couple of days new or updated Management Packs for OpsMgr 2007 are released.