NjokiVal asked a question.
How have you been able to effectively manage the java deployment in your estate. Is it purely reliant on the Oracle Java Installation Overview under Enterprise > Oracle Overview.
Related Product Forums
Need help finding an answer?
© 2026 Flexera. All rights reserved.
Hey Njoki,
I can think of the following questions:
Is the Java scanner installed on every computer?
Has the correct security setting been selected for it?
Furthermore, the data from the Snow Binary scanner can also be used for additional validation.
Thank you @Detlev Eufinger
If you want to see Java in SOMO-OVS you will need to roll-out the Java-Scanner (SIJS).
For machines without Java-Scanner you will only get discovery of Java from the Agent, which will not be displayed in SOMO-OVS but still visible in the application list.
You will need to choose the correct security level of the Java-Scanner for your Java installations.
Some Java-Installations might need lower security levels to get inventoried without issues by the Java-Scanner.
Computers where the Java-scanner had issues should show up in SOMO-OVS under "Computers with incomplete verified data". In addition you can use the "All Java installations report". As well you can check the Java-Scanner discovery against the Agent-Discovery. For more detailed investigation of issues related to the Java-Scanner you will need to use SQL Queries.
@Sascha Pfeifer this is very helpful. I have learnt a lot in this discussion. i have not encountered any issue with Java-Scanner (SIJS) for far. I will share my update within a week on my learnings with this.
Much appreciated!!🙏
Hi Njoki,
for us the question at the moment is, if its possible to effectively manage Java at all.
We are at the point where either we need Professional Services to get this running or it is simply mission impossible.
A single commercial version or feature in an estate triggers the requirement to buy commercial subscriptions.
In conclusion the tollerance is 0 and the required accuracy of the discovery is very high.
I would not say it is as easy as simply rolling out SIJS with default security level and look at OVS.
You might start to find out about the issues that are related to the security level.
If you check Agent vs. SIJS it can get even more confusing.
So you might begin to check asset by asset and you discover one issue after the other.
One of oure issues was, that when we started to reduce our Java-footprint, OVS still showed Java for those assets that no longer had Java-installations.
SIJS requires Java to run, the old SIJS-results were not updated and there was no clean-up in place.
This is solved now, but still a good example for the issues.
For us at some point it felt like beta-testing.
As said, we have reached the point where we are questioning how to move on.
Would be interesting to hear about the SIJS-experience of others.
@Sascha Pfeifer This is an insightful discussion. What we have started with is the known java installation going to the unknown.
We have focused to install the java scanner to the Java SE installation instances discovered by snow as we try to work to what haven't been discovered.