Java application recognition and public vs. restricted version classification

This article explains why Java application recognition behavior changed, how Java versions are classified as public or restricted, and how the Recognized Applications Transparency report helps restore visibility into the raw evidence used for recognition. It is intended as background and reference material to support analysis and auditing.

NOTE: From Flexera One IT Asset Management and FlexNet Manager Suite 2022 R1 onward, the built-in Application Transparency report provides visibility into recognized applications and the underlying evidence used for recognition. More details are available in New Application Transparency report especially helps embedded applications.

This article serves as a reference to explain the background and rationale for changes to Java application recognition, including how public and restricted Java versions are classified. The information here complements the Application Transparency report by documenting the recognition logic and evidence interpretation it exposes.

Background

Oracle Java licensing and distribution changes have introduced complexity around distinguishing between public and restricted Java updates and builds. Depending on the update level and build number, Java versions may be considered public or commercial (restricted). Oracle documents these distinctions in Java release notes, for example: Java Development Kit 8 Update Release Notes.

To address this complexity, the Flexera Application Recognition Library (ARL) links recognition evidence based on Java build levels. This required a shift from granular update-level recognition to normalization at the major version level, avoiding excessive fragmentation caused by recognizing dozens of individual builds and versions. An announcement describing this change is available in Content Change Notification - Java Build Version Changes for File Evidences.

While this approach simplifies recognition and aligns with licensing requirements, it reduces visibility into the exact evidence used to recognize applications. The Recognized Applications Transparency report mitigates this by exposing both recognized applications and the raw evidence versions that contributed to recognition.

Why this matters

The Flexera ARL normalizes raw evidence to keep inventory data manageable and aligned with licensing requirements. Applications are commonly normalized at the major version level.

For Java in particular, there is often a need to understand the exact update and build information associated with recognized installations. This level of detail is important for licensing analysis, compliance reviews, and audit preparation. The Recognized Applications Transparency report provides this visibility.

NOTE: This report was released with IT Asset Management 2021 R1 (31.4) and FlexNet Manager Suite 2022 R1.

Report description

The report displays all installations for the product name entered in the search filter, using an exact match on Product Name. It then identifies all raw evidence that contributed to recognition, including:

• File evidence (mandatory, at least one recognition rule, not ignored)
• Installer evidence (not ignored)
• WMI evidence (added in version 5 of the report)

If multiple evidences contributed to recognition of a single installed application, the report displays multiple rows for that installation.

The report also includes contextual information such as:

• Operating system
• Location
• Corporate unit

Version 4 of the report added support for suite recognition. For example, entering “DB2” returns suite components along with the related file and installer evidence used for recognition. Version 4 also significantly improves performance.

Java public and restricted version classification

Java SE 5

• Up to and including update 22: Public
• Update 23 and later: Restricted
• Any update with build number greater than 30: Restricted

Java SE 6

• Up to and including update 45: Public
• Update 51 and later: Restricted
• Any update with build number greater than 30: Restricted

Java SE 7

• Up to and including update 79: Public
• Update 80 and later: Restricted
• Any update with build number greater than 30: Restricted

Java SE 8

• Up to and including update 202: Public
• Update 211 and later: Restricted (licensing change effective April 16, 2019)
• Any update with build number greater than 30: Restricted

Java SE 9 and 10

• All updates: Public
• Any update with build number greater than 30: Restricted

Java SE 11 and later

• All versions: Restricted (licensing modification effective April 16, 2019)

Summary

Application normalization at the major version level simplifies recognition and licensing management but reduces visibility into the underlying evidence used for recognition. The Recognized Applications Transparency report restores this visibility by exposing raw evidence data alongside recognized applications.