Showing results for 
Search instead for 
Did you mean: 

Updated FlexNet Inventory agent for Oracle Java compliance

Flexera vijay_menon
8 9 986

There has been much consternation about the changes that Oracle has introduced around Java recently. In a nutshell, commercial use of Oracle’s Java Standard Edition (SE) will now require a paid subscription.

These are some of the possible issues that you need to consider:

  • Your developers have been using Oracle Java JDK for in-house projects without being aware of the commercial implications
  • Your environments contain certain older versions of Java, and you are not sure whether they are now free or not
  • You want to understand how much Java is being used so you can decide whether to purchase a Java SE subscription or plan to migrate to another Java distribution

We explained the change in more detail with its impacts and the recommended approach to address these issues in this webinar earlier this post photo.pngRecommended approach to Oracle Java compliance

An updated FlexNet inventory agent was released earlier this year for FlexNet Manager Suite Cloud customers. This has now been made available for On-Premises customers too. You can download the agent and the install instructions from the Product and License Center (PLC).

For details about the feature, please go through the topic in the following Features by Release page.

Feature highlights (and steps to Oracle Java compliance):

  • Identify MSI, package and archive-based installations of Java Development Kit (JDK) and Java Runtime Environment (JRE) This helps find all forms of recognizable evidence of Java installed in your environment
  • Detect these installations in Windows and Unix/Linux environments. This helps to determine how much Java exists across your environment regardless of operating system.
  • Distinguish between different publishers of Java based on installation evidence. This helps to segregate Oracle Java from other distributions.
  • Differentiate among major and minor versions of Java. This helps to understand which versions of Oracle Java now have a commercial impact.
  • Assign appropriate server and desktop license models to understand consumption of Oracle Java. This helps you know how much your Java installations will cost you.


As part of the Application Recognition Library (ARL) #2439 released on July 12, the following commercial minor versions of Oracle Java are classified appropriately: 8.0.201, 8.0.202, 8.0.211 and 8.0.212.

Flexera malderton

Hi, what is the version number of the Inventory Agent currently available to on -premise owners ?

Community Manager ChrisG Community Manager
Community Manager

@malderton - at this point in time the latest agent version number is (also known as release "2019 R1.2").

Active participant


I am wondering if there is also a requirement/change for the FNMS backend? The reason why I ask is because it mentioned cloud and I would like to use this on prem.

Also is nothing changed for windows also because the text say windows/linux but the link shows Linux only

This capability brings Java inventory gathering on UNIX-like platforms in line with existing functionality on Windows platforms. As well, ARL recognition of file evidence for Java on Windows has been improved, so that both installer evidence and file evidence can be recognized on Windows.





Community Manager ChrisG Community Manager
Community Manager

@ronaldschreur - there is no application server change here, but this capability does depend on having current application recognition library content installed.

You are right that there is no change in the Windows agent related to Java: the Windows agent already has the capability to gather relevant data. The agent change is on UNIX-like operating systems, to bring the agent capabilities on those systems in line with capabilities on Windows.

Active participant

Thanks Chris. Does this mean with the latest ARL FNMS agent is capable of detecting all commercial applications for a 100%? I remember from previous discussing that there where some flaws in the agent java detection. 

This part is also interesting:  However, if you wish to gather Java inventory from devices where the archive was copied into place and the installer was not run, the includedirectory preference must be correctly set to allow scanning of the folder where Java is installed.

Does that mean If I use the latest agent version and the latest ARL and do a full scan on every disk \ that my customers should be able to report trustworthy reports on commercial Java products? Including embedded java for example?

Community Manager ChrisG Community Manager
Community Manager

@ronaldschreur - take a look at the final "Note" in the article above: there are still some more updates being worked on to further improve the comprehensiveness of results.

Your thinking to scan all disks/file systems to get the most complete results makes sense to me. Of course, there is always a tradeoff between scanning more filesystems and the time it takes to import and process larger amounts of data - in large organizations, it may not be feasible to do a complete file scan on all computers due to the massive number of files that exist across an organization.

Active participant

Hi Chris,

Thanks, actually i did already read that part. And yes I fully agree with you on the part to do a full drive scan. these days it often more seems a requirement to scan the full disk for vendors like IBM, Oracle. At the other hand there are disadvantages related in doing so.

Perhaps this is someting you can discuss internally? What can be done to improve scanning on full disks and handle the amount of data?





Flexera beginner
For the purpose of clarity is it only FlexNet inventory agent from version 2019 R1.2 that (13.4.1) collects additional inventory evidence for Java? As a consequence any prior version - 2019 R1.1 or older - will not collect this information
Flexera vijay_menon

Hi @liz_burley the FlexNet inventory agent version 13.4.1 adds Java detection capabilities for Unix/Linux environments. And it is backward compatible with previous versions of FNMS. We’ve had questions for as far back as 2017 R1 and it is still compatible.