ArcGIS Deployment Scenarios. Philip Heede, Jay Theodore

Transcription

1

2 ArcGIS Deployment Scenarios Philip Heede, Jay Theodore

3 Agenda Two main sections: - The GIS server - Moving to Web GIS for enterprises - Why? - Patterns - Some technical details

4 The GIS Services Server Web Services (Dissemination)

5 Create separate sites for separate purposes Don t try to do everything in one site: Your server site becomes much more deterministic and predictable when using it for one purpose. (or multiple purposes with similar patterns of usage and resource consumption..) Example of separate purposes: mission-critical, high-throughput GIS services vs. departmental GIS services published ad-hoc throughout the day

6 Create single cluster sites

7 Enable SSL/TLS for all your server sites If you make your ArcGIS Server sites public or plan on using a portal whether or Portal for ArcGIS Reason: SSL/TLS only sites will not be able to consume your services otherwise. Do yourself and everyone else consuming your services a favor and enable now. - Remember to get a properly signed certificate and install it.

8 Keep system architectures simple Keep system architectures as simple as they can be (but no simpler) Corollary: Do not use unnecessary components. E.g. the ArcGIS Web Adaptor is not a required component with the GIS server unless you need web tier authentication. If you have alternative reverse proxy and load balancing solution already in place feel free to use it. KISS principle

9 Many ways to deploy the GIS server Do not necessarily think that multi-machine sites are the only way to go. If you are an advanced IT organization, take a look at the Deployment scenarios topic in the ArcGIS 10.3 for Server documentation - advice there applies to x as well! Main takeaway: for deployments beyond the small 1-2 machine setup for a limited userbase, consider your needs carefully and do a system architecture design

10 Implement release management for service publishing Administrative operations can be expensive and should be done during off-peak or reserved time periods. In other words: - avoid publishing or modifying services during regular production use - implement release management processes to control administration and publishing

11 Desktop Web Device Web GIS Portal for Enterprises Server Online Content and Services

12 Apps Users Anonymous Access Desktop Web GIS Providing Mapping, Analysis, Data Management, and Collaboration

13 A World of Apps

14 Web GIS Deployment Patterns Apps portal GIS Servers Ready to use Content SaaS (portal) (Hosted Servers) Services Software Portal for ArcGIS ArcGIS Server ArcGIS Data Appliance

15 Web GIS Deployment Patterns portal GIS Servers Ready to use Content SaaS (portal) (Hosted Servers) Services Software Portal for ArcGIS ArcGIS Server ArcGIS Data Appliance

16 Web GIS Deployment Patterns portal GIS Servers Ready to use Content SaaS (portal) (Hosted Servers) Services Software Portal for ArcGIS ArcGIS Server ArcGIS Data Appliance

17 Web GIS Deployment Patterns portal GIS Servers Ready to use Content SaaS (portal) (Hosted Servers) Services Software Portal for ArcGIS ArcGIS Server ArcGIS Data Appliance

18 Web GIS Deployment Patterns portal GIS Servers Ready to use Content SaaS (portal) (Hosted Servers) Services Software Portal for ArcGIS ArcGIS Server ArcGIS Data Appliance

19 Deployment model responsibility ArcGIS for Server + Portal for ArcGIS and trust.arcgis.com

20 Web GIS for Enterprises Desktop Web Device Portal Enterprise Server w/oracle Hosted Server Online Content and Services Enterprise Server w/sql Server

21 Implementation Patterns Portal for ArcGIS + ArcGIS for Server Portal for ArcGIS Item A Item B Item C Registered web service Federated Server Hosted Server ArcGIS Server site 1 ArcGIS Server site 2 ArcGIS Server site 3 Identity Store Can be any version Must be same version as federated Portal! ArcGIS Data Store

22 Rate This Session ArcGIS Deployment Scenarios