
Meltdown and Spectre are two vulnerabilities disclosed in early 2018 that affect nearly every processor manufactured in the last 20 years. The initial assessment was that patching these vulnerabilities could in some cases lead to a 30% performance decrease on server workloads. Those are very serious numbers!
This may read like old news, but new patches have become available and some recommendations have changed. It is a good idea to regularly check up on these issues and avoid further problems.
read more »
February 23, 2017 – 17:06
When comparing Qlik Sense to QlikView, the most obvious differences are on the front-end, with its completely overhauled and fully responsive design. Other major differences are the server-based development, the use of Master Items and the shift towards APIs, mashups, extensions and widgets.
Somewhat less prominent, though very deserving of your attention, is the security model in Qlik Sense. This has a completely new approach compared to QlikView, and you can pretty much create endless variations. Rather than hacking stuff together and hoping it works, my colleague Rik and I recently decided to take a more structured approach and do some R&D on Sense security rules. Our goal was to gain more understanding of security in Sense, develop methods for gathering and modeling security requirements and to design reference patterns for common implementation scenarios.
We will be sharing some of the methods and patterns that we came up with in an upcoming white paper. In the mean time, I’d like to share with you some of the little interesting, strange and otherwise noteworthy things that we found. These range from basic to slightly obscure, but all should hopefully help you get more understanding of Qlik Sense security rules. Let’s start with noting that the approach in Sense is totally different than it was in QlikView…
read more »
This is a sneak-peek at one of the topics covered in the Server Admin best practices session at the Masters Summit for QlikView:
When doing QlikView Server deployments for clients, I often come across policies stating that the C: drive, the default installation drive for QlikView, may only be used for the operating system. Program files, data and logs all need to be placed on other, designated drives. The rationale for this policy is that data, and especially log files that aren’t purged, can fill up the boot drive and disrupt the system.
Specifying alternative locations for program files is simply a matter of specifying another installation path during setup, and the location of data and QVWs can be easily configured in the QMC. Moving log files is a little more complex however, so today I have for you a tutorial explaining two options for moving your log files and other configuration artifacts. read more »
November 29, 2012 – 18:00
Today, instead of a tip, I have a little anecdote about how QlikView helped me fix QlikView.
One project had me setting up a customized QlikView Server environment for an enterprise client. Part of the customization was ensuring that the service accounts, the ‘users’ that are used to run the QlikView services, do not require local administrator privileges.
Anyone who’s had to deal with this requirement knows that it isn’t exactly a straightforward job. Out of the box, the QlikView services will not work without local admin privileges. There is some help, but on a typical ‘hardened‘ version of Windows Server you still need to do additional troubleshooting to make things work.
read more »