Latest Contributions by RandallWilliams

Hi, Many organizations maintain more than one environment for the implementation of a given solution. These are often defined as: a. Test/Development - a sandbox type of environment where new functionality can be tested, apps built and rebuilt, prototyping and the like b. Staging - This is where user acceptance and load testing is performed. c. Production - this is the 'Live' site that's 'officially' used by clients. Prod is not to be touched prior to extensive testing. See: https://softwareengineering.stackexchange.com/questions/117945/staging-environment-vs-production-environment Some (well, many) organizations don't have the resources for more than one environment, but this also presents implementation risks. It's a lot less stressful to break a DEV environment than it is to break the PROD environment. With regard to this question: I wanna all the computers connected to my Intranet to be able to connect to the Server/Portal and create Apps with Admin role and use the WAB Dev edition, I am afraid that you mean that ONLY the computer on which we installed these stuff, is the only one where we can do everything we want ? This is not the case. Users of ArcGIS Enterprise won't be confined to using just this one machine, they'll be able to connect to it using a browser via the intranet. However, because the machine you're thinking of deploying the Enterprise GIS on is a bit underpowered, the performance these user experience will likely be less than desired - depending on how many users are working with it. If you elect to work with a multi-machine deployment, the performance impact will be lessened because you're distributing the components of ArcGIS Enterprise across two or more resources, which will lessen the resource impact on each machine. If you're RAM constrained but can spin up multiple machines, I'd highly recommend this route rather than a single underpowered machine. To summarize: It is POSSIBLE to deploy ArcGIS Enterprise on a single machine that has only 10GB memory. However, it is STRONGLY RECOMMENDED - especially under an environment under any kind of production load where users are expecting the system to be available and performant - to have a MINIMUM of 16 GB RAM. ... View more

16 gb RAM is the minimum recommended memory for a performant Web GIS in a production environment. You can install the all-in-one deployment on an underpowered machine, but be aware that users will likely find the performance to be unacceptable - especially under any kind of load. In terms of machine upgrades, RAM and HDD space are relatively inexpensive. I'd add more RAM, or if this is a VM, request that the VM admin bump up your allocation. ... View more

Hi Eric, Additional questions: How are these apps being built? Are you using the Resource Proxy (proxy page) to access this service? The service doesn't look to be a hosted feature service, and I can reach your service and view it in the JS API if I go directly to the service instead of going through the proxy page. The 500 error in your screenshot doesn't look like it's coming from the GIS Server to me, it looks like it's likely coming from a proxy page. ... View more

My guess is that you need to set the webContextUrl to reference the F5. That or the x-forwarded-host. Sounds like ArcGIS Server isn't matching the referrer, causing the token to be considered invalid. http://server.arcgis.com/en/server/latest/administer/windows/using-a-reverse-proxy-server-with-arcgis-server.htm ... View more

Hi Cassandra, I can appreciate the sentiment and provide a little context, for what it's worth. In order to use the nosniff option, certain values for content-type headers must be specified for nosniff to work properly (the content-type must be executable).  Esri was one of the first companies to adopt a RESTful approach, and many of the content-type values we should use were not available at that time. They were correct at the time we implemented our REST-ful approach, but are no longer correct for modern web browsers.  We are updating our code to use these values.  A challenge we face is that some of our clients and SDKs (.Net Runtime notably) look for the old content-type values. They are going to update their next versions.  Also, customers who have clients written in .Net may need to use an option we are putting in the software to go back to the old content-type values.  It is on our roadmap to move to nosniff at future release once we have all of our products using the modern content-type values.   ... View more

And actually, after re-reading the doc, looks like the limit for ports and the web adaptor is on the Portal for ArcGIS side rather than the ArcGIS Server side. Apologies for the confusion. ... View more

I do now. Given my test environment, I typically spin up a box of whatever flavor keep everything self contained. Now, I have a windows box with Server, Portal, and two web adaptors, and a Linux box with Tomcat 8.0.32 Server, Portal, and three web adaptors - two pointing at Server/Portal on this box, and the 3rd pointing to ArcGIS Server on Windows. Keep in mind that 'working' is a relative term, and is not the same as supported. We had to code around some pretty extensive changes in Tomcat in order to support newer versions in 10.6. At 10.6 we've certified Tomcat 7.0.72, 8.0.38, 8.5.6 and 8.5.20. See http://support.esri.com/bugs/nimbus/QlVHLTAwMDEwMjU0NA== for an example. ... View more

Hi, With 10.4.1, the highest supported version of Tomcat that will work/is supported is 8.0.32*. That's because after that, Tomcat made changes to how it manages special characters that breaks a lot of workflows. Web adaptor also needs to bind to ports 80/443. 8080 won't work. http://server.arcgis.com/en/web-adaptor/10.4/install/java-linux/install-arcgis-web-adaptor-portal.htm ... View more

You can publish the NEAR tool as a GP Tool. Portal for ArcGIS has the Find Nearest tool available OOTB. http://server.arcgis.com/en/portal/latest/use/find-nearest.htm I think the OOTB spatial analysis tools documented above were introduced at 10.4. ... View more

Here's a good discussion where Vince Angelo‌ helped to clarify: https://gis.stackexchange.com/questions/126373/difference-between-feature-server-and-map-server Besides editing, feature services also provide the option to dynamically set symbology for features at the client side. Map services essentially provide images pre-symbolized at the server side - either as pre-cached tiles or as dynamically generated images made from an exportmap request. Map services can be cached in order for data to render quickly. That's why basemaps are generally cached map services, while feature layers that render on top of basemaps can be either from a mapserver resource or a featureserver resource. ... View more

I think that the analyst may have misunderstood your question. You can still publish a web layer "by reference" with PRO.  You still need to register SQL Server with ArcGIS, just not as a "managed database" that data is copied into at publish time. When you go to share the map as a web layer, choose the option to 'reference registered data' instead of using the 'copy all data' option. This way all of your data still lives in SQL Server. ... View more

The only time I've seen this is when admins set the X-Content-Type-Options:nosniff header at the web tier. This option is supported post 10.6. ... View more

Does your certificate have a SAN (Subject Alternative Name) defined, is the certificate using SHA-1? Also, is this cert expired? I'm guessing you're using a the self signed certificate that's installed with ArcGIS Server by default, is that correct? Also, which version ArcGIS Server are you working with? ... View more