Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Well this could be a lengthy topic.And it could be an overview (simplified) or very technical.
To be (or try to be) short from a tecnical perspective:
The fantastic four - starring: QVS, QVws, DSC and QMS in order of appearance with the help of DSC (possibly)
The two main components:
QlikView Server (QVS) is the application server that runs your multi-user shared QlikView Applications (QlikView Documents) so various clients can access these applications at the same time. The QVS
The clients can be: A browser (zfc Zero Footprint Client - Ajax client), Internet Explorer with the IE-plugin (Active-X), QlikView Desktop (by connecting with "Open in Server") and iOS-client.
The QlikView Server is complemented by the AccessPoint (QVws) that is a separate ASP.NET server application exposed as a separate Service on a Windows computer. This service for the AccessPoint can run on the same computer as the QlikView Server (application server) or on a separate computer. Furthermore the AccessPoint can use it's own webserver engine or Microsoft's Internet Information Server (IIS).
Communication:
The communication between all the various server services the QVP-protocol is used. To communicate with the browsers HTTP or HTTPS is used. To communicate with the QlikView Desktop as a client QVP is used with possible QVP-tunneling over HTTP as a "fallback" mechanism.
Other important components:
QlikView server architecture contains also the Distribution Service (DSC) that might be the basic reload engine or the full Publisher (additonally licensed) which is an extended reload engine. The latter is building upon that first one so they are closely related and always both referred to as DSC. The reload engine as the name DSC implies runs as a separate service on Windows. The reload engines responsibility is to run the load scripts and possibly distribute the resulting QVW's and other things as part of maintaining the application infrastructure and helping the QVS with refreshed data.
The reload enginge (DSC) can not be separated out from the computer running the QVS unless there is a Publisher license for it.
The QlikView Managment Service (QMS) is helping out with orchestrating the operational business of the server environment. It has a user interface which is web-based called QlikView Managment Console (QMC). It also has a managment API so you can programatically manage it externally QMSAPI and EDX (Event Driven Execution) for further non QlikView integration.
Lastly in the most prevalent QlikView setup you have the QlikView Directory Services Component (QDS). This service have the responsiblity of talking to various directory services providing a flexible authentication service for the server environment. Most customers of QlikView use Microsoft Active Directory as default.
QVS, DSC, QVws, QDS, QMS services on a single server environment where all the five are services on the same server:
