These options control cache settings.
{
"cache": {
"enabled": true,
"offline": true,
"path": "Cache",
"tempPath": "Temp",
"packageTempPath": "${TEMP}",
"autoClean": true,
"expireContent": 90
}
}
| Key | Description | Default |
|---|---|---|
| enabled | When an identity is entitled to a package, the package is automatically downloaded and cached on the end-user device. It will remain there even after the session ends, as long as the end-user is entitled to it. When the entitlement is removed, the cache is cleaned depending on how autoClean and expireContent are configured. | |
| offline | If set to true, the offline mode will be available for the local device. If set to false, the packages marked offline will not be automatically downloaded and the Application Workspace Launcher won't switch to offline mode. | true |
| path | The location on the local device where all the content used by the Agent is cached. Note that this path must be relative to the Application Workspace directory. By default, this path is configured to:
| Cache |
| tempPath | The temp directory on the local device, used for uploading folders to the Application Workspace. By default, this path is configured to:
| Temp |
| packageTempPath | When an Application Workspace app is entitled to a user, it is automatically deployed in the local cache directory: %ProgramData%\Liquit\Agent\Cache. The name of the app will actually be a GUID with the .dat extension. Once it gets installed on the local device, the app is copied in the directory configured for the ${PackageTempDir} variable and renamed to its true name. By default, the path of ${PackageTempDir} is configured to:
| ${TEMP} |
| autoClean | If enabled, the stale content from the local cache of devices is automatically deleted if one of the following conditions are met:
| true |
| expireContent | The period in days after which the local cache of devices is deleted automatically if it meets one of the conditions defined above for the autoClean. | 90 |
