1. QlikView Architecture Overview

2. QlikView Component Architecture

3. In-Memory Technology Easily consolidates multiple data sources
Loads all data into memory, not just selected cubes or static data sets
User selections (queries in traditional BI) only initiate traffic between RAM and CPU

4. The Associative Experience
Traditional
Associative
Patient
Visits
Location
Episode
Patient
Location
Episode
Visits
IT-Driven
Linear, pre-defined thinking
Insights missed in hidden data
Months to change
Data-centric
User-Driven
Follows the user
All data is always visible
Minutes to change
Insight-driven

5. QlikView Skills Are a Great Fit
Most of the skills involved with designing, developing and maintaining QlikView solutions are not only familiar to IT teams, but are skills that are available in abundance.
There are a small set of skills specific to QlikView, for which one week of training will fully satisfy (includes Administrator, Designer and Developer training). 5

6. .QVW Files QlikView Developer
A .QVW file is the application file for QlikView. It contains the scripting, data model, data and user interface for a dashboard (or application).
QlikView Developer
ODBC
Script
DATA
OLEDB
File
QlikView Desktop
GUI
Custom
Data
QlikView
Application File
.QVW
Data
Several architectures are possible with QlikView. These help you balance the speed you will want for prototypes and quick mash-ups and the consistency and re-use you will want with larger production applications.
Show the direct query. This is mainly used for prototyping and data discovery.
Show the 2-tiered build. This is very common for most applications. QVD files are highly compressed, proprietary table storage files for QlikView. They are used as staging tables and help promote re-use, consistency and speed of development. They are also an essential part of incremental (delta) load strategies.
Show the 3-tiered build. This is mainly used when aggregation or segmentation of QVD files is needed to accommodate very large data models (typically hundreds of millions of rows).
Show the 3-tier mixed build. This is mainly used when the development (back-end) and design (front-end) are split between a technical team and a business team. The technical team builds out the data model using QVDs and then loads them into a QVW Model. This is a QVW file with just a data model, no interface. The business team then gets a template QVW with this data model and can build the UI from there.
Stress that a combination of these approaches is routinely employed by our large clients. They usually start from the left side and progress to a mixture of techniques as they deploy more QlikView applications. QlikTech Expert Services can help align these architectures very quickly and efficiently.
XML
Security
SAP
SFDC 6

7. QlikView is a Platform That Scales
NUMBER OF USERS
DEPLOYMENT TYPE
10,000X
IE plug-in
AJAX
Enterprise:
QlikView Local Client
Clustered QlikView Servers
Clustered QlikView Publishers
25X
iPad
iPhone
10X
Departmental:
QlikView Local Client
QlikView Server
QlikView Publisher
Message 1: QlikView can grow from a small, single laptop deployment to a 10,000+ user deployment.
Message 2: QlikView scales from one laptop to a clustered farm with 10,000+ users without the re-architecture of any applications. This is drastically different than many BI tools that will force you to re-design and re-deploy applications as they scale out to larger user bases.
Message 3: As you scale QlikView applications to larger audiences you will be faced with requests for more client access types (AJAX, plug-in, download, mobile, etc…). QlikView allows you to create the application once and then deploy to several formats without maintaining separate copies of the application.
Blackberry
Android 1X
Small Workgroup:
QlikView Local Client
Single User:
QlikView Local Client (Personal Use License)

8. .QVD Files
A QVD (QlikView Data) file is a file containing a table of data that QlikView has extracted from one or more data sources. QVD is a native QlikView format and can only be written to and read by QlikView. They are created with the scripting that is included in the QVW files.
Single Source of Truth
Resource Flexibility
Development Flexibility
Development Speed
Delivery Flexibility
Incremental Loads
Very Fast Data Loads
Several architectures are possible with QlikView. These help you balance the speed you will want for prototypes and quick mash-ups and the consistency and re-use you will want with larger production applications.
Show the direct query. This is mainly used for prototyping and data discovery.
Show the 2-tiered build. This is very common for most applications. QVD files are highly compressed, proprietary table storage files for QlikView. They are used as staging tables and help promote re-use, consistency and speed of development. They are also an essential part of incremental (delta) load strategies.
Show the 3-tiered build. This is mainly used when aggregation or segmentation of QVD files is needed to accommodate very large data models (typically hundreds of millions of rows).
Show the 3-tier mixed build. This is mainly used when the development (back-end) and design (front-end) are split between a technical team and a business team. The technical team builds out the data model using QVDs and then loads them into a QVW Model. This is a QVW file with just a data model, no interface. The business team then gets a template QVW with this data model and can build the UI from there.
Stress that a combination of these approaches is routinely employed by our large clients. They usually start from the left side and progress to a mixture of techniques as they deploy more QlikView applications. QlikTech Expert Services can help align these architectures very quickly and efficiently. 8

