You can manually specify the application that you want to include in a single-session application pool. If an application that you want to specify manually is not already installed, Horizon Console displays a warning message. Each application in a single-session pool can support one user session at a time.
- Install the application on all the Linux machines that you want to include in the desktop pool.
- Create a desktop pool based on the Linux machines. Configure the desktop pool with session type Application or Application and Desktop. See Create a Manual Desktop Pool for Linux, Create an Automated Full-Clone Desktop Pool for Linux, or Create an Instant-Clone Floating Desktop Pool for Linux.
Note: Only virtual machines running RHEL Workstation 7.8 or later, RHEL Workstation 8.1 or later, or Ubuntu 18.04/20.04 can support application pools. For more information, see Considerations for Linux Farms, Published Desktops, and Published Applications.
- In Horizon Console, select .
.The pool configuration dialog box appears.
- Configure the required settings.
Setting Description Application Pool Type
Select Desktop Pool and then select a Linux-based desktop pool from the drop-down menu.Note: To support application pools, the desktop pool must be configured with session type Application or Application and Desktop.
ID Unique name that identifies the pool in Horizon Console. This field is required. Display Name Pool name that users see when they log in to Horizon Client. If you do not specify a display name, it will be the same as ID. Access Group This is a read-only field. You must specify the access group when you create the farm on which the application pool is based. Version Version of the application. Publisher Publisher of the application. Path Full pathname of the application. For example, /usr/bin/gnome-terminal. This field is required. Start Folder Full pathname of the starting directory for the application. Parameters Parameters to pass to the application when it starts. For example, you can specify -username user1 -loglevel 3. Description Description of this application pool. Pre-Launch
Select this option to configure an application so that an application session is launched before a user opens the application in Horizon Client. When an application is pre-launched, the application opens more quickly in Horizon Client.
If you enable this option, the configured application session is launched before a user opens the application in Horizon Client, regardless of how the user connects to the server from Horizon Client.Note: If you enable this option on applications running on a desktop with session type Application and Desktop, the desktop session may not be available.
Connection Server Restrictions
You can restrict access to the application pool from certain Connection Servers by clicking Browse and selecting one or more Connection Servers. The default value is No Restrictions.
If you intend to provide access to published applications through VMware Workspace ONE Access and you configure Connection Server restrictions, VMware Workspace ONE Access application might display applications to users when those applications are actually restricted. VMware Workspace ONE Access users will be unable to start these applications.
You can specify the name of the category folder that contains a Start menu shortcut for the application pool entitlement on Windows client devices. To configure this setting, click Browse. The default value is Disabled.
Select whether to restrict access to entitled application pools from certain client computers.
You must add the names of the computers that are allowed to access the application pool in an Active Directory security group. You can select this security group when you add users or groups to the application pool entitlement.
This setting is deactivated by default.
Entitle Users After Adding Pool Select this option to open the Add Entitlements dialog box automatically after the pool is created. Multi-Session Mode
Select Disabled.Note: Linux application pools do not support multi-session mode, which is not to be confused with the concept of a multi-session pool. If you specify a setting to enable multi-session mode, that setting has no effect.
Linux applications can only be configured in single-session mode. For example, if a user opens an application on client A and then opens the same application or another application based on the same farm on client B, then the session on client A is disconnected and reconnected on client B.
- Click Submit to create the application pool.
What to do next
Entitle users to access the pool. In Horizon Console, select the application pool, select , and add users or groups.
If you must ensure that Connection Server starts the application only on Linux machines that have sufficient resources to run the application, configure an anti-affinity rule for the application pool. Anti-affinity rules are supported only for applications running on floating desktop pools, and not on dedicated desktop pools. For more information, see the Setting Up Published Desktops and Applications in Horizon document.