Vizlib Home
Welcome
Login

Vizlib Teamwork -Virtual Proxy Configuration for a multi-node Qlik Sense Environment (Enterprise only)

To set up Vizlib Teamwork for a multi-node configuration, you will need to configure the Virtual Proxies. These changes need to be done for all Virtual Proxies on apps used with Vizlib Teamwork.  

Please ensure  Qlik sense backend node is whitelisted with the configuration DNS


In order to share the cookies with the Vizlib Server, you need to change the session cookie domain property in the Virtual Proxy, but you cannot do that on the default proxies. If you did, you could potentially lock everyone out of the system. Therefore the session cookie domain property on the default Virtual Proxies is read-only. For this reason, you need to create a new Virtual Proxy that will be set up like the original default one.  You need to follow this procedure for each Default Virtual Proxy unless there are already non-default Virtual Proxies set up and in use. Then only follow the step on how to change the session cookie domain.


Below, you’ll see the detailed step-by-step instructions for a multi-node Qlik Sense environment with only default Virtual Proxies. The guide goes through how to configure the Central node. You need to follow this procedure for each used default Virtual Proxy of your account. 


Initial Nodes Configuration: One Central node, and two additional nodes with the following configuration: (see Picture 1)


Picture 1


Please note that each default Virtual Proxy you use needs to be replicated. So if you start with 3 default Virtual Proxies, you should end with 6 Virtual Proxies in total (see Picture 8: final configuration that you are aiming for.)


Start by creating a new Virtual Proxy with the same configuration as the default Virtual Proxy of the Central node. 


Select Advanced on the new Virtual Proxy, and then add your domain name in the Session Cookie Domain field: the cookies will be shared on the subdomains of this main domain. (See Picture 2.


Picture 2


For testing purposes, you’ll add a prefix (this will be removed later if the test is successful). See Picture 3.


Picture 3


Your new Virtual Proxy needs to have the same configuration as the Default Virtual Proxy that you are replicating. (In this instance, it’s the central one.) If the default proxy contains a Proxy link to the Central node, then your replicated Virtual Proxy must have the exact same link. You need to check the configuration of your default virtual proxy in order to check which Proxy link needs to be added to your Virtual Proxy replication. 



Before you link the Proxy to the Virtual Proxy you need to change the cookies header name of your new Virtual Proxy: for example, you can change it to X-Qlik-Session-vizlib (See Picture 4).


Picture 4


If you try to link the Proxy before updating the session cookie header name, the following error will be displayed: The session cookie header name must be unique. (See Picture 5.) 

Picture 5


Now that the Session Cookie header name has been changed, the Virtual Proxy can be linked to the relevant node. (Again, it’s the central node, but each Default Virtual Proxy will have a different link. Please check which node it is linked to in the relevant default Virtual Proxy.)

In order to add a Proxy link to your Virtual Proxy, you need to select Proxies (see Picture 6) and then select Link at the bottom of the page (see Picture 7). 


Picture 6


Picture 7


Important: All properties of the default Virtual Proxy need to match the new one. Remember to go through all sections and make sure that they match except for the session cookie domain, prefix, and cookies header name.


Now that you have replicated the default Virtual Proxy, you need to follow the exact same steps as above with the other default Virtual Proxies for Rim_Node1 and Rim_Node2. So, if you have 3 nodes in your initial configuration, you should have 3 default Virtual Proxies, and each of them needs to be replicated. You should end this procedure with 6 Virtual Proxies (See Picture 8: same picture as the one provided at the start of the procedure). 


Picture 8



Verify that the new Virtual Proxies work by opening up the URL with the correct prefix https://yourdomain.com/vizlib/hub and open up a demo Teamwork app. If everything works you can proceed to the other nodes.

As it is set up now, the new Virtual Proxy has the “vizlib” prefix, but once the procedure is complete for all of your nodes, you will change the prefix in the Central node to “default” which will enable you to remove the “vizlib” prefix from the Virtual Proxy (added earlier for testing purposes). The users will then be able to connect to their usual URLs and use Vizlib Teamwork. 


Coming soon: an article about the VMC configuration and the exported certificates in a multi-node Qlik Sense environment


P
Pablo is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.