Mindbreeze GmbH, A-4020 Linz, 2019.
All rights reserved. All hardware and software names used are brand names and/or trademarks of their respective manufacturers.
These documents are strictly confidential. The submission and presentation of these documents does not confer any rights to our software, our services and service outcomes, or any other protected rights. The dissemination, publication, or reproduction hereof is prohibited.
For ease of readability, gender differentiation has been waived. Corresponding terms and definitions apply within the meaning and intent of the equal treatment principle for both sexes.
The JVM launcher service allows Java applications packaged as .jar archives to start as Mindbreeze InSpire “Launched Service.” The started processes are monitored and restarted when they terminate. The Output Stdout and Stderr process is written to the JVMLauncherService log.
The JVMLauncher service plugin is included in the Mindbreeze InSpire installation. If you want to install or update the plugin separately, open the Mindbreeze Management Center and select “Configuration” from the menu on the left. Navigate to the “Plugins” tab, select the appropriate zip file in the “Plugin Management” section and upload it by clicking “Upload.” This automatically installs or updates the connector, as the case may be.
After the plugin has been installed successfully, you can configure a JVMLauncher service. Open the “Indices” tab in the Mindbreeze InSpire configuration and add a service of the type “JVMLauncherService” under “Services.”
The following configuration parameters are available for the JVMLauncherService plugin:
Working Directory Path
Specifies the working directory for the process started.
Executable JAR Path
Path containing the executable JAR file.
Maximum Heap Size
Maximum heap memory size in megabytes for the started process. Selectable values are:
Here you can define any JVM arguments. These will be transferred to the Java process.
Example configuration for an executable JAR file on /data/myapp/myapp.jar: