Azul Zulu Prime Builds of OpenJDK Installation Instructions
- Installing Stable Builds of Azul Zulu Prime Builds of OpenJDK
- Installing Stream Builds of Azul Zulu Prime
- Start Using Azul Platform Prime
- Post Installation Tasks
Looking for Zing? The Azul Zing Virtual Machine is now Azul Zulu Prime Builds of OpenJDK and part of Azul Platform Prime. Learn more.
For system requirements and maximum heap size, see Azul Platform Prime System Requirements. Our software distributions are signed by an OpenPGP key when appropriate. To verify your download, see Product Signing Keys (OpenPGP) for details.
Installing Stable Builds of Azul Zulu Prime Builds of OpenJDK
Customers can download Stable Builds of Azul Zulu Prime Builds of OpenJDK (Azul Zulu Prime) from the Customer Downloads page. Once you have downloaded the installation package, run an installation command appropriate for your operating system to install Azul Platform Prime in the default mode:
RHEL, CentOS, Oracle Linux, Amazon Linuxsudo yum localinstall --nogpgcheck zing<zulu_prime_version>-jdk<version>.rpm
SLESsudo zypper --no-gpg-checks install zing<zulu_prime_version>-jdk<version>.rpm
Ubuntu, Debiansudo dpkg -i zing<zulu_prime_version>-jdk<version>.deb
Anytar xzf zing<zulu_prime_version>-jdk<version>.tar.gz
Installing Stream Builds of Azul Zulu Prime
You can install Stream Builds of Azul Zulu Prime from the appropriate Linux repository.
Start Using Azul Platform Prime
After the Azul Platform Prime is installed, verify the completed installation.
Run a simple Java command, e.g., type:
$ <zulu_prime_java_installation_directory>/bin/java -version
<zulu_prime_java_installation_directory> is the directory where the Azul Zulu Prime JVM is installed, for example:
$ /opt/zing/zing<zulu_prime_version>-jdk<version>/bin/java -version
A sample system output should look similar to the following:
java version "1.8.0_282" Java Runtime Environment (Zing 21.02.0.0-b3-CA-linux64) (build 1.8.0_282-b3) Zing 64-Bit Tiered VM (Zing 21.02.0.0-b3-CA-linux64) (build 1.8.0_282-zing_21.02.0.0-b4-product-linux-X86_64, mixed mode)
|Azul Zulu Prime System Tools (ZST) are needed for the following situations or requirements:|
Heap size (-Xmx) larger than 2500 GBytes. With ZST, Azul Platform Prime supports up to 20 TB (20,000 GB).
Static memory reservation for Java heaps at system start.
OS versions older than listed in the Azul Zulu Prime JVM Operating System Requirements. See Installing the Azul Zulu Prime System Tools for instructions on how to install the ZST component.
Post Installation Tasks
The following post-installation steps are not directly required when starting to use Azul Zulu Prime JVM, but it is recommended to go through them to avoid later problems in production systems.
Transferring JDK Customizations
If you have applied customizations to the existing non-Azul Zulu Prime JVM installation location, you might need to transfer those to the Azul Zulu Prime JVM.
Those customizations can be, for example, JAR files added to the directory
$JAVA_HOME/jre/lib/ext or changes in the security settings below
$JAVA_HOME/jre/lib/security. Azul Zulu Prime JVM offers the same directories to store custom JARs and security policies.
Ensuring Sufficient Virtual Memory Areas
Depending on the application activity and its Java object sizes, Azul Zulu Prime JVM requires a larger number of virtual memory areas (VMAs) than the Linux default of 65530. Most applications on Azul Zulu Prime JVM won’t need a change here, but to be on the safe side, set the upper limit to four times the system RAM size in MBytes.
vm.max_map_count Linux system parameter defines this limit.
To keep the configuration simple when managing multiple hosts, set it on all hosts to the same value as setting it too large doesn’t cause any harm. A value of 1,000,000 (one million) is recommended for systems with a RAM size of up to 256 GBytes. To set the recommended value, complete the following steps:
Add the following line to the file
To activate the setting without reboot, run:sudo sysctl -p
To check the setting on any system, type:cat /proc/sys/vm/max_map_count