Java inventory also on UNIX-like platforms
- Automatic adoption of a new device, or policy-driven self-update of an existing installation (self-update is not supported on Debian Linux or Ubuntu Linux)
- Running a platform-native installer package (such as RPM for Linux)
- Copying an archive into place on the device (although tracking this case requires configuration as described below).
As usual, the imported evidence is automatically available in the All Evidence page (on the Installer Evidence tab); and version 2414 or later of the Application Recognition Library (ARL) supports automatic recognition of supported Java versions from this evidence.
No change is required in commands for inventory gathering by the FlexNet Inventory Agent, nor by its core inventory component the tracker
(ndtrack
) where used separately. 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. (As always,
preferences on UNIX-like platforms are saved in the file
/var/opt/managesoft/etc/config.ini, and may be distributed
as part of the deployment process in a mgsft_rollout_response
file. For more details, see Gathering FlexNet Inventory.)
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.
Troubleshooting tip: Missing Oracle publisher gives unrecognized evidence
To collect installer evidence for Oracle Java, FlexNet Inventory Agent (13.4.1 or later) collects the Oracle publisher information by invoking the Java executable and interrogating the release file (this release file is part of the Oracle Java distribution package, and is installed as a peer of the bin folder in the Java installation). If this release file has been removed, FlexNet Inventory Agent cannot identify the publisher, and as a result, the uploaded and imported inventory produces Unrecognized Evidence records.
You can correct this by restoring the release file from the Oracle Java installation media to the correct location on the inventory device, and waiting for the next overnight cycle of inventory collection/upload/import, and subsequent license reconciliation.
IT Asset Management (Cloud)
Current