21 Replies Latest reply: Nov 29, 2017 4:56 PM by Kris Markee RSS

    Extranet Server - Pros / Cons / Best practices?

    Stefan Wühl

      Dear all,


      I've  searched the forum for a while but couldn't really find much information about the extranet server. Does anybody have some experiences with this kind of QV server? At best, I would be interested in somekind of best practice regarding data source access and internal / external user access configuration.


      I understood so far that the extranet server could be run stand alone or in combination with an internal EE / SBE server. The extranet server will be located in the DMZ and is capable of only holding session or usage CALS. It is said the extranet server is based upon the EE server, but will only support up to 3 documents. I am not sure what "bases upon" is saying in this context, or what the exact limitations are.

      And, maybe more confusing, the pricing guidelines further say:


      "There will be a choice to use the AJAX client or a customized AJAX client via QlikView Workbench. QlikView Workbench is included in the Extranet Server"


      So there is no AJAX client support out of the box? The extranet server brochure available for download implies that there is support, but I am not sure.


      I assume one doesn't want to run the scripts in the DMZ, opening the firewall for data source access. So a standard setting would probably include a second EE or SBE server in the intranet which is doing the back end part and then the applications will be put on to the extranet server? Or does anybody have a  different approach here?

      Somebody told me that also the Publisher is needed  for communication between extranet and intranet QV server. Not sure why, though. Maybe he was just referring to the extranet server brochure, where an image may imply that. I usually regard these images more as simplifying marketing than correct technical information, but again, not sure.


      Are there any major CONs regarding using an extranet server in combination with an internal SBE? Or is there an absolutely convincing PRO for using a extranet server in combination with an internal EE?


      The limitation of 3 documents seems pretty hard to me, does anybode have some experiences here? I assume the license management would probably not allow to share user licenses across multiple extranet servers (which are needed for more than 3 documents), right?


      I appreciate any input, also with regard to allowing access to QV for external customers / partners in general.


      Best regards,


        • Re: Extranet Server - Pros / Cons / Best practices?
          Daniel Rozental

          Stefan, I don't have an extensive experience with this kind of server but a customer of ours recently purchased this server so I'll answer the things I can.


          - There is definitely an Ajax client.

          - You need another SBE or EE server or else you wouldn't be able to develop any applications as the Extranet Server doesn't allow named cals. This is more like a "add on", in my opinion, to an enterprise existing BI infrastructure, where they need to serve many users but for just a few applications.

          - I believe you can do reloads in any of the servers, if you have the same application in several servers it would make more sense to do one reload and then distribute it to different servers. I wouldn't "share" the same QVW between different servers unless they are in a cluster, or else I'm not exactly sure how the servers would resolve access to the shared and meta files.

          - You don't need publisher, you could just copy/ftp/etc. the file to the second server.

          - I'm not sure what you mean about sharing licenses between Extranet servers, kinda like a Cluster of Extranet Servers? not sure if that possible but sounds interesting, they would still only allow 3 documents though. I believe you can buy another Extranet Server license and just have one server serving 6 documents (You should probably check with your account manager).

          • Re: Extranet Server - Pros / Cons / Best practices?
            SRINIVAS sc



            Our requirement is to give access to reports for users escaping firewall. I found out QES might be helpful. As i see this is very old post, i believe you might have gained knowledge and experience using this. Can you please help me where to start like installation steps and those con's you mentioned are still valid or any documents explains in detail.


            Thank you for your time

              • Re: Extranet Server - Pros / Cons / Best practices?
                Stefan Wühl



                sorry to tell you that we finally haven't used the QES for that project at all, for one reason:


                Licensing. My customer intended to build some kind of service for his customers using the QES, which wasn't allowed by QT license terms. He would need to get an OEM license for that (I am telling here the status as of end of 2011, no idea if that's applicable to today's situation and / or license situation in another region).

                We initially got an information from our partner rep that the customers request should be possible using QES, so we unfortunately spent some time in investigating this approach.


                Regarding server installation, I think there is no explicite documentation for QES, it's a standard server installation, then QES feature set will be determined by license key.


                IMHO, the more important and delicate thing will be to setup the supporting IT infrastructure (firewalls, application transports (data access) etc.).




              • Re: Extranet Server - Pros / Cons / Best practices?
                Kris Markee

                I know this post is a bit old, but I stumbled across this while researching QES data and I wanted to add a comment describing a "con" of QES as it pertains to collaboration.  At this time if using QlikView 12 and NPrinting 17 with On Demand, we recently (early Oct 2017) uncovered and now have a case/bug open with Qlik regarding the fact that On Demand will not work in the QES environment, and here’s why. Behind the scenes, the On Demand control generates bookmarks so NPrinting knows what data to populate the report with but that bookmark cannot be accessed/used by NPrinting because QES doesn’t offer object collaboration.  Without that collaboration functionality, On Demand reports fail.  We are still waiting to hear from Qlik on their resolution to this bug, which we hope is soon as it is a bit disappointing that we paid for NPrinting but don’t have the full feature set since On Demand is basically broken, and for us is half the reason we got NPrinting in the first place.