9. QlikView is an Architecture That Scales
Several architectures are possible with QlikView. These help you balance the speed you will want for prototypes and quick mash-ups and the consistency and re-use you will want with larger production applications.
Show the direct query. This is mainly used for prototyping and data discovery.
Show the 2-tiered build. This is very common for most applications. QVD files are highly compressed, proprietary table storage files for QlikView. They are used as staging tables and help promote re-use, consistency and speed of development. They are also an essential part of incremental (delta) load strategies.
Show the 3-tiered build. This is mainly used when aggregation or segmentation of QVD files is needed to accommodate very large data models (typically hundreds of millions of rows).
Show the 3-tier mixed build. This is mainly used when the development (back-end) and design (front-end) are split between a technical team and a business team. The technical team builds out the data model using QVDs and then loads them into a QVW Model. This is a QVW file with just a data model, no interface. The business team then gets a template QVW with this data model and can build the UI from there.
Stress that a combination of these approaches is routinely employed by our large clients. They usually start from the left side and progress to a mixture of techniques as they deploy more QlikView applications. QlikTech Expert Services can help align these architectures very quickly and efficiently. 9

10. Co-Development - Utilizing Existing Skills
I.T. or Central QlikView Team
Traditional BI Skills
Querying
Data Modeling
Data Analysis
Using IT for the technical work and Business teams for the Design work allows a QlikView deployment to expand to orders of magnitude larger size without expanding the I.T. team. This provides:
Happier I.T. team
Happier, more engaged Business teams
Faster time to market for new dashboards
More consistency in data models and results
Less code to maintain, lower TCO
More flexible resource model, allowing for rapid growth and change over time in roles
Interface Designers (business unit or I.T.)
Design Skills
Drag-drop
Menu driven

11. enable these while you work on these BI Delivery Quadrants
Highly provisioned data means it is in a ready state to be easily used by Designers of QlikView. This would mean the data is in either aggregated, simplified QVDs or QlikMart QVWs ready for binary loading.
Non-provisioned data is QlikView data that is not yet in the ready state for Designers and would likely need to have scripting or data modeling knowledge to use it.
Undeveloped requirements are those where the user is not sure what they want, and will therefore require several iterations of design to get to a final dashboard or deliverable.
Highly developed requirements are when a user has a very specific set of metrics that are well-defined and the user knows exactly how he/she wants to see them in QlikView.
Data Discovery/Scoping – QlikView developers mash-up data sources to determine certified sources and scope requirements
QlikView Projects – Develop from sources to QVDs to QVWs
Business Discovery – allow enabled designers to “discover” in a sandbox or safe environment
Self Service – allow collaboration and designer users to design from existing QlikMarts or templates

12. Enterprise Case Study – Small Deployment
SAP Data
Oracle Data
16 QV Data Files
1.5 GB Data
~100 M rows
14 loaded in full – daily
2 loaded incrementally
Publisher
8 Dashboards
Reloaded Daily
Avg. 2 minutes load
QV Production Server
12 CPU cores
64 GB RAM
Publisher
Server
QVW File
QVD File
Just 4 moving parts
240 users
150+ daily 12

13. Enterprise Case Study – Mid-Sized Deployment
AS/400 Orders
Oracle Data Mart
SQL Server DBs
Excel Files
84 QV Data Files
12 GB Data
~800 M rows
58 loaded in full – daily
26 loaded incrementally
Publisher
23 Dashboards
21 Reloaded Daily
2 Reloaded Weekly
QV Test/Dev Server
QV Production Server(s)
16 CPU cores
64 GB RAM
8 CPU cores
32 GB RAM
Publisher
Server
QVW File
QVD File
Just 4 moving parts
600+ users
Laptops
iPads
iPhones 13

14. Enterprise Case Study – Large Deployment
SAP Data
Oracle DW
SQL Server DBs
Flat Files
148 QV Data Files
62 GB Data
~2.8B rows
Full and incremental loads
~2 hours load time per night
Publisher 1
(QVDs)
Publisher 2
(QVWs)
52 Dashboards
Daily & Hourly Loads
~1 hour load time per night
~ 5 minute load time per hour
QV Test Server
QV Dev Server
QV Production Server(s)
16 CPU cores
128 GB RAM
48 GB RAM
Publisher
Server
QVW File
QVD File
Just 4 moving parts
~4,600 users
Laptops
iPads 14

