Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, we're going to be going to a cluster environment soon. I see that you should have two QV servers for the cluster and have at least one access point on another server. How do you put the access point on a separate server?
I assume you install the web server portion on a separate server? Then go to the QV server. Open QMC and on the access point section, add the new server?
Thanks for the help,
Matt
- Build the new server and put the QV IIS Web Server component on it.
Which web server product are you referring to? The QVWS (a Qlik Web Server for QlikView, included in the installation package) or IIS (the Microsoft product)?
In the latter case, step 1 should include the installation of the QlikView Settings Service on the same machine as IIS. Otherwise you won't be able to talk to IIS from within the QMC.
In a clustered environment, the QMS may not run on the QVS server (neither one of them). But you are right, after installing one or more Web Servers on other platforms, open QMC and change/add web server configuration entries.under the System->Setup->QlikView Web Servers tree entry. If there is already an entry for a local non-existent web server, you can modify it to reflect the new location.
Best,
Peter
Just install the QVWS on another machine, and then configure it in QMC so that the QlikView Management Service can reach it and tell it how many QVS cluster nodes are to be serviced using the selected load balanving strategy and where theyse QVSes can be found.
Peter
Thank you for the info.
So if I was to leave the server where it's at, I would do the following?
Thanks for the help!
- Build the new server and put the QV IIS Web Server component on it.
Which web server product are you referring to? The QVWS (a Qlik Web Server for QlikView, included in the installation package) or IIS (the Microsoft product)?
In the latter case, step 1 should include the installation of the QlikView Settings Service on the same machine as IIS. Otherwise you won't be able to talk to IIS from within the QMC.
In a clustered environment, the QMS may not run on the QVS server (neither one of them). But you are right, after installing one or more Web Servers on other platforms, open QMC and change/add web server configuration entries.under the System->Setup->QlikView Web Servers tree entry. If there is already an entry for a local non-existent web server, you can modify it to reflect the new location.
Best,
Peter
Thank you for the info, Peter.
We will be using IIS.
That brings up another good question, if QMS is not to be on the QV Servers, where is the best place to put it? Put it on both QV Access Points (with IIS)?
In the past, we normally chose "Full installation, Single machine with IIS".
Can you confirm this is where we'd install the components? If incorrect, please let me know which and where they should go.
For two Clustered QV Servers
For one or two 'load balanced' AP servers
Thank you for all your help
Well I would like to answer your additional questions, but I see two issues:
Anyway, you don't need two QMS installations. A single one will do to configure and manage all services.
Put your QMS on the single web server platform. You don't need two web servers either to get QVS load balancing. And the AccessPoint services don't really need load balancing except if you want to build a fully resilient architecture.
Note that in that case you will need a network load balancer (hardware device) or another solution as the IIS installations will not necessarily load balnce by themselves.
The AccessPoint has nothing to do most of the time. It's just waiting for users to pass by and click on a document thumbnail. If they store links in their Favorites, nobody will ever visit the AP again...
Thank you for the info. It is indeed for resiliency. If we install Microsoft updates, I'd still like a way for Qlikview to be accessible. But it may not be worth having the extra complexity for the 5-10 minutes it'll be down.
For high load servers (thousands of users), it may be worth the energy and investment. But if Windows updates only take 5-10 minites to install (you appear to do this on a more frequent basis than I do ) or you have a maintenance window in a weekend once in a while, then you are probably right.
Good luck !
Peter