Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Greetings QlikCommunity members!
We are currently in the process of putting together documentation on QlikView Server & Publisher upgrade and migration scenarios.
So far, we are focusing on the following topics;
We are now looking for more common scenarios! Can you supply us with feedback on what topics might be interesting in an initial version of this documentation?
Please reply in this thread and we will consider your suggestions!
Addition Nov 3: I added an overview of the topics in a post at the bottom. Check it out to get a preview of what's going to be in the document!
Best regards,
Stefan Bäckstrand
Senior Technical Expert
Problem Management - QlikView Support
Hi Stefan,
We would also like to See how to handle critical tasks or having 3 or more dependent tasks taken care while migrating from qv version 9 to 10/11.
Cheers.
Gaurav M.
Hey Community members!
The document is coming to a final draft soon, and I just thought I would share some topics that will be in it in the first revision:
I hope that this will cover some of the common scenarios and questions that are out there.
Thank you for your input, and keep on adding suggestions on what you want to see in the document! It is going to be revised in further versions as well.
Best regards,
Stefan
HI Stefan,
Great initiative to have in place. One thing that perhaps needs mentioning even if you cant resolve it is related to licensing. Many customers dont have a test server so in order to bring up a new server to test a new release they need to obtain a temporary license some how.
I think different regions may deal with this differently so it may be worth just making a note to get in touch with an account manager for more information
Joe
Joe, good idea, but a bit outside of the scope of the paper. I'll see if we can fit it in somewhere.
Hey Stefan,
There are still a lot of customers out there running 8.5. I would be nice if the process for upgrading from 8.5 to 11 was documented, even if the process is upgrading from 8.5 to 9 and the from 9 to 11.
-Troy
Hi Stefan,
Part of QV Server upgrades can be moving from Windows 2003 to 2008.
My last two installations where on 2008 and I had serious problems to get these servers running.
It would be great to have some kind of checklist for 2008 settings:
What (kind of) user account to use?
In which groups to put this user (member of group Qlikview administrators)?
Use the same Windows account for installation of QV Server as for Services.
User Access Control (UAC) On or Off?
What if ReloadEngine doesn't appear in QMC after installation (use QEMC to trigger ReloadEngine)?
This is really important!
My last two customers started with doubts about Qlikview because of these installation problems, caused by W2008.
Thanks
Fred
try > Unfortunately, 8.50 is not going to be covered in this version of the document, but it is on the list.
fred_s > There are really only one or two things that differ between 2008 and 2003 (except for application data locations on disk) that really have an impact and they are;
Both of these are basic configuration requirements that lie outside of the QlikView configuration itself. We can of course include them, but the first version of the document focus on the configuration & installation of QlikView Server - not Windows security functionality or network safetey.
Service account membership (Administrators, QlikView Administrators), type of accounts and their location is unchanged between them two - across all three latest major versions of Qlikview 9, 10 and 11.
The document is now available and is located here: http://community.qlik.com/docs/DOC-2647
Nice work Stefan Bäckstrand and Brett Bleess!
Hello Arthur,
The following error message appears when I try to open the document:
It appears you're not allowed to view what you requested. You might contact your administrator if you think this is a mistake.
Can you help with this issue?
Thanks,
Thomas
You should be able to see it now. Let me know if you are still having issues.