15. Scalability Example
One QlikView dashboard can do the work of dozens of traditional BI deliverables…at a fraction of the cost.
FAST IMPLEMENTATIONS and EASY TO USE:
QlikView is enabling fast time to value as highlighted by these customer examples - proof of concept development in hours, implementation in days, and training in minutes. One of the telling statements is with Superior Graphite – ”they were able to do in four hours with QlikView with one resource, what they couldn’t do with a team of consultants for 18 months using OLAP cube technology with SAP BW.”

16. QlikView Metadata 3 Types Collection Storage
Descriptive – provides rich context about the makeup of a document
Administrative - Provides centralized or application-specific views of application reloads, user access, usage, performance, and scheduling
Structural - Describes elements of an application such as its data sources and repositories, tables, columns, expressions, charts, and graphs
Collection
Can be collected from QlikView objects at any time. Does NOT need to be forced on developers and designers as they construct.
QlikView provides a “MetaScanner” (QlikView) application to accomplish this.
Message:
QlikView takes a pragmatic approach to metadata. With QlikView, metadata management is optional and retrospective and developers can introduce metadata usage over time. We don’t require a huge upfront metadata effort. QlikView handles three types of metadata—descriptive, administrative, and structural—and makes it available through the QlikView Monitor and a dashboard template. QlikView’s metadata model is a centralized, automated collection, organization, and presentation of metadata for monitoring and distributed use within dashboards. The model is a collection of tables exported from QlikView.
This is a unique approach in the BI industry, getting away from the monolithic metadata repositories of the 1990’s and using a streamlined, value-added collective of the most useful metadata for developers, designers, administrators and end users of QlikView.
Storage
Stored in a QVD structure – simple, efficient and fast
Easily readable or exportable to other formats – embed in dashboards or use monitoring tools to explore the metadata in QlikView
Uses QlikView to Manage QlikView – no additional software/hardware

17. Speed Scalability Sandbox Capacity Plans Collaboration
Simplicity does not mean we can ignore basic principles of the Software Development Life Cycle. The key is that balance the needs of the end users and still keep IT happy and supportive of our approach. We need to make sure IT is involved early and are part of the strategy planning so rules are followed and QlikView systems are sound.
Users want speed and flexibility
IT wants scalability and reliability
You CAN have both
Our most successful clients do this because the established proper strategies and plans.
Collaboration
Monitoring Tools
Co-Development
Meta Model
Self-Service BI
Single Source of Truth 17

18. QlikView Enterprise Framework
best practices
white papers
demo apps
code samples
tips and techniques
…..for enterprise scaling and deployment of QlikView.
The Enterprise Framework is a collection of best practices, white papers, demo apps, code samples, tips and techniques for enterprise scaling and deployment of QlikView. The contents are intellectual property of QlikTech and are generally used as part of QlikTech’s Expert Services offerings.
The speaker should use this for talking points and help to outline an SDP for a technical implementation planning session. 18

19. High Level Security Overview

20. QlikView Security – Dynamic Reduction
Architecture overview 1/3

21. QlikView Security – Loop and Reduce
Architecture overview 1/3

22. Server Components and Scaling

23. QlikView Server - Components
Architecture overview 1/3
QlikView Developer

24. QlikView Server - Three-tier Architecture
To create a tree-tier Architecture put the QlikView Web Server or IIS on a separate front server (Virtual machine) in front of the QlikView Server.
This design works better with AJAX only. The QVP protocol will communicate directly to QlikView Server when using the Plug-in Client.
Tree-tier Architecture 1

25. Hardware Scaling – Scaling Up QlikView Server
Add more memory
Add more CPUs or cores
Scaling QlikView 1/4

26. Hardware Scaling – Scaling Out QlikView Server
Add additional servers to create a QlikView Server Cluster
Automatically loading applications on each node for maximum memory balance
A hardware load balancer or DNS round robin could be added for http failover
QVWS/IIS is on the same server as the QVS
No Windows cluster functionality is needed
Scaling QlikView 2/4

27. Hardware Scaling - Scale up QlikView Publisher
Add more memory
Add more CPUs or cores
Scaling QlikView 3/4

28. Hardware Scaling - Scale Out QlikView Publisher
Add additional servers to create a QlikView Publisher Cluster
Publisher tasks will automatically distributed between the nodes according to a configurable memory, load and CPU formula.
No Windows cluster functionality is needed
Scaling QlikView 4/4

29. Scaling example in a Three-tier Architecture
Adding extra web servers in the presentation tier creating a QlikView Web Server cluster
Use a load balancer on top to balance HTTP/HTTPS traffic to the nodes
Adding extra QlikView Servers in the Application tier
Creating QlikView Server cluster
Or two separate QlikView Servers
Three-tier Architecture Scaling 1

30. User License CALs
Scaling QlikView 3/4

31. Thank You!