With this release of M.App Enterprise, the technology stack will change for the Java platform.
In this article we want to focus on the Hexagon App Launcher.
Starting with the 2018 release, M.App Enterprise is no longer dependent on a specific Java runtime version which must be pre-installed on the machine.
The M.App Enterprise setup includes now its own custom runtime image. Java version fragmentations inside your organization belong to the past. Switches between your production and test environment are easier than ever before.
Yes. The Hexagon App Launcher must be pre-installed on a client machine. Once this is installed, Hexagon App Launcher will be updated automatically.
We will ensure that future versions of Hexagon App Launcher will be still compatible with all released versions after M.App Enterprise 2018. Therefore, there will be no version conflicts in the future if you access different M.App Enterprise versions from the same client machine.
The Hexagon App Launcher comes with the M.App Enterprise setup.
If you don't have installed the App Launcher already you will get a notification on the Apps page after starting an Rich Client App. The notification also includes a link to download the Hexagon App Launcher setup.
In general the Hexagon App Launcher setup can be found at https://{HOST}/AppLauncher/AppLauncher.exe
The Hexagon App Launcher downloads all necessary resources and starts the application.
You can find the App Launcher directory at %LOCALAPPDATA%\Hexagon
The described behavior when App Launcher is not installed yet does not work for Mozilla Firefox. Starting an Desktop App without an installed App Launcher will result in the following screen.
In this case just download the App Launcher from the documented URL and install it.
https://{HOST}/AppLauncher/AppLauncher.exe