SCOM Connector QuickStart Guide
Ambrose Wong put together a great quick start guide to connectors in SCOM. I've attached the Word version below. Any feedback is appreciated and I can pass it on to Ambrose.
SCOM Connector Quickstart Guide v1.doc
Comments
Anonymous
January 09, 2008
PingBack from http://msdnrss.thecoderblogs.com/2008/01/09/scom-connector-quickstart-guide/Anonymous
January 15, 2008
It's allready a while since i last developed a connector for MOM 2005 (a connector between altirisAnonymous
January 29, 2008
Hi Jakub, Is there 64 bit version of Ops Mgr 2007 available? I can not find it online?Anonymous
January 30, 2008
All distributables we provide have both 32 and 64 bit versions.Anonymous
January 30, 2008
Also, SP1 is expected to RTM before end of Feb and there will be a link from www.microsoft.com/opsmgr to download the final SP1. All downloads include both 32 and 64 bits. You can also find the RC of SP1 here: https://connect.microsoft.com/SystemCenter/Survey/NominationSurvey.aspx?SurveyID=1228&ProgramID=500Anonymous
January 30, 2008
Thanks Jakub, now i see those amd64 folders inside the package. Also want to check with you that, is there any report models available for Ops Mgr, bcoz i would lik to do custom reports and publish it in a sharepoint website. Inside the Ops Mgr package i found there is a reports model folder and i found there is only acs models are inside, is there any model for OpsMgrDW database and OpsMgr database?Anonymous
January 31, 2008
Reporting is part of the product and is a role that can be installed.Anonymous
January 31, 2008
Jakub, Is there any special MP for "Windows Data Storage server 2003" Or should just use the standard win 2003 MP to monitor that ?Anonymous
February 01, 2008
Not that I know of.Anonymous
February 21, 2008
Read about it Download the guideAnonymous
February 29, 2008
SP1 RTM released. Reference: http://technet.microsoft.com/en-us/opsmgr/cc280350.aspx The connectors availableAnonymous
March 31, 2008
After successfully coding up a .NET console app that reads notices from and HPSIM SQL store, and writes them into a SCOM instance as a “CustomMonitoringEvent”s, I have a few questions: [1] How exactly to register an inbound SCOM connector. MSDN’s "Connecting to External Systems by Using Operations Manager Connectors" is useful, but leaves me wondering how the registration process really works. The information/properties used to create/register a new connector do not seem to include any references to my actual program file. [2] I could use some tips on how to properly assure that my CustomMonitoringEvents are going into the proper MonitoringClass. Right now, I am using an aribitrary MonitoringClass to create events into. This code seems to close to what I need to run: string MonitoringClassQuery = "Name='System.Chassis'"; MonitoringClassCriteria ChassisClassCriteria = new MonitoringClassCriteria(MonitoringClassQuery); ReadOnlyCollection<MonitoringClass> classes = mg.GetMonitoringClasses(ChassisClassCriteria); But it fails to find any MonitoringClass for “Name='System.Chassis'”. I hope that this MonitoringClass simply needs to be created somehow. [3] So I am creating CustomMonitoringEvents, and I can find them using the SCOM UI. But I think I might need to get Alerts created from the Events, in order for IMQ to pick them up. How does one generate Alerts from Events? I hope this would be a one-time setup of to fire Alerts when any CustomMonitoringEvents for Name='System.Chassis' occur. Thank you EricAnonymous
March 31, 2008
[1] You only create the connector. We don't run your code for you, so you still need to run your code either via an application or service. [2] I am not sure I follow on this one. What do you mean by "going into the proper MonitoringClass." The event doesn't take a class. [3] You need to create rules that generate alerts off the events. This is a good start: http://blogs.msdn.com/jakuboleksy/archive/2006/09/27/Sample-Alert-and-State-Change-Insertion.aspxAnonymous
April 06, 2008
The comment has been removedAnonymous
April 07, 2008
Do you ever call Cleanup on your connector? If so, this is likely causing the problem. Cleanup should only be called when you uninstall your connector.Anonymous
April 09, 2008
I found the problem... ...Actually I removed accidentally che built-in connector installed when SCOM in installed... I beg you pardon but I have a lot of problems with SCOM MCF. I do not find answers, therefore where may I put my questions ? In this blog? If yes, where? If no, where may I post ?Anonymous
April 10, 2008
You can post questions here or in the newsgroups, preferably the SDK newsgroup.Anonymous
April 10, 2008
microsoft.public.opsmgr.sdk is the newsgroup I as referring to.Anonymous
May 14, 2008
I had the opportunity to build a simple product connector for System Center Operations Manager 2007 last week. A product connector is used to forward alert information from OpsMgr to an external system. This post describes how I built the product connectorAnonymous
May 15, 2008
I had the opportunity to build a simple product connector for System Center Operations Manager 2007 last week. A product connector is used to forward alert information from OpsMgr to an external system. This post describes how I built the product connectorAnonymous
October 17, 2008
Occasionally I run across an issue that requires immediate action be taken to resolve the problem whileAnonymous
May 27, 2009
Please tell me how to create an alert subscription for an outbound connector through the OMCF service, I was not able to find any method related to that in the SCOM 2007 web service. Thanks in Advance.Anonymous
May 27, 2009
You can't do this via the web service, you can only do it via the public APIs.Anonymous
September 22, 2011
Thank you for your great qucik start guide! It helped me alot when i wrote an SCOM connector for my company. It ow sync maintenance mode between scom and another monitoring system. And transfer alerts. Your guide helped me alot in the beginning. Thank you.