Replace the JRE Installed by NolioAgent Without Upgrading the Agent

book

Article ID: 210595

calendar_today

Updated On:

Products

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

Issue/Introduction

The JRE that came with the NolioAgent is outdated. Can I update it? 

Environment

Release : 6.6+

Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER

Resolution

The Java that is distributed with the agent is the latest version that has been fully tested with the agent. It is expected that newer releases (of the same version: 1.8) of Java will work, but because they have not been fully tested there might be minor incompatibilities. If there is a problem related to a newer JRE, support may not be able to help resolve the issue.

If you need to update the Java JRE that used used by the NolioAgent, follow the instructions below. If you have problems with the updated JRE it is recommended to revert back to the bundled JRE to determine if the problem is related to the updated JRE. 

 

Instructions for Nolio Agent on Windows:

  1. Stop the "Nolio Agent" service
  2. Rename the existing [Nolio home]\jre folder to [Nolio home]\jre.embedded
  3. Extract the updated JRE that you downloaded in %TEMP%.
  4. Move the extracted jre folder (from step #3) to the [Nolio home] folder. This path should be valid after moving the extracted folder to [Nolio home]: [Nolio home]\jre\bin\java.exe
  5. Copy the [Nolio home]\jre\bin\java.exe to the [Nolio home]\jre\bin\NolioAgent.exe
  6. Start the "Nolio Agent" service

 

Instructions for Nolio Agent on Linux: 

  1. Stop the service (cd [Nolio home]; ./deployer_daemon.sh stop)
  2. Move the [Nolio home]\jre folder to [Nolio home]\jre.embedded
  3. Extract the updated JRE that you downloaded in /tmp.
  4. Move the extracted jre folder (from step #3) to the [Nolio home] folder. This path should be valid after moving the extracted folder to [Nolio home]: [Nolio home]/jre/bin/java
  5. Start the service (cd [Nolio home]; ./deployer_daemon.sh start)