Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
dusasuman
Creator
Creator

Qlik sense server update

Hi Community,

I am working with Qlik Sense server 3.20 edition (Single/central node). I have asked to update the server to latest version.

what would be the prerequisites and steps i need to follow to update the version, without affecting the current development.

thanks in advance,

Suman

8 Replies
ToniKautto
Employee
Employee

I would suggest reading Qlik Sense upgrades and updates ‒ Qlik Sense‌ on how to upgrade to September 2017 release. Additionally it is always advisable to read release notes.

agigliotti
Partner - Champion
Partner - Champion

I recommend you to make a backup of the Qlik Sense Site first.

I suggest you to use RSM Using the Repository Snapshot Manager ‒ Qlik Sense

Quy_Nguyen
Specialist
Specialist

Hi Suman,

Look like you are moving from synchronized to shared persistence, please take a look at this:

Upgrading and migrating from synchronized to shared persistence ‒ Qlik Sense

ToniKautto
Employee
Employee

How do you know? 3.2 can be either synced or shared.

Quy_Nguyen
Specialist
Specialist

That was my mistake. Thank you Toni. Let Suman detail his case.

dusasuman
Creator
Creator
Author

It is a Shared persistence with single node, i.e Central node. I need to update the version.

So do i need to uninstall the existing qliksense version and install latest version?

ToniKautto
Employee
Employee

No, the installer manages the upgrade for you.

Please read help before proceeding, so that you make required backups and any other prerequisites.

JustinDallas
Specialist III
Specialist III

Make sure you have all of your passwords that are needed for the upgrade.  That includes the password of the domain\QlikUser account, the account password of the Postgres database admin, and the account password of the Postgres Qlik user.

I would say that you should back up live, and if at all possible, clone your production server, put it on a restricted subnet, and try to upgrade that to get your upgrade process tightened down.