Loading

Java

Skip Feed
  1. Managing Java reporting excess data from ARL update

     

    Prior to November 2025, reporting for commercial installations of Java, using the Application Transparency Report (as recommended by Flexera), had been working well.

    This is described in this best practices video: https://youtu.be/jMD_AijaBXw?si=pwQ3sMOJ3xt0Esoh&t=1872.

     

    The ARL/SKU/PURL update of November 16, 2025 added a precedence rule that effectively inserts installer evidence into the Java platform application that previously were only using file evidence. Announcement here: https://community.flexera.com/s/feed/0D5PL00000glvjd0AA

     

    Since this change, the number of rows returned when reporting on Java using the Application Transparency Report has basically doubled. Typically, for every installation of Java detected using file evidence, there is now a second line that is derived from the installer evidence via the suite recognition.

     

    To eliminate this extra data from the Java reports you can run the report as you previously did, however once the report is displayed, add a filter to the Suite member application column and set the filter to Is blank. The report will now perform as it did, prior to the November 2025 change.

     

    Note that Java recognition is based on file evidence, as this is the only reliable way to retrieve the accurate application build information needed to correctly identify the version of installed Java; and therefore to determine if the installation is commercial (requiring a license).

     

    Expand Post

    May 2023: Keep Java under Control with Flexera ITAM!

    SAM is a discipline with great benefits but also great challenges. If you’re a SAM manager, in charge of SAM implementation in your organization and using Flexera tools, or if you’re a Flexera partner, watch this knowledge-sharing session.

    • 00:00 Kick Off & Agenda
    • 01:29 Pointers for the last session ("SAM Operations Hub") material and answers to questions
    • 02:23 News
    • 05:00 Managing Java / Agenda
    • 06:09 Context: The challenges of Java.
    • 10:33 How Flexera Helps you (Overview)
    • 14:48 Flexera is Java verified
    • 17:22 Flexera specific Normalization for Java and recent changes of ARL 2740
    • 24:52 Useful advices: use a recent version of the agent with file evidence, don't update Java when asked!
    • 30:59 Managing Embedded Java Instances (Exemption by file path) - Demo
    • 39:34 Java transparency with the New Oracle Java Worksheet
    • 46:24 Step by step process for creating Java licenses
    • 50:00 Demo
    • 54:45 Wrap up

    https://youtu.be/jMD_AijaBXw?si=pwQ3sMOJ3xt0Esoh&t=1872


    • ChrisG (Flexera Software)

      Thanks for sharing the tip @swannd​. Very useful!

  2. Oracle Java Licensing - 'Public' (freeware) vs. Commercial

    Is it still accurate to say that the Public versions of Oracle Java in Flexera are still freeware? e.g. from this KB article: (Unravelling the mysteries of Java (and other products) actual versions for licensing )

     

    I am trying to catch up on Oracle Java guidance and it's giving me a brain aneurysm. Any guidance or support would be greatly appreciated.


    • JohnSorensenDK (Flexera Software)

      @johnksilverwood​ 

      AFAIK the versions relevant for licensing that was called out in this link are still correct. However (and IIRC), Oracle changed the licensing metrics after this article was published, so please make sure to also consult Oracle's official sites for the latest on Java licensing.

       

      Thanks,

      John Sorensen

      Expand Post

  3. simonclarke69 likes this.
    1 of 4
    • Is it possible to ascertain which items are commercial ? We have recently updated ARL,PURL and EOSL and I still dont see any Dashboard Alerts or Items in the Unlicensed Area ? My most accurate piece of guess work is Java v17.x ought to be alerting. Thank you

    • It's been a while since I did this, but if I recall correctly when we wanted to do multiple java paths we had to use a custom solution through Snow Professional Services. As far as I am aware there is no support for multiple paths.

  4. Oracle Java Scanner detailed documentation

    Hi everybody, is there a detailed documentation about the Oracle Java Scanner for Windows?

    I mean like really detailed. I need to know if a Java needs to be installed (hopefully not) in order the java scanner to work and if so how does the scanner check where it is installed.

    Or would it be enough to just copy the binaries to the server.

    The "env.java_home" setting in the snowserver.config did not work at all for the java scanner.

     

    Thanks in advance for any hint.

     

    Best regards,

    Rainer

     

    cc to @Arnis Kalniņš​​ @Reza Rezapour​ @Martin Fruhwirth​ 

    Expand Post

    1 of 6

  5. Snow Inventory Agent 6.8.2 with Java Scanner 2.0 takes hours to scan and consumes lots of GB RAM

    Hello all,

    we currently have discovered a situation, where the Snow Inventory Java Scanner 2.0 1.01 script runs for >10+ hours and consumes 4 GB of RAM with JRE 8/Win 10: SIJSAre there any know reasons for this effect?

    What would be a workaround?

     

    BW Björn

     

    Expand Post

    1 of 8

  6. Java SE - Some machines not showing installations

    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...

     

    tblComputerSoftwareProduct2 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...

     

    smacc rulevs the raw package information that iQuate sends it...

     

    iquate data 

    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

    Expand Post

    1 of 3
    • 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

      Expand Post

  7. 1 of 3
    • Hi ‌ and ‌, thanks for your quick response! Hope both of you are doing fine. :-) I already feared that this will be the answer. OpenJDK is not an option in our environment as this would need to be build, tested and supported by the colleagues responsible for the infrastructure for which they simply have no time for. But anyway, thanks for your answers. Cheers, Rainer

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
Loading
Java | Flexera