ArcGIS Server Server Architecture Publishing Scenarios Caching Published Services Streaming Published Services ArcGIS Online (AGO) Server and Web Architecture H-GAC AGO Basics AGO Web Maps and Web Apps Empowering the Non-GIS User Questions and Helpful Links
13 county service area Works with local governments to address needs of region H-GAC Program Areas: Transportation Planning Community/Urban Planning Environmental Planning Socio-Economic Modeling Area Agency On Aging Cooperative Purchasing Workforce Solutions GIS Services/9-1-1 GIS Services
Server (Staging) 4-Cores N A S Internal Network ARCGIS SERVER ARCHITECTURE Two ArcGIS Server system 4 Core ArcGIS Server (Staging) 8 Core ArcGIS Server (Production) Authorized Data Stores Server Data Folder Department SDEs Local disk storage on both servers for data overflow Separate storage for cached services
Data source is from a department SDE Publish using ArcCatalog Publisher connection Department SDEs setup as valid data stores (no data copied to server system directory) Publishing a service with FGDB data Data source is from a FGDB loaded to server data folder Publish using ArcCatalog Publisher connection Server data folders are setup as valid data stores (no data copied to server system directory) These scenarios can be used on both Production and Staging servers only by authorized publishers at H-GAC Department GIS leads are given a publisher account to both servers
for caching Both servers use separate cache folders to store caches; ArcGIS Server does not support shared cache folders from separate sites Currently have close to 2TB of storage for cache folders; can expand Can build a cache on staging server, then release onto production server (e.g. QA/QC workflow) Staging Server Production Server Build Cache Export Cache Publish Import Cache
to stream published services directly into desktop GIS Publicly streamed services require no login or approved credentials to access Securely streamed services (H-GAC Aerial Imagery, STAR*Map, etc.) requires users to submit a request form for access Services can also be consumed by web-based GIS applications using service URLs located in our REST Directory (https://gis.h- gac.com/arcgis/rest/services) Detailed instructions found on our website (http://www.h-gac.com/rds/gis-data/gis-rest- directory-services.aspx)
Server (Staging) 4-Cores N A S Internal Network ARCGIS SERVER ARCHITECTURE WITH ARCGIS ONLINE (AGO) ArcGIS Online Web Server/ Web Adaptor DMZ https://h-gac.maps.arcgis.com REST Service REST Service
Shared with Group- Members of group can view H-GAC- All H-GAC affiliated users can view Public- All can view, even visitors without a login Groups We can create broad groups (departments) or specific groups (projects) The Featured Content group displays items shared on the homepage as a showcase gallery Our H-GAC AGO site is not federated with either ArcGIS Server, therefore service REST URLs cataloged in AGO do not consume credits
published service REST URLs as catalog entries in AGO; they then become content (mostly web layers) in AGO Web Layers Web Maps Web Apps Web App templates are easy to use and easy to understand http://h-gac.maps.arcgis.com/home/index.html Web Map Web App
GIS experience) can learn and use AGO with ease Users can create their own mash up web maps with various web layers than can become web apps from templates Apps are deployable on most major mobile devices and morph to specific device skin Empowers the non- traditional GIS users and frees up time spent on paper map requests