Java Configuration

As of version 1.4 of Anetd, Java virtual machines (JVMs) are no longer bundled with the Anetd distribution. There are two main reasons for this:

1. The Anetd distribution becomes far too large with Java bundled, especially if more than one version of the JVM is needed.
2. Remote Java debugging is supported in version 1.4 and later of Anetd. Java debugging support requires the full Java Development Kit (JDK), not just the JVM, and the JDK license terms do not permit bundling with other software.

Therefore, node administrators must ensure that all ABOCC-recommended versions of the JDK are installed on their nodes and configured into Anetd.

The ABOCC may preconfigure Anetd to look for recommended JDK versions in particular locations. Node administrators then have the option of installing these recommended versions in the specified locations, or specifying the installation locations of their installed JDKs in the local configuration file (for each Anetd instance). The installation location for a particular version of the JDK is configured via a key of the form ``jdk<version>'', where version is the version number of the JDK, for example 1.2.2. Thus, a JDK configuration entry in the configuration file might appear as

jdk1.2.2 /path/to/jdk1.2.2

With the JDK locations so configured, EE developers can specify the use of a particular version via the ``V'' option in the LOAD command (see section 3.8).

Two additional keys, java<version> and javag<version>, specify the invocation strings for Java and Java with debugging support, respectively. The value of each key should be a list of strings, the first specifying the location of the Java binary, and the remaining specifying additional arguments with Java should be invoked, for example,

java1.2.2 "$(jdk1.2.2)/bin/java"
javag1.2.2 "$(jdk1.2.2)/bin/java", "-Xdebug", "-Djava.compiler=NONE",
"-Xbootclasspath:$(jdk1.2.0)/jre/lib/rt.jar:$(jdk1.2.0)/lib/tools.jar",
"-Xrunjdwp:transport=dt_socket,server=y,suspend=n", "-Xnoagent"

Along with each JDK configuration entry, there should be an entry to specify the location of the Java security policy file to be used with corresponding JDK. The location of a Java security policy file is configured via a key of the form jsp<version>, for example

jsp1.2.2 $(abocc_conf_dir)/java-policy-1.2.2

Normally, the ABOCC will supply Java security policy files and specify their locations.