Changing or updating the JRE of servers
You can change the JRE of active servers by editing their configuration files.
About this task
The new JRE must be from the same vendor as the current JRE. If you want to change the JRE
vendor, contact support to obtain the KeystoreConverter tool.
Important: Beginning in
version 6.2.2, the HCL Launch server and
agent relays require a Java™ Runtime Environment
(JRE) or Java™ Development Kit (JDK) version
11.
Note: Any certificates that you imported to the old JRE cacerts file must be imported into your new
JRE cacerts file as well. SeeConfiguring SSL on Apache Tomcat and LDAP servers for more information.
Procedure
- Install the new JRE.
- Stop the server.
-
Update the location of the JRE in the following files:
- In the file server_install/bin/set_env, set the value of the JAVA_HOME system variable to the location of the JRE.
- In the file server_install/conf/server/installed.properties, set the value of the install.java.home property to the location of the JRE.
Note: As a shortcut, you can delete the old JRE and move the new JRE into the location of the old JRE. In this case, you do not need to update the JAVA_HOME system variable and install.java.home property because they now point to the new JRE.Note: The value of the JAVA_HOME system variable must match the value of the install.java.home property.Note: If you are upgrading to Java 9 or above and are moving off Oracle Java to AdoptOpenJDK you must manually remove the -Djava.endorsed.dir entry from the server_install/bin/set_env file. -
If the server is running as a service on Windows:™
- Start the server.