Request to parameterize the hard-coded app import folder

vj-p — Thu, 21 Sep 2023 06:56:45 GMT

In our deployment setup, we face an issue due to the app import folder not being configurable.

This is especially needed now as we move to Azure from on-prem. Please find details of our setup in the below section.

It would be great if the path in post /app/import API below could be parameterized
https://help.qlik.com/en-US/sense-developer/February2023/APIs/RepositoryServiceAPI/index.html?page=1420

The attached diagram shows the preferred import operation. Currently we have a workaround using symlinks but it is not supported in Azure clusters.

------------------------

Below content is an alternative solution for app transfers between Qlik Sense backend and frontend sites. The solution works around two environment limitations.

Slow network write speeds when downloading and uploading apps over Qlik QRS Api
Qlik Sense hardcoded app import folder

The app must be in the import folder for the calling user. To find the import folder, send the following request as the appropriate user:

GET /qrs/app/importfolder

Create symbolic link in the frontend import folder pointing to the network path of backend apps folder.

New-Item -Type SymbolicLink -Path \\FrontendFileServer\QlikShare\Apps\USERDIRECTORY\USERNAME -Value \\BackendFileServer\QlikShare\Apps

Enable remote to remote symbolic links

fsutil behavior set SymlinkEvaluation R2R:1

Use QRS API to import file directly from backend apps folder through symbolic link

POST /qrs/app/import

topic Request to parameterize the hard-coded app import folder in Management & Governance

Request to parameterize the hard-coded app import folder