Discovery with Software Asset Management

The table structure for managing software installations behaves differently when the Software Asset Management (SAM) application is activated.

The presence of this application affects the way Discovery stores the software installation data it returns from a scan and require additional configuration within configuration item (CI) records.

The following tables are created when the Software Asset Management plugin is activated:

  • Software Discovery Model [cmdb_sam_sw_discovery_model]
  • Software Model [cmdb_software_product_model]
  • Software Installation [cmdb_sam_sw_install]
    Note: The original schema used by previous versions is not affected when the Software Asset Management plugin is not activated.
    When it runs, Discovery populates the Software Installation [cmdb_sam_sw_install] table. The appropriate configuration item (CI) references the software data. A business rule on this table runs, searching for a matching record on the Software Discovery Model [cmdb_sam_sw_discovery_model] table. If a record exists in the Software Discovery Model table, then the Software Installation table updates the record. If no record exists in the Software Discovery Model table, then one is created. Data from this table is then passed to the Software [cmdb_ci_spkg] table to preserve backward compatibility. The Software Model [cmdb_software_product_model] table is not populated or used by Discovery.
    Important: When SAM is installed, the Software Installation [cmdb_sam_sw_install] table is the appropriate source for all current software data. This means you need to update any related lists or customized reference fields you added to CI records

Starting with the Kingston release, the Discovery populates the VMWare License Key [samp_vmware_license_key] and VMWare License Key Usage [samp_vmware_license_key_usage] tables. See VMWare vCenter Server data collected for more information on where Discovery saves vCenter data.