QlikView Reviews

PART 1
---------
QlikView is a great business discovery tool that can easily generate excitement among business users. However, to build out a QlikView system that can support tens, hundreds, or even thousands of users is no easy task. As a QlikView consultant I have seen these scenarios many times:

- A business analyst is eagerly showing an IT manager the beautiful dashboards he/she builds in QlikView, and can’t wait to show the dashboards to hundreds of internal and external users;
- A business executive wants all business users to self-service their information needs through a QlikView platform.

Often times the IT managers seem to be less excited than their business counterparts. To be fair, in order to build a solid system, IT managers have a lot of questions that need to be answered. Let’s take a look at the most commonly seen ones (I have to warn you it’s a bit technical).

-- VMware for the servers? --

Nowadays most IT infrastructure professionals are in love with Virtual Machines (VMs). With its lower cost and flexibility in terms of horse power, VM seems to be the way to go for all enterprise applications. Well this is almost true for QlikView. All components of QlikView services can work fairly well on VM except for QlikView Server. This is because QlikView Server does the heavy lifting in-memory data processing, and the extra VM layer is going to slow it down, a lot. Most seasoned QlikView consultants would recommend at least using a physical machine for the production QlikView server.

-- Separate Publisher from Server? --

The two most important components in a QlikView system are the QlikView Server and Publisher (aka Distribution Service, I am a QlikView veteran so I will stick to the old name). Most people install all components on the same machine but as your data volume and user base grow, people frequently see these two components getting in the way of each other. At this point, it might be a good idea to put Publisher on a second machine (by the way, that second machine could be a VM). The good news is you can still manage both the QlikView Server and Publisher from a single QlikView Management Console (QMC).

-- QlikView Web Server or IIS? --

QlikView comes with its own web server, which is a light version of Microsoft Internet Information Service (IIS). In a perfect world, where all users are Active Directory users, and the number of users is small, QlikView’s web server works pretty well. For a large user base deployment you might want to choose to use IIS because it’s more scalable. IIS also gives you more security options.

-- Security Integration --

Security is always a big issue in an enterprise. Typically security includes authentication, which is about making sure a user is who he/she claims to be, and authorization, which is about letting the user see only what he/she is allowed to see. In the real world, we often see QlikView Publisher and Section Access can handle authorization pretty well, while the authentication is a bit more complex. This is because QlikView does not do authentication itself, it always relies on third-party authentication like NTLM, SiteMinder, WebSeal, etc. This process is also known as Single-Sign-On (SSO). This normally plays well in an enterprise because usually there is already a standard authentication product in place. The good news is, if the existing standard authentication product happens to be NTLM/Active Directory, QlikView can work with it out-of-box with no additional configuration. Otherwise, the third-party authentication product needs to inject the user id into http header and QlikView needs to be configured to read user id from http header. If the QlikView Servers are also accessed by outside people, it might be a good idea to setup a reverse proxy.

I hope by now you get a sense of the extra “behind the scenes” efforts that are necessary to make your QlikView system successful. In my follow up blog, I am going to talk more on topics such as high availability, storage, and running load tests.

PART 2
---------
In my last “QlikView Enterprise Deployment” article, I discussed VMware, the benefits of separating Publisher from QlikView Server, the choice of QlikView web server vs IIS, and security. However, there is more to consider in making your system solid.

-- High Availability --

The QlikView deployment has been so successful, people cannot live without it anymore. All of a sudden IT’s are victims of their own success. People are demanding high availability and high performance of the QlikView system, which of course will make the system more complicated. QlikView Servers need to be put on more than one machine, and a load balancer needs to be put in front of these machines. QlikView Servers also need to be clustered. By doing this, if one server is down the load balancer will stop sending users to this server. Users also enjoy a better response time because they are spread across multiple QlikView Servers.

The same concept also applies to Publisher. I have seen customers trying to get many dashboards refreshed (e.g., month-end or quarter-end) in a short timeframe. It might be a good idea to also install Publisher on multiple machines and cluster them. If one Publisher goes down, QMC will wait for it to be back to normal before sending data refreshing tasks to it again. In the meantime, QMC keeps sending tasks to the good Publishers and nothing gets interrupted.

-- Storage --

A lot of QlikView Servers objects (sessions, shared objects, bookmarks, licensing information, etc.) are stored in a set of system files. When QlikView Servers are clustered, both servers read and write from the same set of system files, which can cause contentions. Some people would use one of the QlikView server’s hard disk as the storage for these system files. This is normally fine except that when that server is down, the good servers cannot work either because the storage location is not there anymore. The best configuration we have seen is to use a SAN owned by a third windows server as the storage, and that windows server can be a VM.

-- Load Tests --

Every component of your QlikView system is properly configured and it looks like it’s ready to go. But wait, how can it be sure the system can support the desired user load and data volume? The only way to find out is to run load tests. QlikTech offers a great tool that is based on JMeter and it is relatively easy to setup. The tool can automatically generate JMeter scripts based on specified testing scenarios, and it can simulate any number of concurrent users. The testing results can be loaded into QlikView for analyzing. Of course, if the company has a strong load testing team that uses other tools like LoadRunner, you can also use your own tool to perform a load test.

These are the most common things people consider in an enterprise deployment. I hope you enjoyed reading it as much as I enjoyed writing it.

Qlikview is one of the older names in Business Intelligence software since it’s been around since 1993. It’s known as being particularly easy to learn, which is important for quickly training employees and getting them up to speed.

Business intelligence tools are applications that deal with Business Objects and that help with analysing and presenting data. For the most part, a BI tool will be working with data that’s already been in-putted into a system, and you’ll simply be using the BI application to work with that particular data set, though there are exceptions. The best business intelligence software for you though will depend on what you need, since there are many pros and cons of various BI programs.

-- Cons --

Qlikview has strong features all around, but there are other clients that tend to be somewhat better when it comes to certain features. For example, Tableau actually has a free reader integrated into it, which makes offline viewing considerably easier than the limited viewing capabilities while offline that Qlikview has.

Qlikview also struggles when it comes to integrating GIS data, which can be pretty important for topographic and geographic analysis and presentation. Other programs having mapping abilities integrated into the client, for example. Qlikview also struggles when it comes to multidimensional support, and support for things like xVelocity or Power Pivot.

While Qlikview excels in ease of use, there are many alternatives out there like Tableau and OLAP that tend to be better at analysing data in a deep and thorough way, and with support for all of the other applications and data sets that you may need.

-- Qlikview Pros --

An advantage of Qlikview is that it takes a very small amount of time to implement. It’s even better at this than other similar software such as Tableau. Another advantage that Qlikview has is that it has a significantly larger Partner Network than many of the alternatives.

Additionally, Qlikview has development scripting that tends to be superior as well. The 64-bit in-memory of Qlikview is among the best of any software BI package period. Qlikview has good interactivity with the UI, solid visual controls, and extensive compatibility with both web clients and especially with mobile clients. Qlikview also has considerably more mature features when it comes to data interactivity and visual drilldown as well. It’s easier to deal with the visualization aspect of the program than almost any of the competitors, including Tableau.

The best feature for Qlikview tends to be the visual drill down which it just does better than any other client. You can hardly go wrong with all of the extras Qlikview like MDI support, as well. The software shines when it comes to ease of use and learning curve. If you need to implement a BI solution fast and without hassle, Qlikview is often the best way to go.

Disclosure: I work for a company that is a partner with QlikView, SAP BusinessObjects and Microsoft.

As a non-Apple using professional (we are becoming less in numbers) I have always leaned further to the Android side of the mobile world. As a QlikView professional, most of my experience is on Windows desktops, laptops and servers and in previous years involved less interaction with what many people believe to be the greatest gadget(s) in the world.

So enter the iPad and QlikView V11.0.11426.0 SR2. Day one, the first step was simple, get to the QlikView Access Point. Open the browser, navigate to my access point and sign in. Outside of the search for the “\” key (domain\userid) that all went well.

The first question you are presented with after getting to the access point is would you like your default in full browser mode or small device mode. iPad is full browser. No question. I’m not a big fan of the small device mode unless the application was really made for phone use. The full browser mode gives you the full experience but beware: if the application was not developed for a smaller device, selection and navigation can become difficult. If you want your users to spend their time using the application, rather than zoom in, selecting, zoom out…repeat, follow some simple design rules from QlikView site:

- It is recommended that QlikView applications are designed for 980 x 590 with a tab row, and 980 x 610 without a tab row. This is a rule of thumb and depends on many things including the version of iPad your audience is using. I found myself struggling to keep the application down to this limit and expanded it slightly after thorough testing in a “no-tab” application.
- Use Arial or other font faces that are supported in iPad browser. I got lucky because my client gave me two options for font based on their creative team, one of which was supported.
- Font sizes – minimum 11pt. Good for most users. Someone with large hands will still probably struggle a bit selecting a specific line item but they probably struggle with most touch screen applications. I did cut this down to 9 and 10 pt sizes for informational only text areas that were non selectable.
- No Mouse Over Options – No mouse, not an option.
- There are some additional tips that I recommend you review but ultimately just keep in mind what you are designing for.

