Welcome Guest, you are in: Login

QVSource: The QlikView & Qlik Sense API Connector (Docs)

Web Edition Doc Quick Links
QVSource Web Edition is now commercially available should be used - if you are still using the WinForms edition please upgrade now as this is deprecated and will no longer be supported after the 22nd May 2016.

You should find most of the documentation on this wiki for the WinForms edition of QVSource still applies, particularly the connector specific pages (ignoring the minor UI differences).

The following are the most important Web Edition specific pages:

  • Web Edition Overview - A short introduction to the new QVSource Web Edition including the benefits and high level differences.
  • Getting Started - A guide on running the QVSource Web Edition in its simplest mode (e.g. servicing requests from localhost only with no user authentication).
  • Example Deployment Scenarios - Some example diagrams showing how QVSource Web Edition might be deployed with QlikView and Qlik Sense.
  • Advanced Configuration - How to perform advanced configuration of QVSource, for example allowing remote access and setting up users.
  • User Management - How to manage users.
  • Upgrading from WinForms Edition - How to upgrade.
  • SSL Configuration - How to set up a test SSL certificate so that traffic between your browser (or QlikView/Qlik Sense) is encrypted.
  • Troubleshooting - Read this page first if you are having trouble running QVSource.
  • Cloud Hosted Demo - Information on a cloud host demo edition we are currently testing out.


On this page we will sketch out some typical deployment scenarios for the new QVSource Web Edition.


QlikView Deployment Examples

Example QlikView Deployment 1

This is probably the way QVSource Web Edition will replace the most common deployment scenario which is in use with the previous WinForms edition, where developers use QlikView Desktop to develop and test QlikView applications locally (QVW files) before deploying to a production (or perhaps test) server for consumption by end users.

Now, instead of having QVSource installed on every machine where a QlikView reload is taking place (which would have been the two QlikView developer laptops and the QlikView server in the diagram below) it is now only installed on one machine and the two QlikView Desktop instances and the QlikView Server instance all make requests to this single instance.

Note that QVSource could also be installed on the same machine as QlikView Server is installed on and indeed this might make sense and mean utilising one less server. However here we illustrate a scenario where QlikView Server may not have access to the internet and so QVSource is installed on a machine in the DMZ which does have access to the internet.



Example QlikView Deployment 2

In this example, QVSource Web Edition is running on the same machine as QlikView Server and both environments are cloned, one for test and one for production.

It is important to remember here that the settings from the test QVSource Web Edition need to be mirrored across to the production server so a process should be in place to do this. In a practical sense this means that any users set up for QVSource which are being used by the load script exist on the production server and that any settings for connectors which are being used (which are not embedded in the load script, e.g. access tokens) are set up - this may mane the developer simply needs to login to QVSource on the production servers and set them up in the same way as they are on the test server. Alternatively a more automated system could be set up which copies across the QVSource settings files.



Qlik Sense Deployment Examples

Example Qlik Sense Deployment 1

In this example, QVSource Web Edition and Qlik Sense are installed on the same machine. A small number of Qlik Sense users are also licensed with logins to QVSource. This means that they can work with connectors, generate load scripts and embed these in their Qlik Sense applications which are then used also by other Qlik Sense users who do not have direct QVSource access.



Example Qlik Sense Deployment 2

This is very similar to the above, the only difference being that QVSource and Qlik Sense Server are installed on different machines. The QVSource machine might for example be in a DMZ with access to the internet.



(QVSource works with Qlik Sense as well as QlikView - See this page for notes.)
QVSource - The QlikView & Qlik Sense API Connector | © Copyright 2011 - 2016 Industrial CodeBox Ltd