Page tree
Skip to end of metadata
Go to start of metadata


Choose the Right Java VM


The EEM Editor is currently only provided for Windows 32 bit. Even though the EEM-specific code is Java, the eclipse UI contains native platform specific code. JCO is included in the editor as well and is also platform-specific. A Windows 64 bit JVM or other platforms will not work for the EEM Editor.


For most use cases the Java Runtime Environment (JRE) is sufficient for the editor. The only exception is the SOAP (web services) wizard which requires a full JDK.


The EEM Editor 7.1 requires at least Java 5 / 1.5 to run. Due to incompatibilities of JDK versions and Netweaver libraries there are however some constraints:

  • The editor will crash with Java 7 and 8 when trying to run a RFC script due to the underlying JCO libraries. This problem will be solved in future editor versions.
  • Java 8 generates problems when trying to connect from the Editor to Solution Manager via HTTPS due to changes in the Java 8 network layer. (Work-around in progress)


Note that in general it is possible and common to have multiple Java versions installed on the same PC. Thus you can have a dedicated JVM for the EEM editor only while still running the latest JVM with latest security fixes for other applications and as browser plugin.

Due to the compatibility issues with Java 7 and 8 listed above it is recommended to use Java 6 for the EEM editor. Since Java 6 is no longer publicly maintained the recommendation is to use SAP JVM 6 (Windows, 32bit) which is available from the SAP Software download center. SAPJVM6 is also commonly used for diagnostics agents and thus EEM robots. So the additional benefit of using SAPJVM 6 for the EEM Editor is that the same JVM (same vendor, same major version) is then used for editor and robot. Using Oracle JVM for the editor and SAPJVM for the robot in some cases triggered "surprises" since the set of bundled trusted root certificates is different.

Configure the EEM Editor to use the JVM

The EEM Editor is based on the Eclipse Rich Client Platform (RCP) and thus follows the RCP configuration procedure:

  1. Identify the full path of the java.exe / javaw.exe that you want to use for the EEM Editor. javaw is the recommended binary since it does not open a console window. If you use java.exe you will get a console window which typically does not contain useful information for normal use.
  2. Open the file EemEditor.ini in a text editor
  3. Add two lines to specify the JVM via the option vm. Make sure to add a line break between the option and the actual path. Example:

  4. Save the file. On next restart the JVM should be used


Make sure to eliminate any leading spaces in front of these lines. Otherwise these settings will be ignored.


Check the current JVM of the editor

Open menu item Help --> About; Installation Details; Tab Configuration: The entry java.home tells the location of the JVM in use.



  • No labels