Bill, we attached data files on QVSP01 and created the shared folders like below:
\\qvsp01\QVPublic --> User Documents folder
\\qvsp01\QVSource --> Source Documents folder
\\qvsp01\QVData --> QVD Files folder
All these shared folder accessed by qvsp02/p03 with Qlikview Service account "qlikviewprod"
All these shared created on the qvsp01 server F:\ drive.
For migrating some suggestions could be :
- Install QV Server on QVSP02 with your new cluster licence, so you have a 1 node cluster
- Add existing QV Server on QVSP01 into the new cluster, so you now have a 2 node cluster
- Will need the new cluster licence
- Carefully check all ok
- Remove QVSP01 from the cluster and close the service down, so you have a 1 node cluster
- Install QV Server on QVSP02 with your new cluster licence, so you have a 2 node cluster
- Uninstall QV Server from QVSP01
- Install QV Web Server on QVSP02 & 03 and do not use for QV Management Service
- Sort them in QMC
- Keep QV Web Server on QVSP01 and do not use for
- But use it only for QV Management Service
- Never moved a QV Directory service
A few remarks on what I think Bill was explaining (I may have misread it)
- The QMS includes its own web server, you don't need a QVWS (or IIS) to navigate to the QMC. So the machine with QMS installed won't need a separate web server.
- However how exactly are you going to do load balancing? The load balancing is usually done by a single QVWS (has builtin features to do that) that forwards each user from the AP to the QVS machine that a) can deliver the required document, and that b) has not much to do at the moment. If you install two web servers, you'll get two URLs to navigate to which isn't particularly user friendly
If you want a fully fail-safe set-up, you can install two QVWS but then you'll need a network load balancer (device) to direct users to the proper QVWS.
Hi Peter, I installed Qlikview server component that includes directory service connector on QVSP02. I add the second server info on the QEMC & made the cluster.
How can I route AP traffic to two servers ? I can't find settings for this.
http://qvsp01/qlikview/index.htm This is working : This QVSP01 access point
http://qvsp02/qlikview/index.htm This is not working
How can create one access point url to manage 2 servers?
You don't have to do that, your Access Point server (a single QVWS) will do this. As I explained before, you will have a single AccessPoint (which is perfectly ok). As soon as a user clicks on a Document thumbnail, the load balancing software inside QVWS will talk to the two QVS services and decide based on specific parameters where to send the user to.
The AccessPoint URL will always be one of the two non-publisher servers. Configure the two QVS in QMC with your cluster license, and configure QVWS so that it knows what load balancing strategy to use.
See chapter 17.3 in the QlikView Server Reference Manual for more information.
You do have a Cluster license, don't you?
We have cluster license up to 5 nodes. I will look into server reference manual. According to your comments, qvsp01/qlikview/index.htm is send the traffic to either of servers depends on the cluster settings.
Our concerns is the access point url misleading to users, its have only one server. So can we markup the access point url like qvspv/qlikview/index.htm ?
Is it possible with QVWS ?
There are two solutions for this issue:
- Either install QVWS on a fourth (scaled down) server that you call 'qvspv'. It doesn't have to be a high-performance server as it will only provide the AccessPoint landing page to users, and will forward them immediately to the appropriate QVS platform when they try to open a QlikView document,
- Or in your company's DNS database, register a domain alias like qvspv.yourcompany.internal or simply qlikview.yourcompany.internal and assign it to the same intranet ip-address of the machine that is running the QVWS. For example, if you do this for machine qvsp01 because that's where you installed QVWS and configured a load balancing strategy, your users will navigate to http://qvspv/qlikview (or even better: http://qlikview/qlikview) and land on the AccessPoint page.
Thanks Peter. I will discuss with my IT team & go with option 2. Even though we can change the server it doesn't impact user bookmarks.
We are doing some OS upgrades, how can we back up the all our tasks & apply task back after upgrade.
Just move the QVPR xml repository move to shared drive and move back to folder after upgrades. I need to take any other precautions to avoid re creating the tasks again.
It would be worth you getting a copy of Steve Redmond's book on QlikView Server as this have plenty of information on setting up QV Servers in a cluster environment. stephen-a.redmond
The book is available from PACKT
I guess your post contains two questions (not entirely clezr). If it does not, just ignore my reply.
"We are doing some OS upgrades, how can we back up the all our tasks & apply task back after upgrade."?
Just make a copy of C:\ProgramData\QlikTech\ManagementService\QVPR and put it back in the exact same place after your OS upgrade. An even easier method may be to make a small change to one of your tasks. QMS will make a backup itself of the entire Task database before the change and put it in the Backups folder. You can use that zip as backup.
" I need to take any other precautions to avoid re creating the tasks again."?
Make sure that after the OS Upgrade your Source documents have the exact same names and locations. Otherwise, the restored tasks will lose track of the actual QVW documents.