Service Graph Connector for Sccm - How is the unique key being set

Go to solution
anfield
Tera Guru

‎11-19-2021 08:01 AM

Configuring the Service Graph Connector for SCCM (version 2.5).I am trying to find where the unique key (for each computer) is being set. It looks like the concept of coalesce is gone? We used to have the unique key set as the resource id, so I am trying to find out if this has changed in the new connector, and how it is being set?

Thanks

Labels:
0 Helpfuls
  • 7,149 Views
1 ACCEPTED SOLUTION

Go to solution
Not applicable

‎11-19-2021 08:22 AM

Service Graph connectors all go through the IRE (Identification and Reconciliation Engine) which does not have a concept of coalesce, but rather uses the IRE rules for identication.  You can inspect the rules for each class through the class manager.  The "unique key" in this case is the source native key.  The source native key is populated through the IH-ETL mappings and changes by target class (for SCCM computers it is the resourceId).  You can see the source native key values in the sys_object_source table as the id field.

Here is a flow of how a record is inserted/updated

  • 1st time running the integration
    • A IRE payload is generated through the IH-ETL mappings (let's say a computer payload) and is sent to the IRE
    • The IRE attempts to identify if the computer already exists in the CMDB via the identification rules defined in the class manager for that particular class (serial number lookup, serial number, name, mac addrees + name OOTB for computer)
    • If the IRE finds a record the record is updated with the values passed in the payload & a record in sys_object_source is created with a source native key and a target sys id of the record updated
    • If the IRE doesn't find a record a new record is inserted & a record in sys_object_source is created with a source native key and a target sys id of the record created
  • Subsequent runs of the integration
    • A IRE payload is generated through the IH-ETL mappings and is sent to the IRE
    • If the source native key exists in the sys_object_source table for the given discovery source it will bypass the IRE and immediately update the record in the matching target sys id field.
    • Otherwise
      • If the IRE finds a record the record is updated with the values passed in the payload & a record in sys_object_source is created with a source native key and a target sys id of the record updated
      • If the IRE doesn't find a record a new record is inserted & a record in sys_object_source is created with a source native key and a target sys id of the record created

In this sense the "unique key" is only going to be used to identify a record after the system has already seen the record flow through the IRE.

Hope this helps, and if you are just learning about the IRE I would recommend reading up on it for more details.

View solution in original post

11 REPLIES 11

Go to solution
glennpinto
Kilo Guru

‎04-27-2022 11:18 AM

View our current Service Graph Connector Essentials free training here: https://nowlearning.service-now.com/lxp?id=learning_path_prev&path_id=2df391441bbe89109098c8ca234bcb57. Content will support the answer provided in this post.