ColinHardie asked a question.
I have been asked by our SAM team as to the reason why some machines that they think have Java SE installed aren't showing.
For diagnostics I have been looking in the table tblComputerSoftwareProduct (our server based data is fed from iQuate, and software seems to appear here, not tblComputerSoftware where agent based data goes). For a specific server I can see the following...
2 entries with a rather generic Java - derived software.
Checking the rule definitions the Snow holds for Java SE 7 (OpenJDK) Update 241 (Linux). we can see the following...
vs the raw package information that iQuate sends it...
Note the – in the rule after the 241 (vs no - on the what iQuate sends). Assuming this wildcard pattern is what Snow uses as part of the software recognition, it may explain why I am not seeing any entries for the package/patch in question. Has anyone else encountered this?
THanks
Colin
H Colin,
I'm not familiar with iQuate connector but here are few hints:
1) you right the rule does not match the actual path of your application.
2) but, are you sure that your application is not considered as a pre-recognized application ? You can verify it on Snow inventory Admin console. Look for your device, open it and search for your Java SE installation in "Installed applications" or in "Pre-recognized applications" sections.
But if your application is listed as "Pre-recognized applications", then the software normalization workflow is different. Your software will not be listed as Unassigned Inventoried software and recognition rules will not be apply. A mapping will be done by Snow directly in the database to link your Pre-recognized application to an existing application in SLM (to make it simple). In that case as well you will also have to create a SRS ticket.
Usually, I'm using the following query to cross check that Snow Support has created a mapping for my Pre-recognized application:
-- Check which pre-recognized applications have already been mapped
-- query based on applications known by SLM
-- argument(s): slm.Name - Name of the application in SLM
use SnowLicenseManager;
SELECT distinct
inv.Name as '[INV] Application Name', inv.Version AS '[INV] Application Version', inv.SoftwareHash AS '[INV SoftwareHash]',
slm.Name AS '[SLM Application Name]', slm.OSType AS '[SLM] OSType', slm.ApplicationID AS '[SLM] ApplicationID',
map.SRSUpdateDate
FROM [SnowLicenseManager].[dbo].[tblApplication] slm
LEFT OUTER JOIN [SnowLicenseManager].[dbo].[tblSoftwareProductApplicationMap] map ON map.ApplicationID = slm.ApplicationID
LEFT OUTER JOIN [SnowInventory].[inv].[DataSoftwareProduct] inv ON inv.SoftwareHash = map.SoftwareHash
WHERE slm.Name like 'Java SE 11.0 (OpenJDK)%'
ORDER BY slm.Name, inv.Version
Example when mapping is done
Hope it helps.
Thanks Christophe, great answer and certainly clears up a few things for me....checking the machine I have been looking at it does indeed show the entries as pre-recognised...
Cheers
Colin
Hi,
I have no good news for you. A new software hash is created per Name, Manufacturer, Vendor, OsType or DataSource. This software hash is used for the actual mapping with application in SLM.
So yes, you have to identify each version of your application and per OS and send this information to Snow support. You do not need to do it per server.
Also note that, the Snow update Service synchronizes the SRS database. It download the last definition but it also upload you data to Snow so they can update the SRS database.
More on Snow Update Service here.
Kind Regards
Christophe