What is the difference between AjaxZFC (Zero Footprint client) and internet Explorer plugin to access the QVW application ? What is the reason for using 2 types ?

[anil_y_86]

What is the difference between AjaxZFC (Zero Footprint client) and internet Explorer plugin to access the QVW application ?  What is the reason for using 2 types ?

[#2]

The Ajax client communicates with the QlikView Server via a web server (either the built-in QlikView Web Server or IIS). It does not require any client-side installation and works in any modern browser. All the heavy lifting is done on the QlikView Server, not the client. It lacks some of the features offered by the IE Plugin, e.g. macro support and better developer environment for server objects, but in turn the IE Plugin lacks some of the Ajax client's collaborative functionality.

The IE Plugin talks directly to the QlikView Server via the QlikView Protocol (QVP) on ports 4747 and 4774. The IE Plugin needs to be installed for each user and requires the use of Microsoft Internet Explorer. The IE Plugin is often faster than the Ajax client because it communicates directly with the QVS, but there are limitations. For example session collaboration is not available via the IE Plugin, extension objects do not work and mobile access is not possible (e.g. iPad).

Which one you choose to use depends on your requirements. I would say that most people currently implement the Ajax client.

QlikView is focussing mainly on HTML5. The future of IE Plugin support is unclear.

[#3]

Hi,

At a very simple level you need to have IE to use the Internet Explorer plug-in where AJAX will work on most browsers.

Realistically more browsers are not Microsoft and so you need to support that... and also you need and eye on the mobile market. I would expect as QlikTech you only want to do things once, you do not want to develop the same thing multiple times. AJAX provides a way for them to give the "same" experience to all users no matter their browser platform.

Where IE Plugin needs you to install the plug in the AJAX browser is a thin client, i.e. all you really need is a browser. The QV server does a lot of the work for you meaning the device viewing the QV document has nothing "extra" installed onto it (AKA no plugin). I think there is some arguments around what needs to be stored locally (in terms of temp files etc....) for either solution to run with AJAX being the better model but I feel you can argue around this very easily for both of the options.

Personally I would say that the IE Plugin provides a very slightly better looking document. From experience at some clients (where the network is not that great) I have found that IE Plugin will provide a quicker experience than AJAX.... but I am sure this is nothing that could not be overcome with a bit of support on the server to cover for the fact it is doing the work of many.

I am not sure what has been confirmed by QlikTech but I suspect that the AJAX will become the option of choice with the plugin being faded out. In theory AJAX will be deliver the same experience to all users no matter how they are viewing the document... again this goes back to the mobile market where more people will be using tablets\phones to view the data being provided.

The legacy reason for two types is in older versions of QV the AJAX option was quite poor so the IE Plugin version gave the user an experience like the developer would have from using QlikView desktop tool but in a web browser. AJAX has continued to improve over time and now gives something very close to the QlikView desktop look and feel.

Also for companies packaging and rolling out the plugin is a task where with AJAX nothing needs to be changed on the users workstation for them to view the QV documents.

I hope that all helps, I am sure that I have missed points and others will have their own views etc etc... but I was hoping to give a flavour of what is going on....

[anil_y_86]

Is there any difference between AJAX and AJAXZFC ?

I knew that AJAX means Asynchronous Java Script and XML then what is this ZFC ?

Can one of you explain about this ?

Regs,

Anil

[#5]

ZFC = Zero Footprint Client, meaning no installation of additional client applications are required

The official name of the browser-based QlikView client is the AJAX Zero Footprint Client, but some people simply say Ajax or Ajax Client

[Suus]

Hi Kai,

You talk about Internet Explorer Plugin needs to be installed for each user.

Can you explain how?

Regards, Suzan

[#7]

As mentioned the Internet Explorer Plugin is optional. Most people use the Ajax client, i.e. native access via a browser that does not require the installation of any additional software on the client machines or tablets/smartphones. Both browser clients (IE PLugin and Ajax) have pros and cons, as discussed in this thread. Most people opt for the Ajax client.

The Internet Explorer Plugin used to be a separate download but is now part of the QlikView Server installation. Note that of course the Internet Explorer Plugin only works if you have a QlikView Server as well. With QlikView Server v11.2 installed on a Windows Server 2012 box the IE plugin can be found here:

C:\Program Files\QlikView\Server\QlikViewClients\QlikViewPlugin

It is also possible to deploy it automatically company-wide with group policies using the MSI package. See Section 22 of the current QlikView Server Reference Manual.

[robert99]

Having used both at work (using 11.2)

We started using Ajax. I was concerned because the performance was so inferior to the client (that I demonstrated to management using a personal edition. Based on this they bought the small business edition)

Then we swapped to the plugin. It is much quicker, a better layout and a far superior print. The plugin gives a performance like the client on explorer.  Ajax was so poor that some staff (and I) did not want to use it. I just keep on using the PE.

Maybe it was partly the way it was set up. Or the type of apps etc. But hopefully QV do not drop the PlugIn until Ajax is as good as the plugin. In all respects. Not just close.

[MarcoWedel]

The performance of the Ajax client is heavily depending on the used browser Type.

E.g. on IE8 the Ajax client is significantly slower than on chrome of firefox, which come near to the Plug-in.

IE10 and 11 seem to be faster though.

regards

Marco

[robert99]

OK I have Firefox at home and IE8 at work

I'm getting a new computer soon hopefully with ie10 on it (I might get Firefox added to compare)