It's recommended to run XpoLog with an updated JAVA version. During product releases we are updating the internal JAVA version that XpoLog is using and in addition we release patches with only JAVA version update.
The deployment of the update is simple and is done as any other patch that is published for XpoLog.
Checking the JAVA version
Check the current JAVA version your deployment is using:
- Go to XpoLog Manager > System > System Health
- Select the 'System Information' section and look for 'Java Version'
- In case the displayed JAVA version is lower than the one in the subject of this page, its recommended that you'll deploy the update
Note: if you're running XpoLog as a cluster with multiple instances, make sure to check each one (under the same section in the System Health console)
Updating the JAVA version
There are 2 options to update the JAVA version, one is to use an external JAVA that you may already have installed on the XpoLog machine(s), or to deploy the update patch and the internal JAVA that XpoLog uses by default will be updated:
- Using a JAVA that is already installed on the machine(s):
- Ensure you have JAVA installed on each of the machines that XpoLog runs on
- For each XpoLog installation, edit the file XpoLog.lax (Windows) or XpoLog.sh.lax (Linux) and look for the line starting with 'lax.nl.current.vm'
- Modify it to the JAVA path you wish to use (for example lax.nl.current.vm=jre_1_8_231/bin/java)
- Save and restart XpoLog (this should be done on all instances)
- Apply the patch to update the internal JAVA version:
- After verification - remove previous JAVA version from the server.
Once verified at XpoLog Manager > System > System Health ('System Information' section) that each of the instances uses the updated JAVA version, remove the old jre directory from the server:
- Go to INSTALLATION DIRECTORY (of each XpoLog instance you're running)
- Verify that there are 2 jre directories: jre, jre_231.
- Delete the jre one (this is the older JAVA).