SAM Pro java verification Yokohama

[suvro]

Hi SAM experts,

I am new to SAM Pro: Below is the problem statement please help me with some pointers:

Some years ago, we created the Custom Product: Java XXX paid to distinguish free java versions from to be paid java versions. We set all java installations via the java discovery models to the then "new" product when needed.
In the latest Yokohama release, there is this announcement made: The ServiceNow Yokohama release includes a feature that verifies Oracle Java installations to help organizations stay compliant with Oracle's licensing changes. This feature leverages ServiceNow's Discovery tool to detect Java deployments across an organization's infrastructure, helping to avoid unlicensed usage and potential audit costs. 
The question is, if it is possible to use the product Java Development Kit (plus Free), Java and Java Free Update instead of the "old" Java update paid, using out-of-the-box SAM features, ignoring the normalization we did, and make use of the normalization of SAM instead.

If yes what are the steps we need to do ? Also share relevant product documentation to follow.

Thanks in advance,

Regards,

Suvro

[dreinhardt · Accepted solution]

Hi @suvro,

the feature your are mentioning is the following "Oracle Java process discovery" > Oracle Global License Advisory Services (GLAS) data collection

It's based in Process discovery to determine all required java process details and store them into a dedicated table "ora_java_audit", which is not related to SAM Pro at the moment, it's a plain GLAS output similar to the Oracle GLAS DB discovery results. 

For SAM Pro Discovery- & Software Model normalization aligned with Oracle Java Paid/Free products, please check the following Solved: Dealing with Oracle Java SE 8 Update > 202 - ServiceNow Community. ServiceNow is now able to distringish between paid/free based on the discovered Versions.

I would recommend to revert all discovery models with reference to your custom products and re-run the normalization jobs to get these models linked with ootb data provided by the content team. Maybe the "Normalization Suggestions" in the SAM Workspace will help.

Best, Dennis