End Point Operations Management agents require a JRE. The platform-specific End Point Operations Management agent installers include a JRE. Platform-independent End Point Operations Management agent installers do not include a JRE.
If you select a non-JRE installation option, you must ensure that your Java package includes Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy files to enable registration of the End Point Operations Management agent. For more information , see Java Prerequisites for the End Point Operations Management Agent.
Depending on your environment and the installation package that you use, you might need to define the location of the JRE for your agents. The following environments require JRE location configuration.
Platform-specific agent installation on a machine that has its own JRE that you want to use.
Platform-independent agent installation.
How the Agent Resolves its JRE
The agent resolves its JRE based on platform type.
On UNIX-like platforms, the agent determines which JRE to use in the following order:
On Linux platforms, you use
export HQ_JAVA_HOME= path_to_current_java_directoryto define a system variable.
On Windows platforms, the agent resolves the JRE to use in the following order:
The path defined in the variable must not contain spaces. Consider using a shortened version of the path, using the tild (~) character. For example,c:\Program Files\Java\jre7 can become c:\Progra~1\Java\jre7. The number after the tild depends on the alphabetical order (where a = 1, b =2, and so on) of files whose name begins with
prograin that directory.
You define a system variable from the My Computer menu. Select .
Because of a known issue with Windows, on Windows Server 2008 R2 and 2012 R2, Windows services might keep old values of system variables, even though they have been updated or removed. As a result, updates or removal of the
HQ_JAVA_HOME system variable might not be propagated to the End Point Operations Management Agent service. In this event, the End Point Operations Management agent might use an obsolete value for
HQ_JAVA_HOME, which causes it to use the wrong JRE version.