topic Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer in Integration, Extension & APIs

Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

rbartley — Fri, 23 Aug 2019 15:34:59 GMT

Hi everyone,

I am experiencing an issue with my Single Integration (Iframe) mashup that seems to be related to the "Websocket limit reached" issue identified in this post on the Qlik help site: https://help.qlik.com/en-US/sense-developer/June2019/Content/Sense_Helpsites/troubleshooting-developer-mashups.htm

My app has 8 sheets, which I originally linked to 8 iframes in the mashup, navigating between these by showing/hiding the iframe according to which tab was selected. Everything works well in all browsers except IE, which appears to show the first 6 iframes. So, given that the help page suggests that one websocket connection is used for each iframe, I re-worked the mashup so that only one iframe was used, but the src attribute of the iframe is updated to show the different sheets. However, the results have been inconsistent and the selections are not maintained (even when the same identity parameter value is used).

Does anyone have any experience of this and, if so, do you have a solution?

Thanks in advance.

Richard

Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

treysmithdev — Sat, 24 Aug 2019 15:45:30 GMT

I would use this scenario as another reason to save people from the horrors of IE.

Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

rbartley — Mon, 26 Aug 2019 07:45:26 GMT

Hi Trey,

Yes, as far as I'm concerned, I would simply advise users to choose a different browser, but that's a hard sell to the business as many are committed IE users.

If you do have any other suggestions, I'd appreciate it.

Regards,

Richard

Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

Øystein_Kolsrud — Mon, 26 Aug 2019 07:54:39 GMT

It's possible to configure Windows to allow for more websockets in IE, but it involves going into the registry, so it's often impractical (especially if you want to do a company wide configuration). You can find more information here if you are interested:

https://support.qlik.com/articles/000040520

Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

ErikWetterberg — Mon, 26 Aug 2019 08:02:44 GMT

Hi,

skipping the iframes and building a mashup instead is of course a possible solution, but I assume you don’t want to go that way.

A possible solution would be to use two iframes. Show the first sheet in one and when the user selects another sheet hide that Iframe and show the other one where you show the other sheets. The first one would keep the session open and preserve selections.

An alternative to this could be to use a separate iframe for the selection toolbar, but then the selection tool would be cut off.

I haven’t tried this, so it might not work at all.

Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

rbartley — Mon, 26 Aug 2019 14:14:14 GMT

Hi,

Thanks for replying, yes I have seen this on another post, but unfortunately this isn't practical in my case since the mahup will be open to users outside my organisation.

Regards,

Richard

Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

rbartley — Mon, 26 Aug 2019 14:16:30 GMT

Hi Erik,

Yes, using the Capability APIs would provide a solution, but we're looking to avoid this due to the development overheads. I had considered the two iframe model you proposed, but haven't investigated this yet. However, since you suggested it too, I'll give it a shot to see whether the selections are preserved.

Regards,

Richard

Re: Qlik Sense Mashup - Single Integration API - Iframes - Websockets limit in Internet Explorer

rbartley — Fri, 06 Sep 2019 14:42:32 GMT

I finally got round to trying this and it works. Thanks once again, Erik.

I will only use this in the case where there are more than 6 tabs and when viewed in IE since re-loading the second iframe leads to a delay in navigation when compared against show/hide, which is obviously not desirable.