Configure a Linux application
Create or select an application in the Admin Console, then set Launcher Type to Linux. The Linux launcher does not use a Java main class or Java classpath. Instead, configure the Linux application command in Launcher Configuration.
Before configuring the application, install the application executable and all of its runtime dependencies in the environment where it will run, whether that is the Session Pool host or an application container. Verify the environment configuration by launching the application manually afterward. See Installation and requirements to ensure launcher requirements are also met.
The Admin Console hides Java- and Swing-specific settings that do not apply to Linux applications, including JsLink, PDF font embedding, and multi-screen support.
Launcher configuration
{
"launcherType": "Linux",
"launcherConfig": {
"appIsolation": false,
"backend": "XWAYLAND",
"command": "/usr/bin/xclock",
"env": ""
}
}
| Setting | Description |
|---|---|
appIsolation |
Runs the application in a Bubblewrap sandbox. Bubblewrap must be available when this is enabled. |
backend |
Use WAYLAND for a Wayland-capable application or XWAYLAND for an X11 application. |
command |
Executable path and optional arguments. Quoting and basic escaping are supported. |
env |
Optional environment variables for the Linux application. Separate entries with whitespace or new lines; use KEY= to unset a variable. |
openUriCommand |
Optional command used when a running application receives an additional desktop file-open request. It can use ${customArgs.file}. |
Use the smallest application-specific environment configuration possible.
For configuration fields shared with every Webswing application, see Application configuration reference.