Databases Reference
In-Depth Information
Create content
The Windows application we used earlier to navigate and analyse the data in
Movies
Database
can not only be used to consume content, but it is also the main tool with
which to create QlikView documents. As this topic is focused on developers, this will
be the main focus for the remaining chapters.
Reload, publish, and distribute content
When QlikView deployments expand, it becomes impractical to update and
distribute files manually. Also, data is loaded into RAM when using a local Windows
application to open QlikView files. When working with huge amounts of data, each
PC would also need a huge amount of RAM. This might work for developer PCs, but
it is hardly a cost-effective solution to outfit each user in the organization with large
amounts of RAM.
Fortunately, QlikView has three components to mitigate these potential roadblocks
to broader adoption:
•
QlikView Publisher
: This component can take care of reloading, reducing,
and distributing the QlikView documents. Jobs can be scheduled or triggered
by external events. When QlikView Publisher has not been licensed,
QlikView Server can handle the task of reloading QlikView documents.
•
QlikView Server
: This is a centralized server which can load QlikView
documents into memory and allows clients to interact with these documents
remotely by using one of the QlikView clients. In addition to providing a
central place where documents are stored, this also has the advantage of
clients not needing huge amounts of RAM and CPU cores.
The clients do not need to load all of the data locally and the processing
power of the server is used for calculating and aggregating data.
•
QlikView Access Point
: This is a portal through which users can access
their documents.
