- InPlace upgrade of only Qlikview Publisher.( Server with only QLikview Publisher Installed)
- Machine Migration of only Qlikview Publisher.( Server with only Qlikview Publisher Installed)
It would be great to have some documentation for
- Qlikview from standalone Server setup ( similarly for Publisher server ) to Disaster Recovery setup. ( with Servers in different Data Centers for Tier-1 DR Plan where the recovery time would be less than 1 hr )
1. What I was looking for today, was documentation on Migrating from QV Native Webserver to MS IIS.
The reason was the need to use SSL Certificates.
2. So related to the first one; how to configure SSL certificates with MS IIS or Native QVWS.
This isn't Upgrade or migration, but maybe you'll find a way to add this to the first scenario.
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:
- Consideration topics on .NET, EDX, services, QDS, clients, changed URLs, settings/programfiles/appdata locations, service refactoring between versions and new services
- Upgrade instructions on QVS 9 to QVS 10/11, QVS 9 to QVS+Pub 10/11, QVS+Pub 9 to QVS+Pub 10/11
- Upgrade instructions on QVS 10 to 11, QVS 10 to QVS+Pub 11, QVS+Pub 10 to QVS+Pub 11
- Re-location of services between machines on QVS 10/11, DSC 10/11, QVWS 10/11, QDS 10/11
- Scenarios on Multi-machine upgrade (in-place upgrade) QVS+Pub 10 to QVS+Pub 11 and Scale-out scenario QVS+Pub 10 (single machine) to QVS+Pub 11 (multiple machines).
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.
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
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;
- UAC on Windows Server 2008. Administrators and technicians installing server software should know if UAC is active, and if so, make sure to run installations with the "Run as Administrator" option (or disable UAC all together). Just as with any other software.
- Firewall in Windows Server 2008 by default blocks everything that does not have service role installed. Server 2003 did not block anything by default.
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.
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.