Integrations & Imports into the CMDB

Definitive questions

• +Should CMDB integrations use Import Sets or the IRE payload API?
• +What are ServiceGraph Connectors?
• +What is IntegrationHub ETL?
• +What is a staging table?

Scenario drills

1. SCCM import creates duplicates

   “An SCCM CSV import creates a new CI on every run even though hostnames match.”

   Approach

   • The transform map writes directly to cmdb_ci_computer instead of going through IRE.
   • Fix: switch to IntegrationHub ETL or call cmdbTransformAPI in the transform script so identification runs.
   • Set discovery_source = 'SCCM' so reconciliation rules can arbitrate.

   var api = new SNC.IdentificationEngineScriptableApi();
   api.createOrUpdateCI('SCCM', JSON.stringify(payload));

   Alternate approach

   Alternate: use the certified 'ServiceGraph Connector for SCCM' — it already wires IRE correctly and ships pre-tuned identifiers.

   Pitfall

   Bypassing IRE on any CI write eventually corrupts the CMDB — every source must go through it.