Qlik Architecture

The Qlik view architecture comprises of three main components, namely 
● QlikView Server ● QlikView Publisher ● QlikView Desktop. 
All these components collectively help in designing, developing, and implementing the QlikView application. 
Front End The Front end in QlikView is a browser-based access point for viewing the QlikView documents. It contains the QlikView Server, which is mainly used by the Business users to access the already created BI reports through an internet or intranet URL. Business users explore and interact with data using this front end and derive conclusions about the data. They also collaborate with other users on a given set of reports by sharing insights and exploring data together, in real time or off-line. These user documents are in the format .qvw, which can also be stored in the windows OS as a standalone document The QlikView server in the front end manages the client server communication between the user and QlikView backend system. 
  Back End 
The QlikView backend consists of QlikView desktop and QlikView publisher. 
 The QlikView desktop is a wizard-driven Windows environment, which has the features to load and transform data from its source. Its drag and drop feature is used to create the GUI layout of the reports that becomes visible in the frontend. The file types, which are created by QlikView desktop are stored with an extension of .qvw. These are the files that are passed on to the QlikView server in the front end, which serves the users with these files. Also .qvw files can be modified to store the data-inly files, which are known as .qvd files. They are binary files, which contain only the data and not the GUI components.
 The QlikView publisher is used as distribution service to distribute the .qvw documents among various QlikView servers and users. It handles the authorization and access privileges. It also does the direct loading of data from data sources by using the connection strings defined in the .qvw files. 

3-tier architecture. This is simple 3 apps that do different things. The first 2 apps act as an ETL process and the third app will be the visualization layer. 
Therefore, the first app, Tier 1, will only get source data from wherever and store it into different QVD's. 
 The second app uses the QVD's from Tier 1 and does all the modelling and transformations and stores this into a more star schema structure. 
Tier 3 will then just read these QVDs and display the analytics as we need.

Comments

Post a Comment

Popular posts from this blog

Section Access

Section access is similar to reduction, but is done by the QlikView Server when a user accesses the document. The choice between section access and static reduction is a question of performance and memory usage. When QlikView Publisher opens a section access protected QlikView file, the file is reduced based on the reduction values Table Columns The following table columns are available: ACCESS, a field that defines what access the corresponding user should have. The following options are available in the drop-down list: l ADMIN 2 USER OMIT, a field that should contain the field that should be omitted for this specific user. Wildcards may be used and the field may be empty. A facile way of doing this is to use a sub field.
Read more

Binary Load

Advantages: Really FAST You can hide script from users. You can load a whole model with only one line of code Section Access also transferred Cons: Lack of flexibility Can load only one model Binary load is used only for one application means you are able to read data from only one QVW application and on the above of the set scripts is a restriction. should be done at the begining It does not load the layout information or variables you can load variables into a table in the source document and then retrieve them from the table (using peek()) in the target document. You could use an include file to hold the variable definitions and then call the include file in both QVWS.
Read more