Installing Azul Zing System Tools

Complete Prerequisites

Install ZST

The ZST installation package contains a kernel loadable module and supporting scripts and tools.

To install ZST:

A sample system response is shown below:

 
Preparing... ################################# [100%]
Updating / installing...
1:zing-zst-8b.dkms.2.6.32-5.22.5.0.################################# [100%]
Creating symlink /var/lib/dkms/zing_mm/5.22.5.0-4/source ->
/usr/src/zing_mm-5.22.5.0-4
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j24 KERNELRELEASE=3.10.0-957.27.2.el7.x86_64 KERNELDIR=/lib/modules/3.10.0-957.27.2.el7.x86_64/build DKMS=1 INTERNAL_BUILD_NAME=zst-5.22.5.0 BUILD_SUFFIX= BUILD_NUMBER=4.....
cleaning build area...
DKMS: build completed.
zing_mm.ko.xz:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.10.0-957.27.2.el7.x86_64/extra/
Adding any weak-modules
depmod....
DKMS: install completed.
zing-memory: INFO: Restarting...
zing-memory: INFO: Stopping...
zing-memory: INFO: stop successful
zing-memory: INFO: Starting...
INFO: Zing Memory reserved using reserve-at-launch policy
INFO: az_pmem_set_device_limit to 500034437120 bytes succeeded
INFO: az_pmem_set_overall_device_limit to 243259146240 bytes succeeded
INFO: az_pmem_fund_limit_transfer (to 7, from 0, bytes 500034437120) succeeded
INFO: az_pmem_fund_limit_transfer (to 1, from 7, bytes 135144669184) succeeded
INFO: az_pmem_fund_limit_transfer (to 3, from 7, bytes 135144669184) succeeded
INFO: az_pmem_fund_limit_transfer (to 0, from 7, bytes 229745098752) succeeded
INFO: Set ContingencyMinimumFreeMemory to 209715200
INFO: Successfully set fund MinimumFreeMemory
INFO: Set PausePreventionMinimumFreeMemory to 209715200
INFO: Successfully set fund MinimumFreeMemory
INFO: Set PausePreventionMinimumFreeMemory to 209715200
INFO: Successfully set fund MinimumFreeMemory
INFO: You can now run Java processes up to -Xmx219102m or -Xmx213g.
INFO: Azul pmem initialized successfully.
zing-memory: INFO: start successful
zing-memory: INFO: restart successful

Transferring JDK Customizations

If you have applied customizations to the existing non-ZST Azul Platform Prime installation location, you might need to transfer those to the new installation location.

Those customizations could 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 Platform Prime offers the same directories to store custom jar files and security policies.

Setting an Unlimited ulimit

Ensure the ulimit is unlimited for virtual memory, resident memory, and core file size. At the command line, type:

 
ulimit -v unlimited -m unlimited -c unlimited

Some operating systems default the ulimit to -v unlimited, others do not. The -v unlimited value is required prior to launching a Zing instance for the first time. The -m and -c options issue warnings and do not prevent a Zing instance from launching.

Set the ulimit prior to launching any Zing instances or add it to a system start command file.

Ensuring Sufficient Virtual Memory Areas

If you are running Oracle HotSpot or OpenJDK and using XX:+UseLargePages, you must ensure there is sufficient memory allocated to each: Azul Platform Prime and Linux memory.

To ensure that OS settings are appropriate for performance sensitive applications, apply the following settings:

JDK Configuration Compatibility

If your Java application requires access to any javax.crypto unlimited strength policy files:

Since Zing 17.11.0.0 the Java Cryptography Extension (JCE) jurisdiction policy files are included. In order to use encryption with key lengths more than 128 bit, no installation of JCE files is required and adding the following line in your code is sufficient:

 
Security.setProperty("crypto.policy", "unlimited");

With Zing 17.11.0.0 no additional encryption algorithm code was added compared to earlier releases, it only enabled existing code by default.

The previous approach of copying the policy files is still available and all policy files for limited and unlimited key lengths are now included. To activate the unlimited key length:

 
cp /opt/zing/zing-jdk8/jre/lib/security/policy/unlimited/* /opt/zing/zing-jdk8/jre/lib/security/