Configure the JDK Version for Release
This guide is for administrators who install or upgrade Digital.ai Release on a JVM (installer-based installations). Use these instructions for a fresh installation or when upgrading an existing Release installation. For operator-based (Kubernetes) installations, see Configure the JDK Version for Release on Kubernetes.
Release 26.3 runs on both JDK 21 and JDK 25. A single distribution supports both JDK versions, and the configuration requirements depend on the JDK version you choose.
Configure Release for JDK 21
JDK 21 is the default for Release 26.3. No JDK-specific changes to the wrapper configuration file are required, for either a fresh installation or an upgrade.
Install JDK 21 and configure the Release server to use it, as described in Java considerations. If you are upgrading an existing installation that already uses JDK 21, you can continue with your existing JDK configuration.
Configure Release for JDK 25
Release 26.3 also supports JDK 25. JDK 25 no longer includes the Java Security Manager, which earlier Release versions use to sandbox script tasks. To run Release on JDK 25, you must:
- Install JDK 25 and configure the Release server to use it.
- Modify the wrapper configuration file for your operating system to remove the Java Security Manager settings.
- Review your script security configuration, because JDK 25 uses sandbox configuration instead of the Java Security Manager to enforce script security.
Before you use JDK 25 in a production environment, test releases that contain script tasks in a non-production environment. For more information about script security, see Configure Script Security.
Configure the JDK 25 wrapper settings
To configure the Release server for JDK 25:
-
Install JDK 25 and configure the Release server to use it, as described in Java considerations.
-
If the Release server is running, stop it.
-
Open the wrapper configuration file for your operating system:
- Linux:
XL_RELEASE_SERVER_HOME/conf/xlr-wrapper-linux.conf - Windows:
XL_RELEASE_SERVER_HOME/conf/xlr-wrapper-win.conf
- Linux:
-
Remove the
wrapper.java.additionalentries that configure the Java Security Manager and its security policy. In the default configuration, these entries are:wrapper.java.additional.6=-Djava.security.manager=java.lang.SecurityManagerwrapper.java.additional.7=-Djava.security.policy=conf/xl-release.policyIf you have customized the wrapper configuration file, the index numbers may differ. Remove the
wrapper.java.additionalentries that set-Djava.security.managerand-Djava.security.policy. -
Start the Release server.
Before running Release on JDK 25 in a production environment, review your script security configuration and test releases that contain script tasks in a non-production environment. This is particularly important when you upgrade an installation that previously relied on Java Security Manager policies to restrict script execution. For more information, see Configure Script Security.