search cancel

How to define alternative JRE when instaling CA Release Automation Agent


Article ID: 4628


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


In some environments, such as ones that utilize IBM JRE/JDK for example, the agent does not come bundled with a JRE, and the systems java version may be too old, or not the intended build to avoid running 'Legacy OS' actions.


In some environments, such as ones that utilize IBM JRE/JDK as just one example, eg: AIX.  Others out there include Solaris, HP-UX, more. The agent utilized by these operating systems do not come bundled with a JRE, and rely on solely the systems java version by default, which may be too old, or not the intended build, as we want to inevitably avoid running 'Legacy OS' actions only, which occurs when utilizing a JRE older than version 7.


Operating System: Any supported UNIX/Linux OSDatabase: N/AVersion(s): Any supported version (5.0+), must NOT have a bundled JRE in the installer.


When installing the agent, you must utilize an installer which does not include a JRE bundled with the deployer/agent, for example:

Little known secret, install4j has a parameter, that, when used in conjunction with installers that lack a bundled JRE, will point the agent to an arbitrary JRE of your choice, typically JRE7 or newer.


The solution is as easy as knowing where the JRE is installed that you intend to use, then defining the environment variable:


Depending on the operating system, or more specifically the shell being used, this can vary.  For example, with bash you may simply execute:


export INSTALL4J_JAVA_HOME_OVERRIDE=/path/to/desired/jre -- followed by executing the installer ( ./ )


setenv INSTALL4J_JAVA_HOME_OVERRIDE=/path/to/desire/jre -- then execute the installer ( ./ )


You should then end up with a working agent installation with the preferred java version.

Additional Information

Please contact CA Support for any assistance needed 24/7/365.