Oracle announced the End of Public update for Oracle Java SE 8. Commercial users will not receive further updates after January 2019.
AppsAnywhere will continue to support our Cloudpaging Server product and has determined that replacing OracleJDK with OpenJDK is the best solution. This article will walk you through the steps to switch existing Cloudpaging Server environments to start using OpenJDK.
Obtain OpenJDK community build
A community build of OpenJDK for Windows sponsored by RedHat can be downloaded here: https://github.com/ojdkbuild/ojdkbuild
Scroll down on the page until you find Other downloads - Windows x86.
Click on the msi link (java-1.8.0-openjdk-1.8.0.<XXXXXXX>.ojdkbuild.windows.x86.msi, where XXXXXXX is the version number of the latest release) to download the installer. Make sure to download the installer for Windows x86, and not for Windows x64.
OpenJDK must be manually installed and configured to all servers running Cloudpaging Server. Follow the steps below to install OpenJDK using an installer.
Run the downloaded installer.
Accept the EULA
Install OpenJDK Runtime. OpenJFX Runtime and Web Start are not needed for Cloudpaging Server. If you change the install location, then make sure to note it as you will need it in the later step.
Continue by clicking on Next, then Install. Finally, complete the install by clicking on Finish.
Update Cloudpaging Server
Once OpenJDK has been installed, Cloudpaging Server configuration must be updated to use the installed OpenJDK instead of OracleJDK provided with the Cloudpaging Server installer.
There is a registry script attached to this article to update the configuration automatically if you installed the OpenJDK 220.127.116.11 using the link provided above, and installed to the default location. Otherwise, follow the steps below to update the JVM configurations.
Warning: A restart of Cloudpaging Server is required for these steps. Be careful when applying these changes to a production system.
Important: The following steps require you to modify the Windows registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs.
Open Registry Editor and navigate to the following path:
64-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\JukeboxServer\Parameters\Java
32-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\JukeboxServer\Parameters\Java
Edit the following registry value:
Data: <path to the OpenJDK install location>\jre\bin\server\jvm.dll
(example: C:\Program Files (x86)\ojdkbuild\java-1.8.0-openjdk-18.104.22.168-1\jre\bin\server\jvm.dll)
Then, navigate to the following path:
64-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\JukeboxServer\Parameters\Start
32-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\JukeboxServer\Parameters\Start
Edit the following registry value:
Data: <path to the OpenJDK install location >\jre\bin
(example: C:\Program Files (x86)\ojdkbuild\java-1.8.0-openjdk-22.214.171.124-1\jre\bin)
Restart Cloudpaging Server by using Services MMC
Verify that Cloudpaging Server is using OpenJDK
To verify that Cloudpaging Server is using OpenJDK, take a look at core_service.log file located in <Cloudpaging Server installation directory>\core\logs\core_service.log (The default location is C:\Program Files (x86)\Numecent\Application Jukebox Server\core\logs).
You should see the following lines if you have successfully configured to use OpenJDK.
Configuration: java.runtime.version: <OpenJDK version> (example: 1.8.0_191-1-ojdkbuild-b12)
Configuration: java.home: <path to the OpenJDK install location>\jre (example: C:\Program Files (x86)\ojdkbuild\java-1.8.0-openjdk-126.96.36.199-1\jre)
Software2-InstallOJDK.zip contains the following files:
Extract Software2-InstallOJDK.zip to the desktop
Run InstallOJDK.exe as administrator
Successful installations will return:
Previous versions of Java will need to be removed manually.