The Content Store contains all icons, background images, folders, scripts, setup files etc.) that are uploaded to the Application Workspace Server.
Application Workspace uses deduplication / single instant storage of content items in the backend. Files that are uploaded to the Content Store will automatically utilize the built-in deduplication feature of Application Workspace. This feature works across the zone for increased storage efficiency.
Content will be replicated across all Application Workspace Servers known to a particular database to enhance content accessibility.
The location of the Content Store is C:\ProgramData\Liquit Workspace\Server\Content
on each server.
Uploading and downloading content
Upload and download of content items do not have to follow the same route from and towards the Agent.
Upload Content
The location of the uploaded content items are residing can be configured in the Storage Settings:
-
Local
The content is saved to a local disk or network share configured in the Server.json file. -
Azure Blob
The content is stored on one or more Azure blob storage containers.
Application Workspace will replicate content between servers and make sure that all Application Workspace Servers can serve all content items.
Download Content
The location of the downloaded content items can be configured dynamically in Content Access. The order of downloading the content items starts with the lowest priority set for the end-point, then continues with all the other configured end-points based on priority and as a final resort the workspace servers are tried. Application Workspace starts content download in the background based on entitlement. You can configure the following end-points as download sources:
Workspace Server (default)
The Application Workspace Server will serve the content to the agents.
Azure Blob Direct Access
The Agent downloads content directly from the Aure Blob storage with a static or dynamic token. This can be combined with a CDN for a GEO-replicated cache.
Satellite
This is a Application Workspace Satellite Server that can be set on a branch location and can be configured to replicate content on-demand or synchronized (full).
SMB
The content from the Application Workspace Servers can be replicated by services like DFSR, rsync, or other copy methods to local SMB share and download content from there. If needed, a Service account can be used.
Custom
You can implement custom endpoints where you can access the content by HTTP or SMB.
For low bandwidth locations, we recommend using a satellite or SMB replicated share on-site where content travels only once over the internet line. For remote work, we recommend Azure Blob with a CDN for speed and latency. Application Workspace can serve both scenarios based on context depending on location and device.
Supported scenarios
- Local directory on a server.
- Server pointing to its own network share.
- Servers pointing to a shared network share.
- Server(s) pointing to an Azure Storage blob container.
These scenarios can be mixed within a single Application Workspace System.
Further reading
Move the Content Store to a new local location for a single server setup
Move the Content Store to a new location for a multi-server setup
Move the Content Store to the Azure Blob service for a single server setup