How do I manage discovered licensed software installed as a component of another software?

[Zach Wehrli]

I can't seem to find anything around this.

Discovery is finding java development kit (among others) on many of my servers and SAM displays them as not compliant under Oracle because they're 'unlicensed'.

The problem is that in my case, all the discovered java installs are a component of another software that uses it to function. 

How do I effectively ignore these but not ignore if it finds it actually installed separately?

[Stephen42]

Hi Zach

It sounds like the Java Development Kit needs to be a 'Child' product under the 'Parent' software model.  Are you leveraging the content library ?  The samp_m2m_suite_entitlement_def  table lists Oracle Java Development Kit  as a child to the Parent Oracle Java SE (via DMAP0202041),  Do you have the correct DMAP on your Software Model ?

If you are using some other 'parent' software model, add Java Development Kit as a child product, (and other component titles ) and ensure your entitlement is on the Parent Software Model.  

Reconciliation should, if this is configured correctly , show compliance at the parent level, and not count the child components as a license towards the entitlement.

Hope this helps

[Zach Wehrli]

I will look into this as an option.
I did forget to mention that these have been discovered with File Based Discovery. They are not listed in the traditional installed software lists on linux or windows. 

Is there a way to essentially filter out the ones discovered this way without having to disable FBD?

[Stephen42]

The other option is to Revert Normalization on the Software Discovery Model, change the 'Product Type' to not licensable and save.    The installs will still be in cmdb_sam_sw_install, but will not be taken into consideration when Reconcilliation runs.