Latest Contributions by AlessandroValra

This is sooooo goooood!!! Yeah, the real problem for many is getting the inital classified point cloud for a certain area, but hey, this is great anyway! Thanks for sharing. ... View more

ahoque-esristaff‌ Yes, I do! Interesting. How could I have it updating without the need to do so? I registered the data with the server not to publish the map service all the time I add/remove points and time attributes to my data. I don't get that "Has Live Data: true" option. Thanks ... View more

Thanks ppapadopoulosmarathondata-gr-esridist‌ for the feedback. Unfortunately, using GeoEvent Server is not a viable solution in my case, so I suppose I would put stream service apart. Also, before using the JS API ,I'd like to know if there's a way to do it with (let's say) the standard tools, like the procedure I described in my thread. Just to know if it is feasible, otherwise I think I would go for another way (like the second you described). ... View more

Hi and thanks for your suggestion. The problem seems to happen all the time I overwrite the mapservice. I didn't try to re-index the portal yet but it wouldn't be a solution if I have to do it all the time I udapte my mapservice, as it happens quite often. Also, deleting and publishing the service from scratch is not feasible as (as I said) I have to reconfigure plenty of popups for the many layers/sublayers I have all the time. Is there any other solution? Is this a known bug or am I just missing something? Thanks. ... View more

Thank you mcontreras-esristaff‌ for the workaround. ... View more

Version 2.1.1 still not fixed. But I guess with "next release" a major release is intended (e.g. not 2.1.0 to 2.1.1 as of now but 2.1 to 2.2?). ... View more

Thanks. It's not clear from the docs that it is a requirement. Seems more like it's something ArcGIS Monitor installs by itself. It should be clarified in the docs IMO. ... View more

or you can try changing the etc/hosts file which would effectively force Enterprise Builder to believe that the machine name is the alias thereby using the alias URLs in the setup of the components. This is interesting. Thanks both for this precious information. I think I will try this way or avoid using Builder in future. I think this is so important to include and highlight in the documentation before going crazy trying to figure out what can be done to fix the problems (= much more time spent for installing with an automated tool rather than doing it manually). ... View more

Just to clarify a bit. It is not the first time I am performing a ArcGIS Enterprise install. It is however the third time I am using the builder and failning in doing that. Generally, the customers ask for a simple install: one server machine, everything on it. They normally then want to access this server machine from client other machines to (e.g.) publish their gis servers with ArcMap or Pro. This is done most typically by adding a connection to the server machine with publisher credentials, or - with the advent of Portal for ArcGIS - by logging into their Portal. The problem is: in order to publish to the Server, they need to Share from ArcGIS Pro to Portal for ArcGIS a feature service (or whatever other type of service), having the ArcGIS Server federated with the Portal and being it also the hosting server for the GIS services. And so they need to LOG IN. Here comes the pain. Using the external address to access the portal (or the server) is fine as long as you don't have to log in. I remember during manual install that when the Portal site is created you can specify a URL, which for our customers is generally the external accessible domain. The builder seems to set this automatically to the FQDN of the server machine server itself, thus redirecting any attempt of login to this rather than the external domain. Am I totally wrong? Is there a way to access (LOG IN) the Portal or Server from outside after installing arcGIS Eneterprise with the builder? Please, I really hope someone would shed a light on this since searching the web I saw many geonet's "presumably answered" questions but no certainties. ... View more

Hi Jonathan Quinn‌. My scenario is probably the simplest one and the one which is supposed to suite the requirements of the Builder. Reasons why you would not use the ArcGIS Enterprise Builder are any of the following: Install the software components across multiple machines So I imagined that having "all the components" means "including Web Adaptor/s". However, in the very same bullet point I also read: Reasons why you would not use the ArcGIS Enterprise Builder are any of the following: (...) Define the name of the ArcGIS Web Adaptor (IIS) So, that's probably where my issues came from. The Web Adaptor installed with the builder automatically configures with the FQDN, which is not accessible from outside the LAN, which I think is a normal case (?). But my SSL certificate is working only for the external domain (which I also suppose is normal). The only way I could point the web adators to this external domain with the certificate is (as I said) by uninstalling them and reinstalling them by pointing to the external domain. Everything seemed fine except that Portal is still pointing to the FQDN when it comes to log in, thus preventing me to use my Enterprise components from outside (and thus I won't be able (e.g.) to publish services...). The web adaptor is essentially a reverse proxy, just simplified. If you do want everything on the machine that's exposed to the internet, you can try to set an etc/hosts entry on the machine so that the internal IP address is set to the external FQDN you want to use. That will tell the AEB to use that hostname for all components and URLs. Do you know if this is actually working? Can you please give more details on how to do it or a link maybe? Thanks in advance! ... View more

