Apogee JREs are based on a highly configurable J9VM technology and provide a multitude of options to control their behavior. Here, we present often used options, together with a short summary of their functionality, in order to get you started quickly with using Apogee JREs.
Apogee JREs are usually distributed as a single compressed archive (.tgz/.zip) which must be extracted and copied to the target system prior to running Java applications. A JRE is composed of 2 main directories:
Running of Apogee JREs is accomplished by invoking j9 executable with appropriate options. Selection of the profile (MJRE/CJRE) is done at startup via -jcl: option, which attempts to load and initialize specific shared library that implements native features of such profile. E.g.
Apogee JREs also support most of the options present in other JREs. These include:
Apogee JREs uses system memory for many purposes, most of which could be reduced and/or limited to maximize memory available for the rest of the system:
Apogee JREs provide support for debugging via JDWP, which means that your Java applications can be debugged using most of the Java IDEs (including Eclipse and NetBeans). JRE must be started in a debug mode, controlled via -Xrunjdwp: argument:
Newer versions also include JVMTI support, extending debugging and profiling functionality.
Apogee JREs support JIT compilation using -Xjit argument. More detailed list of JIT-related options can be found here, but there are a few factors that must be taken into an account when using JIT: