Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Community,
I am running QS and QGA on the same server. This server is offline - no connection to the Internet. Have QS and QGA enterprise licenses.
Installation guide states the following:
From Qlik Sense April 2018, the built-in Map chart can be used with GeoAnalytics Server in an on-premise solution. For this GeoAnalytics Data Package 18.04 or newer is needed. First, install the data package according the guide including the optional step named "Enable support for Qlik Sense Map" or similar. Then go to your Qlik Sense installation and point the Sense map to the server by editing the file mapconf.json in C:\Program Files\Qlik\Sense\Client\assets (or similar) and set the URL to the server in the serverUrl property and the key you have chosen during data package installation for Sense map users in serverKey. Example: { "serverUrl":"https://mysite.com", "serverKey":"abcdefg" }
Has anyone been able to successfully link the two? Server key is my QGA url? key is of QGA or QS? I can only use QGA in my environment. The standard map is not loading the background image until I actually first open a sheet that contains a QGA map.
Any help would be appreciated
Thank you!
For those interested I added the mapchartServices.xml data source source from the enterprise data package, enabled required services, created a new user+key, and added this key to the mapconf.json file.
QGA is in HTTP or HTTPS? if HTTPS, then note the following for the certificate: https://qliksupport.force.com/articles/000042100
If HTTP, then here is tricky, since Qlik Sense is connect via HTTPS, then you are in a secure channel connection, then connecting to QGA to HTTP is basically out going to unsecured channel which the browser won't allow. Read more here: https://qliksupport.force.com/articles/000037673
Any idea why the native QS map object does not show the basemap until the user first uses the QGA extension map object?
Kind regards,
Gysbeert
Not sure, never seen that behavior for some weird reason the initialization call to the QGA server doesn't fully execute correctly with the native map, with the extension it does and it keeps the session for that reason it work with the native map at that point. I would try switch the FQDM to localhost ( since both live on the host machine) and see if things works fine, if it does, then FQDN for some reason it goes to a network device that might be blocking the initial QGA request, I would use browser devtool>network and see if they any load failures . However, currently with the lastest QGA patch and i am not seeing that behavior, it actually work fine for me.
BR
Gio
I'm using HTTPS. I also installed the latest version of QGA.
I followed the suggestion I quoted from the user guide and when I placed my server under the url followed by my QGA license key i got two scenarios:
1) url without the port (https://server.abc.com) and my native QS map would load but not display the background and i would get a script error (e.g. https://server.abc.com/ravegeo/webmap5/...).
2) url with the port number (https://server.abc.com:4443) and my native QS map would not load at all. the object was blank/white but the script error from above is successfully executed. After a while i would get the following message displayed on my screen "Invalid visualization.. The visualization was not found on the server. This extension is not available: map"
This is quite frustrating. Any idea what I am doing wrong here?
@Gysbert_Wassenaar many thanks for forwarding the message
Regards,
Marko
Marko, then I would suggest to open a Qlik Support ticket, here can see what portion is missing to further assist you.
BR
Gio
Gio,
I did that already but not too happy with issue resolution
Marko
Can you share the case number, since I am not seeing you owning a case under your account?
BR
Gio
01509445
thanks
marko
For those interested I added the mapchartServices.xml data source source from the enterprise data package, enabled required services, created a new user+key, and added this key to the mapconf.json file.