For running SAP GUI for Java as an applet in a browser, please also refer to SAP Note 1831420 regarding security settings.
For the current state and future plans regarding the Applet functionality please refer to SAP Note 2317316.
For information how to setup the connections repository for SAP Logon or how to migrate the configuration used in SAP GUI for Java 7.30, please refer to the SAP UI Landscape Configuration Guide .
Please check following notes, if they are applicable to your backend system.
Issues with screens containing group boxes and termination messages with 'gmux not active' are likely caused by missing corrections that are part of these notes.
In order to have the latest security and bug-fixes, it is highly recommended to use the current Java update.
Java FX is needed since it provides the browser component used inside the HTML control.
Java FX is no longer bundled with the Java VM from Java 11 on. A seperatly installed Open-JFX distribution is therefor needed.
The Installer has to be told where to find this separate component.
These Distributions are tested and officially supported.
We expect that SAP GUI runs with other distributions as well and appreciate any feedback about potential problems.
Make sure the distribution you want to use is supported by your Java vendor!
You can find Oracle's support statements at http://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html#A1097144
For supported locales and writing systems, please refer to http://www.oracle.com/technetwork/java/javase/java8locales-2095355.html
SAP tries to make sure that the SAP GUI for the Java Environment runs on other combinations as well. But please note that the solution of problems caused by the Java Runtime depends on the support of the Java vendor.
In case of missing glyphs of Southeast Asian languages indicated by the missing character symbol (usually rendered as an open rectangle), check the fontconfig.properties used by the JVM refer to the correct fonts installed in the system.
The use of UTF-8 locales is strongly encouraged, especially for japanese, korean or chinese environments.
The japanese input method kinput2 is known to be problematic when using java applets with firefox older than version 2.0. In this case the combination of scim /anthy may be an alternative input method frontend.
Since SAP GUI for Java is not yet supporting Gatekeeper, it might be required to explicitly exempt it from Gatekeeper in order to be allowed to launch the SAP GUI for Java application. Please refer to Apple's knowledge base article referring Gatekeeper for details.
Please make sure to install a complete international version of the JRE, in particular support for Extended Encoding Set (contained in lib/charsets.jar of the JRE). Please refer to http://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html for details. An existing installation of JRE can be modified in the "Programs and Features" Control Panel using the "Change" button. There support for additional languages can be added.
HKCR\Mime\Database\Content Type
HKLM\System\CurrentControlSet\Control\Session
Manager\Environment
HKLM\Software\Microsoft\Windows\CurrentVersion\App
Paths
HKLM\Software\Microsoft\Windows
NT\CurrentVersion\ProfileList
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\<gui
version>
HKLM\Software\Microsoft\Windows\CurrentVersion
HKLM\Software\SAP\General\Appearance\Themes\Default
HKCU\Environment
HKCU\Volatile Environment
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\<gui
version>