Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have just migrate the existing QlikSense server to the new QlikSense Server.
This two server is on different environment, I have copied the all the apps from the existing QlikSense Server and moved to the new Qlik Sense Server into the QlikShare folder.
However on the QMC i dont see the list of apps that supposed to reflect the apps from the QlikShare.
Is there any setting to make the QlikShare folder sync with the QMC ?
The server does not automatically sync with new files in the app folder. In order to "tell" Qlik Sense about the app you'll need to import the app. This can be done manually using qmc apps section or using the qlik Sense api if you are familiar/comfortable using that.
I don't know if you considered this, but doing the correct preparations you should be able to migrate all the apps and configurations of the old server into the new by restoring an backup onto the new machine. Take a look at this: https://help.qlik.com/en-US/sense-admin/May2023/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...
The PostgreSQL migration while a risk actually does work quite well with the updater tool that Qlik has released.
But you would need to downgrade the new server to same version as old server in order to migrate a backup.
Alternative is to export each and every application in the old server to files and then import them on the new server.
But then you will have to set up all configuration in the QMC again (streams, tasks, users, access, connections etc.)
Apps will get new internal IDs in Qlik repository but thats not a big deal anyway if you have not migrated the repository.
You will loose any private and shared sheets in applications and all bookmarks, stories etc. Anything that an end user has added, only things that developers has built will survive the export/import transfer of applications.
You could salvage shared & private sheets by making them official temporarily on the old server before exporting and after import on the new server changing them back to shared & private sheets and reassigning to correct user.
It is some work but is possible.
The server does not automatically sync with new files in the app folder. In order to "tell" Qlik Sense about the app you'll need to import the app. This can be done manually using qmc apps section or using the qlik Sense api if you are familiar/comfortable using that.
I don't know if you considered this, but doing the correct preparations you should be able to migrate all the apps and configurations of the old server into the new by restoring an backup onto the new machine. Take a look at this: https://help.qlik.com/en-US/sense-admin/May2023/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...
Hello @Vegar ,
I have tried the following method by restoring the repository database. However the old server is using postgresql version 9.6 which is already outdated to the new server using PostgreSQL version 12.5.
In order to restore the existing settings, will require both server having the same version which from our production would be in high risk for PostgreSQL migration.
The PostgreSQL migration while a risk actually does work quite well with the updater tool that Qlik has released.
But you would need to downgrade the new server to same version as old server in order to migrate a backup.
Alternative is to export each and every application in the old server to files and then import them on the new server.
But then you will have to set up all configuration in the QMC again (streams, tasks, users, access, connections etc.)
Apps will get new internal IDs in Qlik repository but thats not a big deal anyway if you have not migrated the repository.
You will loose any private and shared sheets in applications and all bookmarks, stories etc. Anything that an end user has added, only things that developers has built will survive the export/import transfer of applications.
You could salvage shared & private sheets by making them official temporarily on the old server before exporting and after import on the new server changing them back to shared & private sheets and reassigning to correct user.
It is some work but is possible.