locked
Is it possible to discovery multiple classes in one discovery? RRS feed

  • Question

  • Hi.

    I have an abstract class "LogicalDevice" with some properties like "DeviceType" etc. and about 25 derived classes each representing a specific device type. The devices are currently discovered from SQL server databases by separate Discoveries based on an OLEDB datasource. My composite datasource module uses the workflow
       
        System.SimpleScheduler > System.OleDbProbe > System.Discovery.ClassSnapshotDataMapper

    The query just differs by the "WHERE DeviceType=x" part. This works fine. However, it creates 25 queries where one query without the WHERE statement could be sufficient if I could discover all devices in one single Discovery. Based on the DeviceType I would then try to set the appropriate ClassID of the DataMapper.

    In the Authoring Console it is possible to add several classes/properties and relationships to be discovered, but I wonder if this is fully supported.

    Is there any experience with this kind of problem?

    Best regards,
    Ralph
    Monday, February 22, 2010 3:09 PM

Answers

  • Make sure that your script runs correctly on the desired machine outside of the MP. It'll be much easier and quicker to catch and debug things that way.

    For the majority of scripts the $MPElement$ and $Target/Id$ parameters can be replaced with zero GUIDs, so you don't need to worry about what values are being passed to the script for these parameters.


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Monday, February 22, 2010 7:09 PM

All replies

  • Yes.  This is easy to do with script based discovery - but  not possible from the authoring console directly via the wizards.  You can use the AC to write the script however.
    Microsoft Corporation
    Monday, February 22, 2010 5:12 PM
  • Make sure that your script runs correctly on the desired machine outside of the MP. It'll be much easier and quicker to catch and debug things that way.

    For the majority of scripts the $MPElement$ and $Target/Id$ parameters can be replaced with zero GUIDs, so you don't need to worry about what values are being passed to the script for these parameters.


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Monday, February 22, 2010 7:09 PM
  • Thanks. Meanwhile I found a good sample for script based multi class discovery on authormps.com.

    Is this only possible using scripts?

    Best regards,
    Ralph
    • Proposed as answer by Dan Rogers Friday, February 26, 2010 5:00 PM
    Thursday, February 25, 2010 2:41 PM