Skip to main content

Correlating key settings in QlikView Web Server and Qlik Sense Proxy

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Andre_Sostizzo
Digital Support
Digital Support

Correlating key settings in QlikView Web Server and Qlik Sense Proxy

Last Update:

Feb 15, 2021 6:57:43 AM

Updated By:

Sonja_Bauernfeind

Created date:

Sep 11, 2020 8:34:43 AM

This video aims at making a high level correlation of the key settings in QlikView WebServer and Qlik Sense Proxy and Virtual Proxy.

Video Transcript:

Hi and welcome to Qlik Fix.
This video aims at making a high level correlation of the key settings in QlikView WebServer and Qlik Sense Proxy and Virtual Proxy.
The "QlikView Webserver" service is the web server responsible for hosting the QlikView Documents when not hosting via an IIS server.
In Qlik Sense, access to the Apps via the Hub is hosted by the Qlik Proxy Service.
Looking at the QlikView Management Console under the Web Server's General tab, the settings align with what is available in Qlik Sense Proxy settings.
This includes Logging and configuring a certificate to be used with inbound secured https client connections.
Note that this setting along with all Virtual Proxy settings are used together when both the Proxy and Virtual Proxy are involved with the client's Web request. For example.
Proxy settings are specific to the server running the Proxy service, while Virtual Proxy is specific to the configured Prefix which is used when accessing the Hub or QMC.
Under Authentication options we see a one-to-one correlation with what is listed for Anonymous Access mode in Qlik Sense Virtual Proxy settings.
As far as Authentication Type, similar options are listed under the Qlik Sense Virtual Proxy settings, being that NTLM option will equate to the use of "Ticket" Authentication Method in Qlik Sense.
For Login Address in QlikView, the Default "Browser authentication" will occur for all major browsers also in Qlik Sense if the default string value for "Windows authentication pattern" is used.
So in order to use a Web form for authentication prompt, the "Windows authentication pattern" needs to be changed to a string that is not found in the "User-Agent" header which identifies the type of Browser the request came from.
For example, the word "Form" is not a word found in the User-Agent header using any major browser such as Chrome and IE, so the Login page will be displayed.
Under the AccessPoint tab for Server Connection in QlikView, we see the Load Balancing setting. The corresponding setting in Qlik Sense which uses a modified round robin algorithm, is found in Qlik Sense Virtual Proxy under Load Balancing.
It is important to note that one of the key Virtual Proxy settings "Session inactivity timeout", is not represented in QlikView WebServer settings.
It correlates to the setting "Maximum Inactive Session Time" found under the QlikView Server Performance tab.
Thanks for watching!

Related Content:

Labels (3)
Version history
Last update:
‎2021-02-15 06:57 AM
Updated by: