Visit Azul.com Support

Using Azul Zulu or Zing Build of OpenJDK

Table of Contents
Need help?
Schedule a consultation with an Azul performance expert.
Contact Us

Azul Intelligence Cloud is integrated in all recent Azul Java Runtime Environments, thanks to the Connected Runtime Service (CRS).

Download Azul JVM With CRS

Check our download pages for the most recent version:

  • Azul Zulu Builds of OpenJDK: open source, TCK-tested and certified builds of OpenJDK for all platforms.

  • Azul Prime Builds of OpenJDK: a modern, TCK-compliant Java platform based on OpenJDK, providing low, consistent response latency of your Java workloads, higher total throughput and carrying capacity, faster warm-up, infrastructure savings, achieved thanks to the C4 pauseless garbage collector, Falcon JIT compiler and other technologies created by Azul.

Connect to Azul Intelligence Cloud via the Forwarder

The default connection mode for JVMs is auto, where they determine if/where they should connect through the environment. JVMs connect when they detect the right conditions.

Configure Runtimes

There are different ways to enable and control your connection to Azul Intelligence Cloud:

  1. Using only Command Line Arguments

  2. Using only Environment Variables

  3. Using only a Properties file

The configuration can be controlled with optional settings, which are fully described in Configuration Options along with examples for each of the setup methods mentioned above.

Once enabled, advanced users can utilize DNS to control connections at scale without touching individual systems or containers.

Connect with Command Line Arguments

This example uses Command Line Arguments. Apply the following arguments to your Java command line, substituting your forwarder_endpoint.

Note
 The Forwarder endpoint must be in URL format, e.g. https://FORWARDER_IP:443. 
 
java -XX:AzCRSMode=on \
    -XX:AzCRSArguments=api.url={forwarder_endpoint} \
    -jar MyApp.jar

Other configuration options are not required.

Identifying Successful Connection

By default, the JRE doesn’t emit log messages. To control the log level and see connectivity messages, add the following to the AZ_CRS_ARGUMENTS: log=info.

Once in place, your JRE produces a message about its JVM Instance ID:

 
[CRS.id][info] CRS authenticated: YOUR_UUID

Configuring JVMs at Scale

If all JVMs share a common network, IT administrators can set up the DNS on the network so that all Java VMs can connect to the Forwarder that exchanges the data with Azul Intelligence Cloud. Rather than configuring each JRE individually, each enabled JRE looks up a DNS entry for the required property. You still can override the connection parameters for individual JVM instances via command line arguments or environment variables.

To set up service discovery via DNS, create the following DNS record:

Name Type Description

az-crs-endpoint

CNAME

The IP address or FQDN of the Forwarder.

When your DNS is configured, start the application with AzCRSMode set to either auto (default) or on:

 
java -XX:AzCRSMode=on MyApp

Disabling Azul Intelligence Cloud

Application owners can disable features by setting the mode to off with -XX:AzCRSMode=off.

Environment Variable

In your AZ_CRS_ARGUMENTS, set enable=false.

This change is only used by new launches and restarts.

Reference Documentation

Consult Configuration Options for complete documentation about arguments and variables.