Live! from Auckland, New Zealand…
I didn’t want to keep you waiting, just because I was here at Tech•Ed New Zealand. So I found some time to add to the “8-Minute-Demo Video Series”. Something that I at first overlooked, is now available. A simple demonstration of the “Query Database” Object. Please note that this is a SQL oriented demonstration, though other Database queries are possible with this object.
Okay, on to the good stuff; Roll Tape!
If you would like a copy the export of the Opalis Workflow used in the demonstration, please feel free to download, expand and import the contents of the attached “DBExamplesExport.zip”.
Charles, Thats great stuff..Quick qst. How do you integrate the output of the 3rd party DB(SQL Query) to show up as an alert in SCOM, with all the fields in SCOM populated?
I would advise against using OIS as a connector; it is really more of an integration mechanism (that can transfer data). That said, what I mean by a “connector” (in this instance) is a continually running data transfer with VERY high volume. OIS has too much overhead (as it was designed for integration, orchestration and automation, not for strict data transfer like MSSQL SSIS) for data transfers with a high rate and volume.
If you are doing a one-time data load (or a relatively low volume / frequency continual data load) from one system to another, you could use the Query Database object to SELECT the data from the SQL DB (source) and connect it to a SCOM Create Alert object. You would have to map the fields from the Query Database object to the fields in the SCOM Create Alert object, but that should not be too difficult (you could use the “Map Published Data” object or just parse the necessary data out of the Query Database Published Data into their associated fields).