Hello all,
the topic Java SE and the since 2019 newly introduced license conditions for Java SE 8 Update > 202 are surely known to most of you here. For all others, the following link is a very good introduction to the topic Oracle's Java licensing changes - what do they mean for you? ITAA (itassetalliance.com).
In short, for all installed versions from Java SE 8 update > 202, you need a Java SE Subscription.
The challenge now is to be able to identify these installations correctly and assign them to corresponding software models. I've installed the following Java package on a test machine (jdk-8u211) and transferred the data to the Platform via our SG-SCCM integration. In the following you can see the excerpt from the discovery models
It is good to see that all entries have been normalized by the content database, but at a second glance it becomes clear that this data is of limited use for our application.If you look at the entries for Software Models, DMAPS, you will find some matching entries e.g. for "Java 8 Update 8.0", but all of them are missing the crucial detail - the version of the update (e.g. > 202). The provides normalized discovery models for the JDK product is too generic and you have to assume that every JDK installation consists these 2-3 entries per device to allow detection based on the "Java 8 Update" entry.
Basically, the question to the ServiceNow colleagues, are there already internal efforts, how the platform would like to map these details necessary for Java SE in the future in the content database? And the other question is, how do I map my requirements in the meantime to get a clear picture of my Java SE consumption?
I could edit all affected installation to "Java 8 Update 8.0" and reset the normalization and change the version to 8.0 211.
The same for the products "Java SE Development Kit 8 Update 211" and there once change the product to e.g.: "Java Development Kit" and change the version accordingly to 8.0 211.
However, the whole thing does not feel good and I would like the content team to provide this important information at this point and update all components involved in it (DMAP, Software Models, ...)
I look forward to your answers and a great exchange of ideas
Best, Dennis
The content updates are available and will add the new "Java Free Update" products.
BBest, Dennis
While working with this problem I noticed other and especially strange things that point to a not really consistent handling of version data by the content team.
I've created a software model (Publisher "Oracle", Product "Java 8 Update"), because I would like to test if it's possible to handle this issue with "Suite Components" and other conditions. The content team provides you two DMAPS for this products (DMAP0132336, DMAP0154835). A closer look at the provided lifecycle data shows the problem I mentioned regarding normalization.
DMAP0132336, is providing version 8.0 only and no information about the patch level e.g
DMAP0154835, is providing the level of information I'm looking for. Version is normalized to e.g. 202 and not 8.0. They know it, but didn't normalize the discovery models 😕
Is there a colleague from the content team here in the community who can comment on this? I would be pleased - otherwise we wait for the ideas from ServiceNow and continue to try out some approaches. Further ideas are welcome.
Best, Dennis
The content updates are available and will add the new "Java Free Update" products.
BBest, Dennis
