topic Re: Qlik Sense Enterprise Document Analyzer - Connector in App Development

Qlik Sense Enterprise Document Analyzer - Connector

greg-anderson — Sat, 16 Nov 2024 18:13:17 GMT

I am managing a new QSE for Windows instance, running on AWS

I installed the QS Document Analyzer (1.7) on the server per instructions.

I am trying to create the data connector and getting a WebSocketConnector error message / HTTP 500.

This URL directs to our default virtual proxy, which uses Windows authentication.

I thought it might be related to firewall rules, but I see no blocked traffic. Turned off the server firewall briefly, same result.

Has anyone else seen this? I have a few apps that really need tuning/trimming.

Hi @rwunderlich, sorry to bug you personally. Been trying to diagnose this connection issue. Any thoughts?

Thanks!

Re: Qlik Sense Enterprise Document Analyzer - Connector

AnjaliRai — Thu, 27 Aug 2020 07:28:34 GMT

Hi @greg-anderson ,

While creating the QS App Metadata connection , under Hostname, you need to give your Central server details (itseelm-ntservername.com) and then try connecting.
For me, this works perfectly fine.

Hope you find this useful.

--Anjali

Re: Qlik Sense Enterprise Document Analyzer - Connector

greg-anderson — Tue, 01 Sep 2020 21:37:17 GMT

Hi, Anjali.

Thank you for the reply.

I am putting my fully-qualified Central server name in the Host box. Still no luck.

Re: Qlik Sense Enterprise Document Analyzer - Connector

rwunderlich — Fri, 11 Sep 2020 16:28:19 GMT

There is a problem with connection to virtual proxies. Works for some, not for others. I have not been able to determine why. I've not spent any more time on it as I'm spending all my time on the next version which will change how the connections are made.

-Rob

Re: Qlik Sense Enterprise Document Analyzer - Connector

paulodantas — Thu, 08 Apr 2021 14:41:18 GMT

@greg-anderson what works for me is go to the data connection in QMC and change the string.

Like this:

CUSTOM CONNECT TO "provider=QsAppMetadataConnector.exe;server=CentralMachineName;environment=Enterprise;appid=IdApp;appname=AppName;"

Hope this work for you too.

Best regards.