Data Warehouse – Anatomy of Management Pack Synchronization

Data Warehouse – Anatomy of Management Pack Synchronization

  • Comments 9
  • Likes

In my last post I gave an overview of some of the components that make up Data Warehouse and Reporting. One of the components of the DW is the Management Pack Synchronization. Because the structure and data within the DW is driven by MP’s within Service Manager we need to be able to regularly synchronize them into the DW. Later on when we get into looking at actual DW MP’s, the direct correlation with SM MP’s will become more clear.

Sequentially, MP Synchronization works in this way (see figure below also):

  1. A MP is imported into a Service Manager implementation that is registered as a source for the DW.
  2. On the DW management server the MP Sync workflow kicks off on a set schedule
  3. It grabs the source Service Manager name(s) from the DWStagingandConfig database via the Data Access Service (see Travis post on Data Access Service here). We will accommodate multiple sources as a part of our Multi-Management group support within DW so that there is a consolidated location for all Service Manager reporting needs.
  4. We connect to the source Service Managers and get the list of their MP’s. DW will specifically key off of the MP version number for changes to classes and relationships.
  5. At this point, the MP list in DW is compared to the MP list in SM for any action that MP Sync should take. These actions can be:
    • If the MP is new to that SM instance but already exists in DW there is only the need for the association between the source SM and MP to be recorded within DW
    • If the MP is new or updated and does not exist within DW, the MP is exported from SM and then imported into the DWStagingandConfig database.
    • If the MP has been deleted from that SM instance then, depending on how many sources have that MP, we will either
      • decrement the source count within DW and remove the association to that source
      • we will remove the reference entirely if the source count will now be equal to zero

Note: only sealed management packs will be sync'd from SCSM to the DW.  Exception to this: List items (aka "enumerations") and groups/queues will be sync'd to the DW regardless of whether they are in a sealed or unsealed MP.  More information on how to seal a management pack can be found here:

MP’s that we bring over from SM will be both SM specific and DW specific. The SM MP’s give us awareness of what the Service Manager CMDB is structured like, the DW MP’s drive the structure and processes of the DW databases. In my next post we will dive into what happens after MP Synchronization…Anatomy of DW/Reporting deployment. In the meantime, please leave any questions you may have!


Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • 237 Microsoft Team blogs searched, 106 blogs have new articles in the past 7 days. 244 new articles found

  •   In my last post I went over the management pack synchronization process that brings over MP’s

  • Hello,

    I have an extended change request class with new properties. This is done in an unsealed MP and is in production since a while, so there are a lot of custom data.

    In order to seal the MP and get the custom properties synced with the DW I need to delete the unsealed version of the MP and then import a sealed version. But if I delete the unsealed MP, the custom data will be lost.

    There is a way to do that but without losing the custom data?

    Thank you!

  • @Fede -

    The only way would be to do something like export out the data to a CSV file and the use the SDK, PowerShell, or CSV import to put it back in there.  MAke sure you export out the Work Item ID as that is the key property for CR.  You will need it to know where to put the property values back to.  Hope that helps.

  • Hi, when I register my DW it creates the MPSync job OK but only imports MP's from the DW datasource and not the main SM management group data source. Under MPSync there's no import jobs at all listed for the main SM management group, because of this there's no management packs imported from the SM and no reports/reporting tab.

    On the DW in Event Viewer I see an error which states that "MPSync failed to connect to the data access service on the DB server" and a second error which states "unable to connect to datasource SM Management Group Name" which I imagine accounts for the problem. However, there is no data access service on the DB server (which is separate from the SM server), only on the SM and DW servers.

    Any ideas?



  • Hi,

    I got this error

    There are no primary or candidate keys in the referenced table 'dbo.CDIncidentDim' that match the referencing column list in the foreign key 'FK_IncidentSLAStatusDurationFact_CDIncidentDimKey_CDIncidentDim'.

    Could not create constraint. See previous errors.

    this fail to import my mp to datawarehouse and now I cannot remove it from there or change it.

    how to get rid of it?