Our original plan for the MP Authoring Guide was to publish sections on TechNet as they were completed but not make the entire guide available for download until all sections were complete. We had quite a few requests to make the download available immediately though. Apparently, there are quite a few of you out there who prefer to read in Word as opposed to online and even some who prefer to print and read on paper.
In any event, the guide exists for the community so if the community wants it available for download, then who am I to argue? As of last night, the guide is available to download in Word format as part of the complete set of Operations Manager 2007 documentation.
Each time we add a new section to the guide, it will go immediately into the online version on TechNet, and we will publish an update to the downloadable version. The document includes a publish date and a change history, so it should be clear which version you have at any given time.
As always, please send any feedback our way. Making the download available earlier than we originally planned was a direct result of requests from the community, so please keep those comments coming.
The Operations Manager 2007 R2 technical documentation helps you plan, deploy, operate, and maintain Operations Manager 2007 R2. For information about the specific guides available in the library, see http://technet.microsoft.com/en-us/opsmgr/bb498235.aspx."">http://technet.microsoft.com/en-us/opsmgr/bb498235.aspx."
(quote from http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=19bd0eb5-7ca0-41be-8c0f-2d95fe7ec636)
But 'Released/Updated Date' is not updated here http://technet.microsoft.com/en-us/opsmgr/bb498235.aspx
Thanks for pointing that out. You're correct - that date needs to be changed, and the link for reading it online looksl ike it needs to be changed. I'm on it.
Thanks for making the document downloadable. I am one of those guys that need a hard copy in front of me.
I am glad to see you listing the modules in the document but unfortuatly the list does not seen to be complete. The module Microsoft.SystemCenter.DataWarehouse.BulkInsertBulkDataWriter is not in the list. Another thing I would like to see in explanations on how to use the modules expecially the not so common ones as the one I have listed above.
Is there information anywhere of how to use that module.
The module list in the guide is not intended to be exhaustive. Those are just the most common modules of each type. It's intended to be a quick reference for someone relatively new to custom authoring.
The complete module reference is part of the Management Pack Development Kit on MSDN - http://msdn.microsoft.com/en-us/library/ee533840.aspx. There are still some modules to be documented, but there are quite a few already complete. In addition to documenting more modules, that reference includes more detailed information each module type. The MPDK is targeted at developers, but the reference information should be very readable to someone with a good understanding custom authoring.
I thought we had a mention of the MPDK in the Authoring Guide, but we might do a better job of calling that out in the module listings. We'll have a look at that for the next update.
A few questions about "How to create a monitor and rule that share a script supporting cookdown".
At "To create rule to collect performance data", item "n", I do not see Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData available in the module chooser.
At "To create monitor type using custom data source", item 10, I cannot save the monitor type. I can remove SyncTime from Member Modules, Configuration Schema and Overridable Parameters and the monitor type will save. Error message is "The element 'Configuration' has invalid child element 'SyncTime'."
Finally, when I run either the rule or the monitor with the Simulator, the fourth DS is empty, along with the three thresholds. If a sample XML MP is available, I'd love to use MPDiff to find my mistakes.
Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData is in the Microsoft.SystemCenter.DataWarehouse.Library. It sounds like your management pack is missing a reference to that management pack. I'll have a look at the guide and see about adding that to the procedure.
In that procedure, SyncTime is being passed from the Monitor Type to the MyPerformanceScriptFiltered data source module. It sounds like you either didn't define the SyncTime parameter on the module or the parameters are out of order.
The module configuration requires that the parameters be ordered the same as the parameters on the module. The procedure for creating the module puts SyncTime in between IntervalSeconds and Version which is the same order that they have to be defined in the configuration in the monitor type. If you have a different order on the module, then you should match that order.
Putting this one in a separate message so it stands out. You're problem with the data sources mot returning data is due to two bugs in the procedure, and I'll throw out a big thanks for identifying those.
First, the script is wrong because it is only returning a single property bag. Instead of oAPI.Return(oBag), we need oAPI.ReturnItems. We also need oAPI.AddItem(oBag) in the For..Next loop. The correct script is as follows:
sComputerName = WScript.Arguments(0)
sVersion = WScript.Arguments(1)
Set oAPI = CreateObject("MOM.ScriptAPI")
oAPI.LogScriptEvent "MyCookdownScript.vbs",10,4, "Running script on " & sComputerName & ". Version is " & sVersion
For i = 1 to 3
Set oBag = oAPI.CreatePropertyBag()
Call oBag.AddValue("ComponentName","Component" & i)
The second bug is in the MyMP.DataSourceModule.MyPerformanceScriptFiltered module. The Parameter Name in the Expression should be InstanceName, not Context/InstanceName.
I'm going to get those fixes in place right now so they get fixedo n the next publication update. Again, thanks for identifying those and my apologies for the errors.
As for providing sample MP files, we're looking at the best way for doing that once the guide is complete. We're interested in providing some other downloadable samples as well, although we're still working on the best process for that.