Skip to main content

A simplified view of a QlikView tool:

In our last blog related to Qlikview, we discussed the use of Qlikview for Financial Data Analytics. Qlikview is a Business Intelligence tool that consists of a front end to visualize the processed data and a back end to provide the security and publication of the mechanism for QlikView user documents.

The Qlikview in-memory architecture virtually eliminates the problems and complexity plaguing traditional, slow, disk-based, and query-based BI tools that deliver little more than static, prepackaged data.With QlikView, all your data is loaded in memory and available for instant associative search and real-time analysis with a few clicks.

The diagram given below depicts the internal working of QlikView:

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 Business users to access the already created BI reports through an internet or intranet URL.

Qlikview Server :

The QlikView server in the front end manages the client-server communication between the user and the QlikView backend system.

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.e. desktop, IE plugin, AJAX, or Mobile) and the server. It includes a management environment (QlikView Management Console) for providing administrator access to control all aspects of the server deployments (including security, clustering, distribution, etc.) and also includes a web server to provide front-end access to the documents within. The web server’s user portal is known as Access Point. (It’s important to note that while the QVS contains its own web server, one can also utilize Microsoft IIS (Internet Information Server) for this purpose, too).The QVS handles client authorization against existing directory providers (e.g. Microsoft Active Directory, eDirectory) and also performs read and write to ACLs (access control lists) for QVW documents.

Back End:

The QlikView backend consists of QlikView Desktop and QlikView Publisher.

QlikView Desktop:

The QlikView Desktop is a Windows-based desktop tool that is used by business analysts and developers to create a data model and to layout the graphical user interface (GUI or presentation layer) for QlikView apps.

The QlikView desktop is a wizard-driven Windows environment, which has the features to load and transform data from its source. The files created by QlikView desktop are stored with an extension of .qvw.

QlikView Publisher:

The Qlikview Desktop data is passed on to the QlikView server in the front end, which serves the users with these files. The Qlikview .qvw files can be modified to store the data-only files, which are known as .qvd files.

The QlikView Publisher is used as a distribution service to distribute the .qvw documents among various QlikView servers and users.

The QlikView Publisher is a server-side a product that performs two main functions:

1) It is used to load data directly from data sources defined via connection strings in the source QVW files.

2) It is also 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 privileges) and to distribute these newly-created documents to the appropriate QlikView Servers or as static PDF reports via email.

Accepted File Structures in Qlikview:

QlikView accepts an Excel spreadsheet for data analysis by simple drag and drop action. By using the Load Script option in Qlikview Desktop shows the command that loads the data into the QlikView document.QlikView loads CSV files using the Data from file options available in the script editor under the File Menu. Alternatively, you can also open a new QlikView document and press control+E. We can connect to the SQL Server or Oracle database by using ODBC and OLE DB connectors available within Qlikview.

 Qlikview  Capabilities:

QlikView runs a natural search through all the available data stored in memory. Users can carry out fast and easy data discovery and analysis processes within QlikView apps. QlikView provides a unique cloud-based data service. So by using RESTful API connectors we can connect and integrate with data sources such as LinkedIn, Facebook, Twitter. The Qlikview is also compatible with iOS and Android devices through the QlikView Servers' great mobility and ease in data analysis, report generation, and sharing on the go. Qlikview offers charts, graphs, tables, and other attractive visual aids, for displaying the data reports. Data from different sources (even from traditional sources like data warehouses) is loaded in the RAM of the system and is ready to be retrieved from there, causing fast retrieval of data.

About Amlgo Labs : Amlgo Labs is an advanced data analytics and decision sciences company based out in Gurgaon and Bangalore, India. We help our clients in different areas of data solutions includes design/development of end to end solutions (Cloud, Big Data, UI/UX, Data Engineering, Advanced Analytics, and Data Sciences) with a focus on improving businesses and providing insights to make intelligent data-driven decisions across verticals. We have another vertical of business that we call - Financial Regulatory Reporting for (MASAPRAHKMAEBAFEDRBI etc) all major regulators in the world and our team is specialized in commonly used regulatory tools across the globe (AxiomSL Controller ViewOneSumX DevelopmentMoody’s RiskIBM Open Pages etc).We build innovative concepts and then solutions to give an extra edge to the business outcomes and help to visualize and execute effective decision strategies. We are among top 10 Data Analytics Start-ups in India, 2019 and 2020.

Please feel free to comment or share your views and thoughts. You can always reach out to us by sending an email at or filling a contact form at the end of the page.



  1. Pretty good post. I just stumbled upon your blog and wanted to say that I have really enjoyed reading your blog posts. I hope you post again soon. Big thanks for the useful info. Philippines Import Data


Post a Comment

More Popular Posts

Amlgo Blog - Experience The Experiments

Amlgo Labs Blog  is a step towards our vision to share knowledge and experiences, Amlgoites accept every challenge very enthusiastically. We do experiments, we fail but we learn and build complex solutions to help our clients solve their problems in Data, Analytics, Prediction, Forecasting, Reporting, Designing and Development area. During this process we enjoy immense learning everyday and we have decided to share our thoughts, learnings, experiments and experiences so that we don't work in silos and contribute the best of our knowledge towards community and learn more by views and reviews. This website is maintained and brough to you by  Amlgo Labs Professionals .   Our Strong Basics -  1)   KISS (Keep It Simple and Straightforward) :  We believe most of the problems can be solved by keeping things simple and straight. This is the learning we had in past, sometimes we try to solve technical problems using high end algorithms and complex codes but this results into complications.

Polybase : Polybase Scale-Out Group

In the last blog, we discussed the Introduction of the Polybase and the Implementation process of Polybase in SQL Server . PolyBase Scale-out Group consists of multiple virtual machines, each having its own SQL server instances which help in parallel processing and distribution of data. Data loading and query performance can increase in the direct proportion of the number of SQL server instances on each virtual machine.

Polybase Blog - Introduction

Overview: This Polybase blog series is all about the use of Polybase Technology in today’s era to be able to take advantage of the Data(Relational and Non-Relational) by using T-SQL only. Data whether Big or not is the lifeline to many different sectors to cope up with Production, Maintenance, Predictions, Taking Precautionary Measures, Customer Satisfaction, Customer Retention, Sales, Revenue Generation and many more.

Financial Regulatory Reporting

This blog is an introduction to the Regulatory Reporting. Regulatory reporting is mandatory activity banks have to perform with the coordination of Treasury, Group Finance, IT, and business lines. Regulators across the globe depend on accurate and timely submission of various Risk and non-risk reports by banks to measure the overall health of the banking sector.

Polybase Installation for Scale-Out process

This part is the continuation of the previous blog about the introduction of  Polybase Scale-Out Group . As we have discussed in our earlier blog PolyBase enables your SQL Server instance to process Transact-SQL queries that read data from external data sources. SQL Server 2016 and higher can access external data in Hadoop and Azure Blob Storage. Starting in SQL Server 2019, PolyBase can be used to access external data in SQL Server, Oracle, Teradata, and MongoDB.

Stages of New Regulatory Reporting Implementation

In the last blog, we discussed what is  Financial Regulatory Reporting  and its importance in the banking industry. Regulatory Reporting comprises the submission of business numbers as required by regulators to evaluate and track the financial and operational status of financial institutions and their compliance with required regulatory provisions.