Global Application Pools allow you to use multiple Workspot Application Server Pools (Cloud App Pools) in different Clouds, zones, regions, or datacenters as if they were a single pool. For each Workspot App served by the Global Application Pool, the end-user sees a single icon on the Workspot Client Dashboard: from their point of view there is no difference between an ordinary Workspot App and a Global App.
Prerequisites
Global Applications are a selective feature: contact Workspot to have it enabled.
Not all Clouds are supported: see the Workspot Compatibility Matrices.
Limitations
Client support begins with Windows Client 6.0.0 (which at the time of this writing is not yet released), with other Clients to follow.
Only the “Breadth” load-balancing method is currently supported. That is, sessions are sent to the first server until it reaches its session limit, then the second server is used, etc.
Load-Balancing and Warmup Policies are not currently supported.
Under some circumstances, the individual servers in a newly added pool will not receive the list of Global Cloud Apps from Control and will not allow users to connect.
Workaround: Add another Cloud App to the Global Pool to force all server VMs to be updated. To prevent this app from being visible to users or require significant configuration, it can be a Web App such as “https://www.google.com” that isn’t assigned to any user groups.
Creating a Global Application Pool
Global Application Pools are created from one or more existing Application Pools (Cloud App Pools. You can start with a single Application Pool and add more later.
Application Pools assigned to Global Applications cannot be used as normal Application Pools.
In control, go to “Resources > Global Pools > Global App Pools.”
If Control doesn’t display the “Global App Pools” tab, it is not enabled on your Workspot deployment. Contact Support.
Click the “Add Global Pool” button at the top right of the page. The “Add Global Pool” page appears. Fill in the fields.
Pool Name: A name for the pool. Control, Watch, and Trends will use this name.
Pool Type: “Cloud Apps.”
Load Balancing Method: “Breadth” is currently (Control 18.3) the only supported method.
Pool Name: The name of the first existing Cloud App Pool you are adding to the Global Pool You must type this: there is no selection menu.
Servers and Max. Sessions: Ignore these for now. They will display information about the pool later.
Gateway Type: The type of RD Gateway used to reach the App Pool. This will typically be the same type you specified when creating the App Pool.
Gateway: The name of the gateway used to reach the App Pool. This will typically be the same gateway you specified when creating the App Pool.
If desired, add more App Pools with the “+” key or by typing “Enter.”
The App Pools will be used in order, with the topmost Pool in the list receiving all traffic until it is full, then the second one, etc.
Rearrange the order of the pools by dragging the entries up or down ad desired.
Click “Add Global Pool” to create the Global Pool.
Adding Applications to the Global Pool
Global Application Pools do not inherit the apps of the underlying pools. They must be declared on the “Add a New Application” page.
Go to “Resources > Applications > Add an Application” and fill out the “General Settings” section of the form as follows:
Application Type: Choose the appropriate app type, which is typically “Windows Application.”
Server Type: “Workspot Global App Pools.”
Workspot Global App Pool: The name of the desired Global App Pool.
Cloud App Type: One of:
Installed Application: A Windows program that Control already knows about and for which it can fill in the Full Path and Parameters fields.
Custom Application: An App where you specify the Name, Full Path, and (optional) Parameters fields.
Cloud App Session Hosted Desktop: A Windows login session.
Application Name: The name Control will use for this App.
Full Path (including .exe file): The path to the executable file on the App Server.
Parameters: Optional Windows ommand-line parameters.
Working Directory: Optional directory to launch the App from.
Route Through Gateway: Use “Always” to always use the specified Gateway, “External Only” if you have a Location Detector configured to determine when Gateways are needed, and “Never” to always connect directly.
Gateway Type: Use “Cloud Gateway Cluster” to select a Workspot Managed RD Gateway, “Private Cloud Gateway” for other RD Gateways, and “Private Cloud VPN” for VPN connections.
Application Icon: Use the default, choose one from Workspot’s icon catalog, or upload your own.
Workspot Certificate SSO: If you use Workspot Certificate SSO, see the Workspot Certificate SSO article.
Login Type: Username and password or domain, username, and password.
Fill in the “Target Platforms” section to include all the Workspot Clients you wish to support.
Fill in the “Bundles” section to assign this Global Application to the desired user groups.
Click “Add Application.”