Oracle Java SE and SE-Embedded

The server script in bin/vms/jdk starts framework on the JDK JVM. By default, the script is configured to load serverjvm18.jar dedicated to JVMs compliant to JDK 1.8.x.

The Oracle JDK to be used is 8 or higher.

Bellow a list of specific changes you need to place on your startup command for different versions of the JDK:

• For JDK 1.8.x:

  If you are using JDK 1.8, consider the instructions:

  Map your system path to <jdk1.8_install_dir>/bin to enable execution of the JDK 1.8 commands (directory is arbitrary):

  Windows:

  SET PATH=%PATH%;c:/jdk1.8/bin

  Linux or Mac OS X:

  export PATH=/usr/java/jdk1.8/bin:$PATH

  After configuring the environment as described above, run the server.bat or server.sh script, depending on your OS.

Configuring the JVM could be done through set/export of the VM_HOME environment variable or adding the JDK/JRE to the executable PATH. VM_HOME is used to locate the VM on the device, as it can be seen in server.sh and server_common.sh scripts. If the VM is not found anywhere, the script dumps the following message:

This script was unable to detect the $1 VM executable. Please set the
VM_HOME environment variable or add the '$1' to the executable PATH. Current VM_HOME is $VM_HOME

Supported options

The server script supports options for launching the framework with:

• security
• lazy initialization
• measurements
• error log
• clear storage
• enabled framework extensions
• disabled certificate management
• framework loader (For JDK, the Framework Loader is activated by default.)
• uncaught exception handling
• application class loader

For more information on these options, please refer to the section Starting the Framework.

In addition, the server script supports options for:

• debugging the framework and installed bundles with a JDWP debugger
• profiling the framework and installed bundles with the mBProfiler