I found out what is the real method to have a fully working installation of the web adaptor. Basically, when you install and launch web adaptor, it opens upo in the browser with a URL like "http:\\localhost\arcgis\webadaptor". The protocol (HTTP) and web adaptor name (arcgis) might be different depending on what was specified during installation. If you want to access (e.g.) Portal for ArcGIS from an external machine, YOU HAVE to change the web adaptor URL in the browser to point to a domain which is accessible from outside, and that has a SSL certificate installed. So, if you already have configured it "the wrong way", you have to first unregister the webadaptor (Unregistering ArcGIS Web Adaptor with Portal for ArcGIS—Installation Guides (10.5) | ArcGIS Enterprise ). Then, UNINSTALL it, and reinstall it, changing the URL as I said. Then, once inside the configuration, just specify the external domain again and you'll see that everything will work just fine. If you don't change the URL in the browser as I said, it will finish configuring succesfully, you will be able to access the Portal for ArcGIS from outside the server machien wirth the external domain name, BUT as long as you try to log in, you won't be abkle to continue as this procedure will point to the server internal machine name (Fully Qualified Domain Name, or FQDN), which in most of the case is not accessible from a machine which is not the server itself. NOTE: if you (like me) install ArcGIS Enterprise using ArcGIS Enterprise Builder, it will automatically configure the web adaptors (one for portal, one for sever) with the FQDN. You have to do what I wrote in order to make it work correctly. Hope this will be of help. EDIT Apparently, this will somehow break ArcGIS Server login. If you press login in the /rest/services, it will stuck to a blank page, the URL being https://<YOUR_EXTERNAL_DOMAIN>/server/login/?returnUrl=https:/<YOUR_EXTERNAL_DOMAIN>/server/rest/services . Looking at the dev console, it seems to try to get stuck at this request: https://<FQDN>/portal/sharing/rest/portals/self?f=json&callback=dojo.io.script.jsonp_dojoIoScrip… So, again, the FQDN is back (don't know why??!!), and it's preventing ArcGIS Server REST (and MANAGER) from logging in from a machine that is not the server itself. SOLUTION go to your ArcGIS Server Administrator directory (https://gisserver.domain.com:6443/arcgis/admin). in security -> config and click on "update" (at the bottom of the page). change "Authentication tier" from ARCGIS_PORTAL to GIS_SERVER. click "Update". Now, the authentication should work. I don't know if this thing is working wether the server is federated/registered with the portal or not (still struggling to understand this). EDIT 2 Ok, so... I also had problems with federating/unfederating register/unregister the server with the Portal (which, as far as I know, is key if you want to be able to publish MapServices from ArcGIS Pro to ArcGIS Server passing through Portal). Maybe the key element is in this requirement, will come back to this if I'll find out. If you'll be federating your site with Portal for ArcGIS, it's recommended you configure your organization's domain name service (DNS) to include fully qualified domain name (FQDN) entries for each site you intend to federate with the portal. Portal for ArcGIS will request the FQDN of each site when you federate. ... View more