Share via

Reports in Management Packs.

  • Article

In my previous post “Authoring reports for SCOM 2007” I said that there are basically tree ways to author new reports for SCOM 2007. Create a linked report, use Report Builder or create a custom report using Visual Studio. The best way to introduce a new report in the system is to include it in a Management Pack (read “SCOM 2007 Report Catalog” post for details).

Any Management Pack (MP) can contain reports. If you have RDL file you can simply paste it content under Reporting/Report/Definition node in the MP.

Here is an example:

<Reporting>

  <Reports>

    <Report ID="Demo.MyReport" Accessibility="Public" Visible="true">

      <Definition>

        [Paste content of the RDL file here...]

      </Definition>

    </Report>

  </Reports>

</Reporting>

 

ID is the name your report is deployed under to the SSRS. ID is also a reference for your report inside the Operations Manager. It has to be unique inside the MP and if you specify Accessibility="Public" other management packs could reference your report if they like to use it as a drill-down or as a sub-report.

Your report is going to be visible inside the catalog if you set Visible to "true". Specify "false" if you author a sub-report or a drill down report that you don’t like to be a part of the list of reports users can run directly.

That’s it! Your report is ready to go. To complete the picture however you probably want to give you report a friendly name. That name is displayed in the console when user clicks on your management pack inside the Reporting navigation tree.

To give your report a friendly name you need to define a display string inside the management pack and target it to your report ID.

<LanguagePacks>

  <LanguagePack ID="ENU" IsDefault="true">

    <DisplayStrings>

      <DisplayString ElementID="Demo.MyReport">

        <Name>My Report</Name>

        <Description>My First SCOM 2007 Report</Description>

      </DisplayString>

    </DisplayStrings>

  </LanguagePack>

</LanguagePacks>

Comments

  • Anonymous
    May 21, 2007
    The comment has been removed

  • Anonymous
    March 09, 2010
    Eugene, I am trying to insert some reports in my MP. I created a report in VS then copied the xml from the rdl file. When I run the report from the console it fails because it cannot find the DataSource. The datasource in the rdl is defined at <DataSource Name="OpsMgrDW">      <DataSourceReference>OpsMgrDW</DataSourceReference>      <rd:DataSourceID>f669bd41-9d46-4318-877a-e9af08ec0733</rd:DataSourceID>      <rd:SecurityType>None</rd:SecurityType>    </DataSource> How do I find out what are the right values for the datasource ? Thank you.

  • Anonymous
    March 16, 2010
    Shared data source pointing to DW main dataset should be defined exactly like this:    <DataSource Name="DataWarehouseMain">
         <rd:DataSourceID>e4235c51-407f-4065-8519-a1e57374bc45</rd:DataSourceID>
         <DataSourceReference>Data Warehouse Main</DataSourceReference>
       </DataSource> Management Pack deployment process uses these names for report uploading and configuration.

  • Anonymous
    April 29, 2010
    The comment has been removed

  • Anonymous
    January 25, 2013
    What if the SQL Query i based on the OPSMgr Database.  Can you elaborate on what the Data Source Name would be in that scenario? <DataSource Name="DataWarehouseMain">     <rd:DataSourceID>e4235c51-407f-4065-8519-a1e57374bc45</rd:DataSourceID>

  • Anonymous
    November 05, 2013
    The comment has been removed

  • Anonymous
    November 05, 2013
    Nevermind, solved my own issue. Thanks.