Adelia Studio requires a JDK version 8 or later to generate Java programs and execute certain utilities (debugger, profiler, middleware daemon).
From Adelia Studio Version 14 onwards, this JDK is no longer supplied as standard with the product so must be installed separately. Adelia Studio has been tested with JDK 8 and OpenJDK 11.
During installation, you must specify the JDK installation root directory.
It is preferable for the JDK to be installed before Adelia as if it is not specified, the Java dependent services will not be installed (license server, Java middleware daemon).
Configuration for execution
The tools in the command line are based on the presence of the ADEL_JAVA_HOME variable to locate the Adelia JDK. This variable is normally created during installation and points to the JDK installation root directory.
The CLASSPATH system variable is no longer changed during installation.
If you wish to manually execute a Java command which depends on Adelia runtime, you must configure the CLASSPATH yourself on the command line by adding in the header:
"%ADELIWS%\javarun" and "%ADELIWS%\javarun*" :
java.exe -cp "%ADELIWS%\javarun;%ADELIWS%\javarun\*;%CLASSPATH%" com.exemple.MYCLASS
You can configure the JDK and create the ADEL_JAVA_HOME variable later. In this case, you will have to manually install the services if necessary.
Installing the license server
Execute the following command to install the license server:
LicenceManager -install [profile password]
Caution:
If you define a service startup profile, this must have write access to the Adelia Studio installation directory (licence.dat license file writing).
Installing the Java Middleware service
Execute the following command to install the Java Middleware service:
DaemonJavaService -install [port [[-auto|-manual] password profile]]
If you just specify "-install", the installation will be carried out with the system account and port 3500. If you want to specify an execution profile, you must specify all the parameters. ↑ Top of page
Configuring the compiler
If you use a JDK higher than 1.8 (e.g. JDK 11) for the compilation but you want your application to be executed with an older JDK, you can specify a parameter in ADELIWS.ini to define the minimum level of compatibility of the generated classes.
The "-release [VERSION]" parameter must be added to the "CFLAGS_JAVA", "CFLAGS_JAVA_DBG", "CFLAGS_CLOUD" and "CFLAGS_CLOUD_DBG" configuration keys.
VERSION indicates the minimum Java version level. For example, "-release 8" indicates that the classes must be compatible with a JDK 8.
Caution:
You must not specify this parameter if you are using a JDK 8:
- The class level generated is the minimum level supported by Adelia,
- The -release parameter is a new addition to JDK 9 and later versions ("-release 8" is the equivalent to "-source 1.8 -release 1.8 -bootclasspath "chemin_rt.jar_jdk_1.8" parameters) and is not accepted by a JDK 8.