We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

How to Normalize the Software Installations coming from SAM tool to CMDB

perumalselvam
Tera Contributor

an hour ago

How to Normalize the Software Installations coming from SAM tool to CMDB. Please share if there is a best practises to model

Software pkg

Software Installations
Software Model 

Business applications.

0 Helpfuls
  • 85 Views
2 REPLIES 2

Vikram Reddy
Tera Guru

51m ago

Hi @perumalselvam,

 

Point your integration at cmdb_sam_sw_install and stop there, and it will just sit unreconciled, normalization is a separate engine, not something that happens automatically on insert. The four terms you listed actually span two different pipelines depending on your licensing, and mixing them up is where most of the confusion starts.

  • Software Installations (cmdb_sam_sw_install) is the raw, 1:1 record straight from whatever reported it, your SAM tool, SCCM, BigFix, brought in via Integration Hub or an import set.
  • Each install gets matched or created against a Software Discovery Model (cmdb_sam_sw_discovery_model), the bridge layer between the raw data and the normalized catalog.
  • Normalization rules then map the discovery model to a Software Model (cmdb_software_product_model) by publisher, product, and version, using rules pulled from ServiceNow's Content Library. This is the SAM Pro path, and it's what "normalization" actually refers to here.
  • Without SAM Pro, software instead rolls up into cmdb_ci_spkg ("Software pkg"), a simpler aggregate populated by classic Discovery's Install Software sensor. It doesn't run through the normalization engine, so don't expect Publisher/Product/Version cleanup there.
  • If a discovery model gets stuck at Partially Normalized (Content Library only has a Product Map rule, not a version-level Package Map rule), you're not stuck fixing it by hand forever. Export the unnormalized discovery model records as XML and raise a Content Request with ServiceNow support, the Content Team will build the missing Package Map rule and push it back through the content library for everyone.
  • For Business Applications, CSDM has no direct relationship from Software Model to Business App. You get there through the infra chain instead: Business App consumes App Service, App Service runs on the same Infra CI the software is installed on.

Worth checking first: are you actually licensed for SAM Pro, or running base Discovery? That's the fork in the road for whether cmdb_sam_sw_install or cmdb_ci_spkg is even the right target.

 

Thank you,
Vikram Karety
Octigo Solutions INC

0 Helpfuls

pr8172510
Kilo Sage

44m ago

Hi @perumalselvam,


use the OOTB SAM Pro normalization process rather than manually normalizing software installation data.

 

  1. Import software installation data from a supported discovery source (Discovery, Service Graph Connectors, SCCM, Intune, ACC, etc.).
  2. Software Installation records are created from the imported discovery data.
  3. Software Normalization uses the Content Library and Normalization Rules to map discovered software to a standardized Software Model.
  4. The Software Model is then used for license reconciliation, compliance, and reporting in SAM Pro.

 

  • Software Installation – Represents software installed on a specific device.
  • Software Model – The normalized representation used for reconciliation and compliance.
  • Business Application – Managed separately in APM/CSDM and is not part of the software normalization process.
  • Use the Content Library for normalization whenever possible.
  • Avoid creating custom Software Models unless necessary.
  • Keep Business Applications separate from software discovery and map them only when there is a defined business relationship.

 

You can refer  

0 Helpfuls