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 use Application Workspace's built-in deduplication feature. 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.
Content doesn't have to follow the same route to and from the Agent when being uploaded and downloaded.
Upload Content
Configure the location of uploaded content in your 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 Azure Blob storage with a static or dynamic token. This can be combined with a CDN for a GEO-replicated cache.
Satellite
This is an 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.
- Stop the Application Workspace Server service.
- Move the content of
C:\ProgramData\Liquit Workspace\Server\Contentto the new location. - Ensure the Application Workspace Server service has read and write permissions for the new location.
- Modify the
Server.jsonfile located inC:\Program Files (x86)\Liquit Workspace\Server - By default, the
Contentobject in theServer.jsonfile contains thepathkey with the valueContent. Replace this value with a full path to the new location. - Start the Application Workspace Server service.
All backslashes need to be escaped when entering a full path. For example, if the content needs to be placed in D:\Contents, the path would be D:\\\\Contents within the JSON file.
- Stop the Application Workspace Server service.
- Configure the new storage location by changing the Storage Settings on the server and/or updating the
Contentobject in theServer.jsonfile for local storage. - Start the Application Workspace Server service.
- Monitor the content replication from the content screen on the reconfigured server.
- After the replication has finished, stop the other Application Workspace Server service(s).
- Reconfigure the other Application Workspace Servers the same way as the first server. This can also be done globally.
- Start the reconfigured Application Workspace Server service(s).
- Stop the Application Workspace Server service.
- Make a backup of the local Content Store. By default, its location is
C:\ProgramData\Liquit Workspace\Server\Content. - Remove all ".tmp" files from the Content Store.
- Remove all ".dat" extensions of the files within the Content Store. For example, from the command line run: "rename *.dat *."
- Upload the content files to the desired Azure Storage blob container. You can use the Microsoft Azure Storage Explorer for this, for example. The container should look like in the following image, where the Access Tier can be different:
- Start the Application Workspace Server service.
- Log in as an administrator and navigate to Manage > System > Storage Settings.
- Configure the Storage Settings to use the Azure Blob service.
