Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

After the transition from Oracle JDK 8 to SapMachine 11 and OpenJFX 11 [1] last year, there is another big change. Until now, SAP GUI for Java has required a specific preinstalled Java runtime (and OpenJFX in case of Java 11) to be able to run. Starting with SAP GUI for Java 7.50 rev 8, the installer includes SapMachine and OpenJFX resulting in a self contained application embedding those. Only for launching the installer, a Java runtime 8 or newer is needed.

There are various advantages of this approach.

  • It reduces the number of installation steps until SAP GUI for Java can be launched.

  • It is no longer required to specify the module path to OpenJFX during installation in case of Java 11.

  • SAP GUI for Java is running with exactly the same Java version and build it has been tested with.

  • It is no longer needed to manually set the Java runtime to be used for SAP GUI for Java in case other Java applications require a different Java runtime.

  • Frequent stumbling blocks like using an unsupported Java runtime, forgetting to set the module path during installation and other adversities resulting in a non functional installation are avoided.

However, in case of running in a 32-bit environment, SapMachine 11 can not be used since it is 64-bit only. Then still a preinstalled Oracle JDK 8 is required.

SAP GUI for Java 7.50 rev 8 can be downloaded from Service Marketplace [2].

Please note, that the next major version of SAP GUI for Java will only support Java 11 at the minimum and therefore will not work on 32-bit environments.


[2] Download from Service Marketplace
1 Comment