Java version and file location

I am trying to create a report to show the running Java process for both *nix and Windows and show the directory the process was started from (which I already have the working for Windows and still finishing it on *nix). I and trying to find a way to use ‘find files’ to search all fixed_drives for any version of java, jre, or jdk and list the version of it. Any help would be appreciated.

Try this?
-jgo
(names of it,
pid of it,
name of user of it|"",
(pathname of image files of it) | (“no path”) ,
(version of image files of it) | (“no version”) )
of processes whose (name of it contains “java” or name of it contains “jre” or name of it contains “jdk” )

It is kicking back ‘Incompatible Types’. What about a relevance that would scan directories for those files and kick back a version?

I think if you just add “as string” to the version of image file of it then it should not errror in relation to casting of types. My bad.

What about searching local drives for any ‘java’ files (not worried about jar files) and checking the versions? The reason I am trying to accomplish this… Oracle is changing the support structure and if you are not at the latest version of Java, you are going to be required to pay for support. We are trying to determine if java is installed via a 3rd party application so I am trying to find the best way to report on this, hence the need to display the directory it is in.

The Inventory add-on for Bigfix can do this.

It’s not advised to use the “find files” inspector to walk the hard drive, as that will both tie up the client (preventing it from processing other content and sending reports), and bog down your machine (processing all that disk i/o).

Better to send an action with something like ‘dir /s /b c:\java.exe’, output that to a file, and read the file as an analysis result.

We have BigFix Inventory, but there is no way to add the path as a column in the reports. I am still researching that side as well also. I will try creating an ActionScript to do output to a file and see what happens.