Public and internal sites best practice
Just wondering what the best practice recommendations are for Essentials when publishing both public and internal sites? Is it better to have one install of Essentials on the public web server for public sites and a separate install on the internal web server for internal sites rather than having both installs on the same server? My feeling is that separate public and internal Geocortex REST endpoints on separate servers would be a good thing, security wise and also in the case that one needs scale up one environment and not the other. I had previously seen some threads on this topic but I can't seem to find them anymore.
Thanks,
Aron
0
-
Aron, I have the same questions and notions, and am frustrated by the lack of documentation for best practices. I see it's been over a year, were you ever able to get some guidance? What configuration did you settle on?
Thanks0 -
I agree it would be nice to have some best practices, but maybe we could figure those out as a community. As a mid-size city government, we use a single virtual server to run our web GIS. There's definitely room for improvement, but this setup is meeting our current needs. We have about 150 internal users accessing our app in and out of our network and a resident population of about 80,000.
Virtual Windows 2012 R2 Server
- 4 cores
- 16 Gb of RAM (usually around 80% consumed)
- 100 Gb storage (60% full)
ArcGIS for Server Standard Enterprise 10.3.1
- Web Adaptor using IIS
- 38 published sevices (map, feature, cached and dynamic image, geocode, and geometry)
- Public and internal use
- AGS user and role security applied to service folders
Geocortex Essentials 4.4
- 1 live instance and 1 test instance
- 16 sites, both public and internal
- Windows integrated security for city staff
- Geocortex security for third party users0 -
Curious if anyone has been able to make progress on this? We're in the same situation. 0 -
Our setup has been solidly stable in the eight months since my last post on this topic, though I am requesting an additional 4-8 GB or RAM to support our growing collection of map services. 0
Please sign in to leave a comment.
Comments
4 comments