Documents related to Qlik GeoAnalytics.
Default folders and paths for different installation, can be changed during installation.
Qlik Sense Desktop
Extension folder: C:\Users\<user>\Documents\Qlik\Sense\Extensions\
Connector folder: C:\Program Files\Common Files\Qlik\Custom Data\QvIdevioConnector
Connector log: C:\ProgramData\QlikTech\Custom Data\IdevioGeoAnalyticsConnector\Log
Qlik Sense Server
Extension folder: C:\ProgramData\Qlik\Sense\Repository\Extensions\ (Shared persistance->under c:\QlikShare)
Extension folder: C:\Users\<user>\AppData\Local\QlikTech\QlikView\Extensions\Objects\
Connector folder: C:\Program Files\Common Files\QlikTech\Custom Data\QvIdevioConnector
Extension folder: C:\ProgramData\QlikTech\QlikViewServer\Extensions\Objects\
Since the Engine loads connectors (and DSNs) from local resources, it is important to install the GeoAnalytics connector to all nodes with an Engine service active or the GeoAnalytics Connector may not function properly.
Home: C:\Program Files\Common Files\QlikTech\Custom Data\QvIdevioConnector (QV) C:\Program Files\Common Files\Qlik\Custom Data\QvIdevioConnector (Sense)
Checks license at https://floatinglicenses.qlikcloud.com
Home: C:\ProgramData\Qlik GeoAnalytics Server\server3\
Logs: C:\ProgramData\Qlik GeoAnalytics Server\server3\logs.
Port 80 for http and port 443 for https, can be changed during installation.
The following urls are needed, QGA Extensions: https://maps.qlikcloud.com
License activation, ports 80 and 4747 to lef1|2|3.qliktech.com,
QGA Server can be activated without internet connection.
The QGA connector: https://ga.qlikcloud.com
QGA Plus: https://route.qlikcloud.com, https://geocode.qlikcloud.com, https://floatinglicenses.qlikcloud.com
Note! The connection for the extensions are from the client web browser to the map server. The connection from the QGA connector are from the Sense server (like all connectors) to the map server.
Hi, can someone explain when each of the 4 URL's is used when you have the GeoAnalytis plus license?
Ditto this question from Frank.
The Qlik GeoAnalytics Plus is minified version of the QGA server that can do all Geoanalytics operations except routing and location lookups. Same folder paths apply for QGA Plus. Installation documentation, also reachable from help.qlik.com:
ga.qlikcloud.com is used when location names (city, zip etc) are used in the GeoAnalytics operation. Local geometries (lat, long, points, lines, areas) in the app are passed without lookup.
route.qlikcloud.com is used for route operations: Closest, Routes, TravelAreas.
geocode.qlikcloud.com will be used when Qlik Geocoding is released, for street address lookups.
One more question, if we install Qlik GeoAnalytics Plus with a customer that does not allow us to have a connection to the internet, does the installation work, as long as we don't use:
geocode.qlikcloud.com will be used when Qlik Geocoding is released, for street address lookups
Thank you for your help.
Thanks a lot Patric. Another question here too: What are we accessing through maps.qlikcloud.com when using GA Plus? Is it just the background tile layer?
Yes, background map layers are fetched from maps.qlikcloud.com
Also lookups on the fly: city, country, zip etc <-> point or area, goes towards maps.qlikcloud.com in bubble, line, chart, heatmap or area layers.
Thanks a lot Patric!
I have a server with GeoAnalytics and other server with Qlik Sense that communicated between, when I dragged the map in app, I changed the server URL of https://maps.qlikcloud.com/ to //MyServerGeoAnalytics.com, but the map displayed "Invalid Key"
This problem presented when I upgrade the version of qlik sense server 3.2 to june
I have license of Geoanalytics
I have install Qlik Sense June
How to fix this problem?
Sounds like an installation issue, I would upgrade to the latest extensions.
Please make sure to use the same LEF key for the extensions as for the internal QGA server.
If it isn't clear, all your users or applications containing maps need access to the map server. So if you use an on-premise map server, and you have external users, you will need to open this through your firewall, use a public DNS entry and certificate, etc.