You are on page 1of 5

QLIKVIEW DEVELOPMENT AND

DEPLOYMENT ARCHITECTURE
A QlikView Technical Brief

Published: February, 2011

qlikview.com

IE plugin. rename fields. The QVS handles client authorization against existing directory providers (e. The file type that is created using the QlikView Developer is known as a ‘QVW’ (. developing and implementing almost every QlikView deployment. one can also utilize Microsoft’s IIS for this purpose too). The QlikView Developer is also the environment where all user interface and user experience design is developed in a drag-and-drop paradigm: everything from graphs and tables containing slices of data to multi-tab architectures to application of color scheme templates and company logos and so forth is done here. QlikView Development and Deployment Architecture | Page 2 . Previously created SQL code can be ported into the QlikView Developer environment very easily. a QVW can be used to create a data-only ‘QVD’ file. QlikView Developer The QlikView Developer is a Windows-based desktop tool that is used by designers and developers to create 1) a data extract and transformation model and 2) to create the graphical user interface (or presentation layer). Upon reload. clustering. The web server’s user portal is known as “Access Point”. eDirectory) and also performs read and write to ACLs for QVW documents. apply expressions) so that it can be analyzed within the User Interface. QlikView Server (QVS) The QVS is a server-side product that contains the in-memory analytics engine and which handles all client/server communication between a QlikView client (i. as well as re-used by other QlikView files.e. AD.Products Overview The QlikView Business Discovery platform consists of 3 major components.g. desktop. negating the need for large amounts of re-work or re-coding when beginning to use QlikView within an existing BI framework. distribution etc.g. which is binary and contains no UI. (It’s important to note that while the QVS contains its own web server. It is within this environment where a developer will use a SQL-like scripting environment (augmented by ‘wizards’) to create the linkages (connection strings) to the source data and to transform the data (e.qvw). AJAX or Mobile) and the server.) and also includes a web server to provide front-end access to the documents within. It includes a Management Console for providing Administrator access to control all aspects of the server deployments (including security. each playing an important part in designing.

Pre-prod testing Source Documents QlikView Devloper QlikView qvw and qvd file structure Infrastructure resource NAS/SAN Storage SMTP service QlikView Publisher Diretory Catalogue (Active Directory.QlikView Publisher The QlikView Publisher is a server-side product that performs 2 main functions: 1) It is used to load data directly from data sources defined via connection strings in the source QVW files. QlikView Development and Deployment Architecture | Page 3 . E-Directory) DATA WAREHOUSE Data Source Figure 1 depicts a simplified view of a standard QlikView deployment containing the location of the various QlikView products as well as both data and application locations. Pre-prod testing User Documents QVP or HTTPS QlikView qvw and .meta file structure Front end Clients QlikView Server QVP Back end Development. 2) It is used as a distribution service to ‘reduce’ data and applications from source QVW files based on various rules (such as user authorization or data access) and to distribute these newly-created documents to the appropriate QlikView servers or as static reports via email. Figure 1: Architecture Overview ARCHITECTURE OVERVIEW Development.

Since all documents in the Front End are created via Publisher tasks. it is very straightforward to recreate all user documents by simply running these tasks again. QlikView Development and Deployment Architecture | Page 4 . Within the Front End.shared documents. created using the QlikView Developer. the QVS is responsible for client security. .com) or b) the actual binary data extracts themselves within QVD files. data warehouses. as stated above. End users can only access QlikView documents that exist on the Front End. It contains the QlikView user documents that have been created via the QlikView Publisher on the back end. Salesforce.log files are contained here. . In addition. It does not send any queries to data sources on the back end.BACK END (INCLUDING INFRASTRUCTURE RESOURCES): This is where QlikView source documents. the Publisher is responsible for data loads and distribution.e. The Back End depicted here is suitable for both development. if active.g. nor do any of the user documents (QVW’s) contain any connection strings to data sources located on the back end. The main QlikView product component that resides on the Back End is the QlikView Publisher and. it’s important to understand that the Front End does not have any open ports to the Back End. FRONT END The Front End is where end users interact with the documents and data that they are authorized to see via the QlikView Server. SAP. QlikView is not responsible for access privileges). reside. and never in the Back End. From a security standpoint. The file types seen on the Front End are QVW. the Windows file system is always in charge of authorization (i. All communication between the client and server occurs here and is handled either via HTTPS (in the case of the AJAX client) or via the QlikView proprietary QVP protocol (in the case of the plugin or Windows client). Excel files. Within the Back End. These source files contain either a) scripts within QVW files to extract data from the various data sources (e. testing and deployment environments.meta and .

if any. without representation or warranty of any kind. products and services used herein are trademarks or registered trademarks of their respective owners. separate environments. Data tier Here information is stored and retrieved from a database or file system. the product that provides for data loading and application and data distribution. In Figure 2.pdf to fully understand the optimal approach for an individual deployment scenario. QlikView Publisher A standard QlikView deployment using AJAX employs a Three-Tier architecture where data. The Uncontrollable Smile and other QlikTech products and services as well as their respective logos are trademarks or registered trademarks of QlikTech International AB. It’s important to note that within the Data tier.Figure 2: Three Tier Architecture EXAMPLE DEPLOYMENT IN AN N-TIER ENVIRONMENT 1. Communication from the Publisher to the Server is done securely via port 4747. Finally. Qlik. The Application (or Logic) tier contains the QlikView Server(s) and the user documents that have been distributed via the Publisher in the Data tier. and QlikTech shall not be liable for errors or omissions with respect to this publication. Application tier (Logic tier) It controls an application’s functionality by performing detailed processing. QlikView Server Port 4747 or CIFS/SMB Front end Back end 3. the Presentation tier contains the Web Server(s) (either the QlikView Web Server or IIS). Q. the highly important Data tier contains only the QlikView Publisher. Power of Simplicity. This is where user requests for application access are handled via the ‘Access Point’ portal. application and presentation layers are maintained in distinct. QlikTech. there are many different approaches to handling data access and modeling and one must carefully consider the various Data Architecture approaches covered in documents such as QlikView Data Architectures. This publication is for informational purposes only. Nothing herein should be construed as constituting any additional warranty. As mentioned above. © 2011 QlikTech International AB. QlikView Web Server Port 4747 2. All rights reserved. Presentation tier The main function of this interface is to translate tasks and results to something the user can understand. access to this tier is very limited and no end users or applications within the other 2 tiers have access to this layer and the data or files within. QlikView. Simplifying Analysis for Everyone. QlikView Development and Deployment Architecture | Page 5 . The only warranties for QlikTech products and services are those that are set forth in the express warranty statements accompanying such products and services. All other company names. The information published herein is subject to change without notice. New Rules.