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: 
rafael_qg
Partner - Contributor III
Partner - Contributor III

Cluster QV with two nodes?

[EN]

Hi,

We want create a cluster with two nodes on our QV Server (one node no cluster) to separate the heavy reloads of the AccessPoint and QVS.

Now, we have the QV Server with one node, the reloads are all day running and the user experience is afected seriously. For this reason we want separate this services on two nodes. It is posible? What is needed?

Thnaks a lot.

[ESP]

Hola,

Queremos crear un clúster con dos nodos en nuestro Servidor QV (un nodo sin clúster) para separar las recargas pesadas de AccessPoint y QVS.

Ahora, tenemos el servidor QV con un nodo, las recargas se ejecutan durante todo el día y la experiencia del usuario se ve seriamente afectada. Por esta razón queremos separar estos servicios en dos nodos. ¿Es posible? ¿Qué se necesita?

Muchas gracias.

Labels (1)
1 Solution

Accepted Solutions
Sonja_Bauernfeind
Digital Support
Digital Support

There might be a little confusion on what exactly each of the services does, as moving the AccessPoint (WebServer) away from the QlikView server will not help with splitting up reload and user consumption.

  • The QlikView WebServer component is responsible for handling user web sessions, presenting the AccessPoint and Full Browser client (AJAX), and to direct the users to a QlikView Server.
  • The QlikView Server service is responsible for handling User Documents. It is the the engine (heart/brain), of the QlikView system and is the one that carries out all calculations and document loading for the end users.
  • The Distribution Service is the service responsible for handling backend tasks, such as reloading QlikView documents and creating QlikView documents (distribution).

If you have a Publisher license, you are able to do exactly what you plan on doing.

You can split out the environment to, for example, look like this:

  • QlikView Server & QlikView WebServer
  • QlikView Distribution Service, QlikView Management Service, (+Directory Service Connector)

This type of setup splits up user interaction (QlikView Server) and backend processes (Distribution Service).

As you noticed, I did not move the WebServer from the QlikView Server. You can do that as well though. But this setup is only possible with a Publisher license. Without a Publisher license, the Distribution Service and the QlikView Server cannot be separated, and moving the WebServer will not have any performance improving affect.

 

Note that this is only an example setup. 

Don't forget to Like posts and use the "Accept as Solution" button on content that answered your question! Thanks 🙂

View solution in original post

10 Replies
Chip_Matejowsky
Support
Support

First you'll need to ensure that QVS clustering is provisioned in the LEF file. The QVS LEF file must contain entry "NUMBER_OF_CLUSTER_NODES;X;;" where X = 2 or higher. If your current QVS LEF doesn't have this provision, you'll need to contact your Qlik account manager for assistance in getting the license sorted out.

See the Qlik Support articles "QlikView Server: A Simple Installation" & "How to Setup QlikView Server Cluster" for further steps on how to configure a QVS cluster.

Hope this helps,

Chip

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
Daniele_Purrone
Support
Support

If you plan to move the QlikView Distribution Service to a different machine, you will need to have a Publisher license as well. 

Without that, the QDS is bounded to the QVS.

With a Publisher license, you'll be able to split the services. Check this article for details: https://qliksupport.force.com/articles/000002874

Daniele - Senior Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.
Daniele_Purrone
Support
Support

@Chip_Matejowsky, my understanding is that they want to split QVS and QDS. If that's correct, they won't need to have 2 QVS cluster nodes.

Daniele - Senior Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.
rafael_qg
Partner - Contributor III
Partner - Contributor III
Author

Thanks, I will see that you say 🙂

rafael_qg
Partner - Contributor III
Partner - Contributor III
Author

Hi, my plan is to separate the AccesPoint of the scheduled loads to they doesn't work on the same node.

Is it posible?

I thought to enable the QVS in the 2 nodes, the QWS in only one node and QMS & QDS in the other node. Will it work well?

How can I get this?

Thanks a lot 🙂

 

 

 

Sonja_Bauernfeind
Digital Support
Digital Support

There might be a little confusion on what exactly each of the services does, as moving the AccessPoint (WebServer) away from the QlikView server will not help with splitting up reload and user consumption.

  • The QlikView WebServer component is responsible for handling user web sessions, presenting the AccessPoint and Full Browser client (AJAX), and to direct the users to a QlikView Server.
  • The QlikView Server service is responsible for handling User Documents. It is the the engine (heart/brain), of the QlikView system and is the one that carries out all calculations and document loading for the end users.
  • The Distribution Service is the service responsible for handling backend tasks, such as reloading QlikView documents and creating QlikView documents (distribution).

If you have a Publisher license, you are able to do exactly what you plan on doing.

You can split out the environment to, for example, look like this:

  • QlikView Server & QlikView WebServer
  • QlikView Distribution Service, QlikView Management Service, (+Directory Service Connector)

This type of setup splits up user interaction (QlikView Server) and backend processes (Distribution Service).

As you noticed, I did not move the WebServer from the QlikView Server. You can do that as well though. But this setup is only possible with a Publisher license. Without a Publisher license, the Distribution Service and the QlikView Server cannot be separated, and moving the WebServer will not have any performance improving affect.

 

Note that this is only an example setup. 

Don't forget to Like posts and use the "Accept as Solution" button on content that answered your question! Thanks 🙂
rafael_qg
Partner - Contributor III
Partner - Contributor III
Author

Thanks a lot SonjaB!! Smiley Happy

Then, I need mandatorily to have one Publisher Licence  and one Qlikview Server Licence to separate the QlikView Server & QlikView WebServer (and run the AccessPoint) of the QlikView Distribution Service, QlikView Management Service, (+Directory Service Connector) (to run the scheduling tasks). Is it correct?

Thank you very much!! 

 

 

 

Daniele_Purrone
Support
Support

Hi Rafael,
I can confirm that you correctly understood what @Sonja_Bauernfeind said. If you don't have currently a Publisher license, please contact your account manager for pricing details.

Have a great day!

Daniele - Senior Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.
rafael_qg
Partner - Contributor III
Partner - Contributor III
Author

Perfect!!

Thank you very much!! 🙂