Redirect from cmdb_ci_spkg and cmdb_software_instance to cmdb_sam_sw_install

[poyntzj]

I know that installing SAM has changed discovery so that when it detects software it now updates the cmdb_sam_sw_install table

Does anyone know what the actual mechanism is to make this change ?

I have a client who for various reasons need the original tables (cmdb_ci_spkg and cmdb_software_instance) updating for the next little while before changing - this is due to a plugin.

Not seen anything obvious, but need this for now 😞

[emir]

DiscoveryReconciler script include calls GlideappCMDBSoftwareHelper. If SAM is enabled then "cmdb_sam_sw_install" else reconcile on "cmdb_ci_spkg" table.

I have not looked at it in a while, but something like that.

[poyntzj]

Yeah, problem is that the GlideappCMDBSotwareHelper is not visible so I cannot see what happens

[Salom_ Fonseca1]

Regarding cmdb_ci_spkg table, is there more information on impact on it?

Is it possible for this table to continue to be used by ongoing connections to other platforms?

[Rahul Priyadars]

You are correct

No SAM - Tables used are CMDB_CI_SPKG ,CMDB_Software_Product_Model

With SAM- CMDB_SAM_SW_INSTALL,CMDB_SAM_SW_Discovry_Model,CMDB_Software_Product_Model

Old and new Tables will always be there .

(1) New Host discovery after SAM - SW data will go to SAM tables.

(2) You need to run this script after installing Software Asset Management Foundation plugin to copy previously discovered software installation records from the [cmdb_software_instance] table to the [cmdb_sam_sw_install] table, which is used by Software Asset Management Foundation plugin to store software installation records.

Procedure

Navigate to Software Asset > Administration > Migrate Software Installs and click Procced.

The Software Installations list is shown. If the data has already been migrated, a message is shown.

Hope this helps

Regards

RP