So now I am having enough fun with this that I really want to start testing out existing applications, some designed for mobile and some not. Unfortunately my lack of attention span kicked in and I was diverted over to the Apple Store to discover QlikView for iOS.

I had the chance to get to Tableau Customer Conference in early November 2012 and thanks to exceptionally good organization of the event I was able to greatly enhance my picture of Tableau (which I first reviewed 2 years ago) and get answers to some questions.

Below are my impressions from Tableau (which I haven't used in real projects yet) in comparison with QlikView -- tool I've been working with since 2009.

First thing I'd like to tell -- starting from version 8 Tableau can honestly be considered a truly mature product -- a big difference with what I saw two years ago. It's a smartly designed, feature-full and powerful analytic tool which is especially good for ad hoc query and analysis (Q&A). Prior to Tableau I considered BusinessObjects WebIntelligence to be the best Q&A tool on the market. However, in my picture of BI world this honorable title now belongs to Tableau.

Here is what I liked (not in order of importance):

- State-of-art data visualization makes Tableau outstanding in the crowd of BI suites. Tableau people talk about "being creative with data" and it's easy to believe in this while looking at clean and elegant Tableau dashboards. By the way, in French tableau has two meanings -- painting and table. Artwork and data. Excellent match of brand and product concept.

- Drag-n-drop authoring as cornerstone of analysis and design processes. That's what WebIntelligence was good at, but Tableau makes it even better, simpler and easier. Sadly QlikView has almost nothing to offer here -- fields still...

Read the rest of the post at http://bi-review.blogspot.co.il/2012/11/impressions-from-tableau-in-comparison.html

When is the best time to implement Business Intelligence?

Many of our clients still operate with outdated ERP legacy systems. The common complaint we hear is “I cannot get access to the information that is stored in my ERP system!”

Most commonly, issues are due to the fact that when these systems were built, paper-based reporting was still dominant. That is not the case anymore.

--A New Approach to Reporting--
There are ways to solve data access and reporting issues today without having to go through a costly conversion to a new ERP system.

Today a number of new software products are available that are relatively easy to deploy. These tools can put the power if information in the hands of users.

-- QlikView --
We recently reviewed one such product from QlikView. This Business Intelligence (BI) vendor got its start in Sweden in 1993. Today they have over 27,000 customers worldwide.

Our client still uses a legacy system they implemented 20 years ago and struggles to manage the business with poor information. The information they access often takes hours to assemble.

This BI product easily attaches to the client’s various data sources: the old legacy data files, Excel files, Access files and more. The data files can be linked. The user, through a series of wizards, can easily construct displays of the data.

-- A Cube of Data --
What we saw during the system review was the access of a “cube” of data. The system organizes the cube by dimensions and the user can “slice and dice” the information by the various dimensions: dates ranges, customers, products, territories and more.

In this demonstration we viewed a dashboard that showed tabs across the top:

- This year YTD compared to last year YTD
- KPI’s over time
- P&L
- Cash Flow
- Budgets
- Trends

The user could click to the tab, and then select the dimensions they wanted to look at.

The user can add notes to the dashboard for other users to view. Also, the user can share a view of the dashboard to other members of the team at no addition license cost. This increased insight aids in overall business process improvement.

-- Unlocking Data --
Over the years, our independent ERP consultants have found BI to be an effective route to unlocking information. By getting information into the hands of the users, companies achieve benefits that can then be used to fund the transformation to modern ERP. The BI system you deploy today can ease your transition to modern ERP implementation and is compatible with your data today and your data tomorrow.

Growing up in the 80′s and 90′s, one of my favorite TV shows was the A-Team. Over-the-top, cartoonish action with huge explosions, cars flipping over in mid-air topped off with a cool theme song. And all without anyone getting seriously hurt. This was the perfect TV show for young Barry!

But I’ve grown up since, and my tastes have matured (somewhat). However, there is one thing about the A-Team which I think is still relevant today: the actual A-Team and the well-balanced blend of skills of its members. No matter what an episode’s villain (drug king-pin/shady land developer/corrupt senator/whatever) threw at them, the combined qualities of the A-Team always ensured that they came out on top.

In today’s post, I am going to take a closer look at the skills and qualities of the A-Team, and will explain how they can be translated to the role of a QlikView Consultant. (Or, alternatively, how these roles can be used to staff the perfect QlikView Competency Center.)

-- B.A.: Technical genius and a pragmatic attitude --
Let’s start with the character every kid in my class wanted to be: Bosco “B.A.” Baracus. Forget about the kick-ass hand to hand combat skills and bad temper, as a QlikView Consultant, it’s B.A.’s technical genius that you’ll want to emulate.

Invariably, the A-Team will get pinned down somewhere (usually a barn) by the episode’s bad guys. What follows is a 5 minute montage in which B.A. welds together an entire armored vehicle out of scrap metal. In the next scene, we see the A-Team using this vehicle and some make-shift weapons to defeat the villains. (Who, for some reason, never see this coming, despite the A-Team using the exact same tactic in every single episode)

For a QlikView Consultant, the takeaway is that you should strive to continually improve your technical skills. Besides that, when the situation calls for it, you need to be able to keep your head down and do the work. Doing the work is a lot easier when you have the right tools, in this case not an acetylene torch, but a toolbox of scripts and solutions (either your own, or a third party one such as QlikView Components or QlikView Addict’s Codebox) that you can use to quickly build a solution in a modular, maintainable manner.

-- Murdock: Analytical skills and general knowledge --
Don’t let the goofball impression of H.M. “Howling Mad” Murdock fool you. While he may seem to not be all there, he is in fact a deep and analytical thinker.

Every episode sees Murdock obsessing over a new subject, historical character or object. This greatly annoys B.A., who refers to Murdock as a ‘crazy fool’. (in reality, even though B.A. will never admit it, they’re the best of friends) Despite his strange behavior, throughout the series, it becomes clear that Murdock is an analytical thinker, has a broad general knowledge and is very aware of current events and trends in the world. More than once do his brilliant, out-of-the-box ideas save the team.

While as a QlikView Consultant you’ll probably want to avoid the “raving madman” association, in my opinion, you do need to possess some of Murdock’s analytical and out-of-the-box thinking skills. Not only to apply them to your client’s projects, but also to periodically apply them to your own way of working. There are always ways in which you can improve.
Besides purely analytical skills, you also need to have a broad general knowledge of business processes and functions, as well as general market trends. Technical proficiency may be mandatory to get the job done, but real value is added when you understand the client’s business and market, and because of this, his/her problems and needs. There’s nothing wrong with ‘obsessing’ a little over a new field of knowledge if it helps you become more effective and efficient.

Combining the skills and knowledge of BA and Murdock leads to a T-shaped profile that I believe comes very close to the ideal profile for a QlikView Consultant; a deep, technical understanding of QlikView and peripheral methods, technologies and skills, combined with sound analytical skills, business knowledge and a broad general knowledge. As your experience grows, both the base and the roof of the T become broader and deeper, adding extra value for your clients and making you a more all-round professional.

Of course, we still have two more characters left, and as we’ll see, their skills and knowledge are just as important.

-- Face: Communication skills and persuasion --
Templeton “Faceman” Peck is the A-Team’s suave and smooth-talking con man and womanizer. He is always able to procure whatever supplies the team needs to get the job done.

The superiority of Face’s ability to convince others is demonstrated by the fact that he is able to break Murdock out of the same military hospital in almost every episode. Even after hundreds of successful escapes, each time using the exact same approach, he is still able to convince people that they should let Murdock leave with him. That’s an impressive display of persuasion, rivaled only by the Jedi mind trick.

Of course, womanizing and duping people aren’t really things you should be doing in a professional environment. However, as a QlikView Consultant, you will want to take at least a few pages from Face’s book. You can have best the best technical and analytical skills in the world, they’re useless if you cannot clearly communicate your ideas and are able to rally people around your cause.

Whether it be gathering requirements, getting access to various resources, designing interfaces, presenting your business case or just plain office politics (unfortunately a reality in many organizations), having excellent verbal and written communication skills and being able to present a convincing argument will greatly increase your effectiveness as a consultant.

-- Hannibal: Project management and leadership --
John “Hannibal” Smith is the leader of the A-Team. He is a master tactician, planning for every contingency and always ensuring that “the plan comes together”. His leadership ensures that the team is directed towards the common goal.

He also likes to wear very bad disguises, but nobody’s perfect.

One of the reasons for Hannibal’s continued success is the formulaic approach he takes to his projects. Every episode of the A-Team roughly plays out the same:

Bad guys harass innocent victims → Victims hire A-Team → B.A. says he won’t go on no plane → B.A. gets drugged and is put on the plane → A-Team confronts villains about their dastardly deeds and urges them to stop → Bad guys ignore the advise, take the A-Team by surprise and lock them up → A-Team builds weapons from scrap metal, escapes and beats up the bad guys in a fist fight → Villains go to jail → Credits roll.

You may find a lot of faults in Hannibal’s plan (I certainly see a few) but at least he is following some sort of methodology and he consistently delivers within the agreed-upon 60 minute timeframe. As a QlikView Consultant, you should also be following a consistent methodology to deliver your projects. I prefer to use Scrum, but any method will do, as long as it follows a predictable and consistent process that results in quality output delivered in a timely manner, with the end result meeting the client’s expectations.

Besides Hannibal’s project management skills, the most important takeaway for the QlikView Consultant is his leadership and focus on the end-result. Hannibal is really the one who brings the plan together, by keeping the team together. Without Hannibal, the individual qualities of the A-Team’s member would become unproductive; impulsive action (B.A.), paralysis by analysis (Murdock) and cheap talk (Face). Hannibal ensures that the team maintains just the proper blend of skills and qualities to get the job done, every time.

-- I love it when a plan comes together --
And that’s how I think the skills of the individual A-Team members relate to those of an ideal QlikView Consultant. Unfortunately, like the A-Team, consultants that actually meet this ideal combination of skills and traits are very hard to find. Often one specific ‘personality’ will be more present than others. As a consultant, once you’re aware of this, you can work on developing the other qualities. The Magic A-Team Quadrant (shown below) can be a very useful tool to assess yourself, or your team.

[To see the diagram go to: http://www.qlikfix.com/2013/03/26/what-qlikview-consultants-can-learn-from-the-a-team/]

Besides the ‘All-round QlikView Consultant’, the obvious hero of this story, I’ve added two profiles that I often encounter:

- The IT Consultant: has great technical skills, but has problems understanding the business context of what they are doing. Often delivers exactly what the client asked for, but not what they need. Applications tend not to be used after they leave.
- The Business Analyst/Management Consultant: knows exactly what the client needs, but has problems delivering a technically sound solution. Applications tend to fall over after they leave.

Where are you? And where are you going? Would be very interested to hear about your thoughts in the comments.

PS. Should you be based in the Netherlands and either feel that you already meet the ideal profile, or aspire to attain it; I’m hiring. Drop me a line and let’s chat. And no, unfortunately there is no company van :)

Yesterday, I had a very nice meeting with the folks at Qlikview (thanks, @DHurd11 & Andy for making the trip). They partnered with a local DC consulting firm by the name of Tandem Conglomerate. I had the pleasure of working with Ben Nah from Tandem Conglomerate last year – and I can vouch that their talent is top-notch. Qlikview is smart to find partners of this caliber – and utilize them to better serve their customers.

As a technologist, I always have my eyes open to exploring new technology. This is always challenging with long term contracts, university politics, and an ever-changing IT landscape. However, for me, vendors have to prove why they should remain at the top. Competition is healthy for everyone as it makes us constantly improve. I should also say that as long as we have a defined data model, the reporting tools that we use on top of that data model are fluid. The point is not to constantly change and rip out what you’ve done just for the sake of redoing it, but it is important to keep an eye on the latest technology, experiment, and find what is best for your organization. This can be done gradually with small pilot projects to prove value. We’re actually in the process of doing one of these pilot projects with Hadoop.

Ok – so you’re probably wondering why I titled this post ‘real-time data collaboration’? During the Qlikview presentation yesterday, I saw something that really resonated with me. And, that was the ability to collaborate, in real-time, on the same Qlikview dashboard.

This capability is a market differentiator for Qlikview. As many of you may have seen from Gartner and in my previous post regarding Gartner’s Magic Quadrant for BI, this is one of the reasons that Qlikview remains ahead of competitors such as Tableau. Other dashboard vendors may provide the ability to ‘share’ with others, or embed the dashboard into a web page or part. Don’t misunderstand. This is NOT the same.

During their product demonstration, Qlikview demonstrated the ability in real-time to share dashboards. This means that you can select the filters/parameters that you would like to analyze, hone in on the particular area of interest, and share it in real-time. The recipient can then see that selection, modify it, and as they modify the shared dashboard, it will update your dashboard. You can modify and send changes back to the recipient as well. VERY COOL! Kudos to Qlikview on this feature.