The env.java_home setting in snowagent.config is used by Snow Inventory Agents and Oracle Scanners to locate the Java binary required to run database, middleware, hardware, and Java application scanners.

This article explains how to configure env.java_home, how it is used on different operating systems, how to update it, and what errors appear if the setting is missing or invalid.

Configuring env.java_home

Windows

Provide the absolute path to the Java installation directory (not including the bin folder).

Example

• Java binary: C:\Program Files\Eclipse Adoptium\jre-8.0.432.6-hotspot\bin\java.exe
• env.java_home: C:\Program Files\Eclipse Adoptium\jre-8.0.432.6-hotspot

Linux/Unix

Provide the full path to the actual Java binary.

Example

• Java binary: /opt/alt_java/jdk1.8.0/bin/java
• env.java_home: /opt/alt_java/jdk1.8.0/bin/java

How env.java_home is used

SIOS (Windows and Linux/Unix)

• The database scanner (sios) is launched directly by the agent.
• Changes to env.java_home are applied immediately on the next run.

SIOMS, SIOHWS, SIJS (Windows)

• These scanners are launched via PowerShell scripts.
• The agent looks for and runs any file named scan-*.ps1 in the agent directory (like scan-SIOMSLauncher.ps1, scan-SIOHWSLauncher.ps1, scan-SIJSLauncher.ps1).
• Each script checks multiple locations for Java, but env.java_home always takes precedence.
• Because the check is performed every time, changes to env.java_home are applied immediately.

SIOMS, SIOHWS, SIJS (Linux/Unix)
Launcher scripts are .sh files that start the scanners. Post-install scripts regenerate these launcher scripts whenever they run, using the current value of env.java_home from snowagent.config.

• These scanners are started by launcher scripts (SIOMSLauncher.sh, SIOHWSLauncher.sh, SIJSLauncher.sh) scheduled via cron.
• The launcher scripts are created during installation by the post-install scripts, which use the value of env.java_home from snowagent.config.
• Each time the post-install scripts are run, they check env.java_home and recreate the launcher scripts with the current value.
• If you update env.java_home, rerun the post-install scripts to apply the new Java path.

Updating env.java_home on Linux/Unix

For most users, particularly for mass rollouts, update the setting in snowagent.config and rebuild the installer package. For single servers or testing, you can update it directly:

1. Check the current value:

grep env.java_home snowagent.config

2. Check the launcher script value:

grep -A2 Launching SIJSLauncher.sh

3. Edit snowagent.config to set the new Java path.
• Old value: /opt/alt_java/jdk1.8.0/bin/java
• New value: /app/local/jdk-17.0.7+7/bin/java
4. Verify the update:

grep env.java_home snowagent.config

5. Run the post-install scripts to update the launchers:

./snow_post_install_sijs.sh

./snow_post_install_siohws.sh

./snow_post_install_sioms.sh

./snow_post_install_sios.sh

6. Confirm the launcher scripts reflect the new path:

grep -A2 Launching SIJSLauncher.sh

The next time cron runs the launcher, the scanners will use the updated Java binary.

When env.java_home is missing or invalid

• If the setting is not present (or is commented out), the agent will search the system PATH for Java.
• If the path is incorrect, errors will appear in the logs depending on the operating system.

Windows

ERROR; snowagent; win32\OracleInfo.cpp; OracleInfo::Scan;

Failed verification of <PATH TO>\bin\java.exe: Verification error: 80092003

Linux/Unix

ERROR; snowagent; nix/ExternalExecuteables.cpp; determine_if_binary_exists;

<PATH TO>/bin/java does not exist.