Article Number: 000003336 | Last Modified: 2018/06/12
Using QlikView Workbench with a named instance of QVS (not “Local”), for example when the QVS is on a different server to their IIS/QVWS or when using QVS clustering.
There is a "No Connection" error, and the web server log shows that URLs are requested withe host=Local parameter.
According to the SDK documentation on http://qlikcommunity.s3.amazonaws.com/misc/symbols/Qv.Config.html#Host
"Host" is “Name of the QlikView Server Cluster. Defaults to Local”.
This will affect anyone using QlikView WorkBench with a named instance of their QVS (not “Local”), for example when the QVS is on a different server to their IIS/QVWS or when using QVS clustering.
The normal way you would initialise WorkBench on a website is by using something like the following:
This tells WorkBench to initialise with a document named “FilmsWebView.qvw”.
There is a difference in behaviour from the standard AJAX client. With the standard AJAX client if you do not specify the name of the QVS instance (in other words you don’t specify the “host=QVSName” parameter) then QlikView defaults to the named instance of the QVS as specifically defined against the QVWS/IIS in the QMC. However WorkBench defaults to “Local” which resolves to “localhost” assuming a vanilla installation of QlikView Server.
To use a different QVS name then you simply need to provide the “Host” parameter as part of the WorkBench initialisation:
where “QVS@qvcluster” is the name of the QVS instance as defined in the QVS.