Architecture Best Practices for the ArcGIS Platform

Dave Wrazien, Solution Architect, Esri Andrew Hendrickson, Solution Architect, Esri

Session Topics

• Best Practices – People • Best Practices – Process • Best Practices – Technology

People Technology Process

Best Practice: People

How People Use the ArcGIS Platform Use Patterns as Framework

DATA MANAGEMENT

Collect, organize, and exchange data

ANALYSIS

Transform data into actionable

information

FIELD ENABLEMENT

Get information into and out of

the field

VISUALIZATION

Disseminate information

where and when it is needed

CONSTITUENT ENGAGEMENT

Get feedback and make

informed decisions

A Complete Integrated System

Identity Matters Too Many Individual Identities

My Corporate Identity

dwrazien@esri.com e-mail

1616 Time Card

dave.wrazien Cloud File Share

dwrazien CRM

Users

Bryce Harrison

Emily Mars

Jacob Ruiz

Jason Key

Jay Tomas

Jon Connor

Kelvin Hernandez

Identity in the ArcGIS Platform Connect Users to Apps

Esri Apps Partner Apps

Portal Portal for ArcGIS / ArcGIS Online

Server Server Server

Incorporating Identities in Your Apps Adding Code

Users

Bryce Harrison

Emily Mars

Jacob Ruiz

Jason Key

Jay Tomas

Jon Connor

Kelvin Hernandez

Java Script

WPF

Android

J

resources.arcgis.com

Name: Jon Connor

Title: Project Manager

Organization: Star Consulting Role: User

Defining Identities Configured by You— Based on Your Business

New Custom Roles

Standard Roles

Organizational Roles

User

Publisher

Administration

Analyst

Public

Viewer

Editor

…

Avery,Francis,Avery.Francis@star-con.com,User Ben,Bentz,Ben.Bentz@star-con.com,Analyst Brittney,Brown,Brittney.Wrazien@star-con.com,User Bryce,Harrison,Bryce.Harrison@star-con.com,Publisher Carter,Henritzy,Carter.Henritzy@star-con.com,User Christian,Beebe,Christian.Beebe@star-con.com,Publisher Emily,Strunk,Emily.Strunk@star-con.com,Analyst Emily,Mars,Emily.Mars@star-con.com,Publisher Jacob,Ruiz,Jacob.Ruiz@star-con.com,User Javon,Key,Javon.Key@star-con.com,User

Adding Identities to the Platform Small Organization Pattern

Users

Bryce Harrison

Emily Mars

Jacob Ruiz

Jason Key

Jay Tomas

Jon Connor

Kelvin Hernandez

Small Organizations

Import XLS / CSV

Adding Identities to the Platform Large Organization Pattern

Large Organizations

Users

Bryce Harrison

Emily Mars

Jacob Ruiz

Jason Key

Jay Tomas

Jon Connor

Kelvin Hernandez

SAML

Enterprise Identity Management System

Avery,Francis,Avery.Francis@star-con.com,User Ben,Bentz,Ben.Bentz@star-con.com,Analyst Brittney,Brown,Brittney.Wrazien@star-con.com,User Bryce,Harrison,Bryce.Harrison@star-con.com,Publisher Carter,Henritzy,Carter.Henritzy@star-con.com,User Christian,Beebe,Christian.Beebe@star-con.com,Publisher Emily,Strunk,Emily.Strunk@star-con.com,Analyst Emily,Mars,Emily.Mars@star-con.com,Publisher Jacob,Ruiz,Jacob.Ruiz@star-con.com,User Javon,Key,Javon.Key@star-con.com,User

Leverage Identity Many to One

Shared Identity

My Corporate Identity

dwrazien@esri.com e-mail

1616 Time Card

dave.wrazien Cloud File Share

dwrazien CRM

Leverage Identity One Shared by Many

Shared Identity

Esri Apps

Partner Apps

ArcGIS Community

Best Practice: Process

Approach/Process to Providing Solutions Maintain focus on the business!

1. Configure First 2. Customize Second 3. Create New Last

Implementation Process Rapid and Agile

• Understand / Engage Mission & Priorities • Understand Business Processes & SLAs

- Distill Processes - Define Services

• Construct Common Services • Develop Applications • Rapidly Prototype • Consider Other Technologies

- Bus & Orchestration Tools • Implement Standards

- WSDL, UDDI, REST, XML, SOAP,

Best Practice: Technology

Conceptual Reference Architecture

Development Environment

Web Clients 4

Browser ArcGIS forMobile5

ArcGIS forDesktop

Local Clients 7

ArcGIS forDesktop(Editor)

ArcGIS forDesktop(Admin)

ArcGIS forDesktop

(Analysis)

Other API Clients

ArcGIS EDNSubscribers6

Other API Clients

GeoData

WCS

WMS

WFS

KML

ImageAnalysis

Map

Locator

Globe

Geoprocessing

Network Analysis

Mobile

Geometry

Custom

Web Applications

GIS Portal

ArcGIS Online

Feature

Servers

GIS Visualization,Analysis and Field Mobility Servers

ArcGIS for Server

Publication GDB

GIS Cache Servers

ArcGIS for Server

Publication GDB

Cache

GIS Data Management Servers

ArcGIS for Server

Transactional GDB

Staging Environment

Web Clients 4

Browser ArcGIS forMobile5

ArcGIS forDesktop

Local Clients 7

ArcGIS forDesktop(Editor)

ArcGIS forDesktop(Admin)

ArcGIS forDesktop

(Analysis)

Other API Clients

Other API Clients

GeoData

WCS

WMS

WFS

KML

ImageAnalysis

Map

Locator

Globe

Geoprocessing

Network Analysis

Mobile

Geometry

Custom

Web Applications

GIS Portal

ArcGIS Online

Feature

GIS Data Management Servers 1

ArcGIS for Server

Transactional GDB

GIS Analysis Servers 1

ArcGIS for Server

Publication GDB

GIS Field Mobility Servers 1

ArcGIS for Server

Publication GDB

Cache

GIS Visualization Servers 1

ArcGIS for Server

Publication GDB

Cache

Servers 2

Production Environment

Web Clients 4

Browser ArcGIS forMobile5

ArcGIS forDesktop

Local Clients 7

ArcGIS forDesktop(Editor)

ArcGIS forDesktop(Admin)

ArcGIS forDesktop

(Analysis)

Other API Clients

Other API Clients

GeoData

WCS

WMS

WFS

KML

ImageAnalysis

Map

Locator

Globe

Geoprocessing

Network Analysis

Mobile

Geometry

Custom

Web Applications

GIS Portal

ArcGIS Online

Feature

GIS Data Management Servers 1

ArcGIS for Server

Transactional GDB

GIS Analysis Servers 1

ArcGIS for Server

Publication GDB

GIS Field Mobility Servers 1

ArcGIS for Server

Publication GDB

Cache

GIS Visualization Servers 1

ArcGIS for Server

Publication GDB

Cache

Servers 2

Applications

Web Services

GIS Application Server Components

Persistance Components

NOTES

1 GIS application servers should be configured for high availability.

2 Web servers should be load balanced and configured for high availability.

3 One-way GDB replication from Transactional GDB to Publication GDB. ETL from other databases may be necessary to enrich the Publication GDB. However in many cases, service level access to data sources will be consumed at the application level, foregoing the need for an ETL process at the data level.

4 Web Clients should discover content via GIS Portal and access found GIS Services (internal and external) via SOAP or REST.

5 ArcGIS Mobile clients enabled with editing tasks would access the transactional GDB.

6 ArcGIS EDN subscribers should maintain a local GDB for development purposes.

7 Local Clients should connect to the Transactional GDB via “Direct Connect”.

3

3

3

Development Environment Defined: a limited scale and scope environment sufficient for the development of primary code and data modeling.

- Supports developer creativity - Individual “build” environment - Promotes creative development of new applications

without the fear of impacting other systems.

Staging Environment Defined: a separate mirrored pre-production environment

- Allows insight into what may break with patching, software upgrades, & etc.

- Promotes use of a QC/QA environment - Supports performance testing - Ensures a stable, extensible, and high performing system

Pattern Segregation Defined: separate technology deployments by solution pattern

- Reduce risks - Improve service delivery - reduced system resource

contention

Typically SLAs will often determine which server deployments need to be

separated.

Data and Asset Management

Constituent Engagement

Publication Geodatabase Defined: a unique instance of a transactional geodatabase used to support the dissemination of geographic data, services and applications.

- improved performance - reduce data security risks - reduce system resource contention

Decouple contending usage patterns from a common enterprise

geodatabase.

Data and Asset Management

Operational Awareness

replication

Caching Environment Defined: separate server(s) to support map cache creation and maintenance.

- reduce system resource contention - support QA/QC of published map content

Cache Server(s)

Map Cache

Caching Environement

Summary

• Best Practices: People – Leverage Identity • Best Practices: Process - Rapid / Agile Development (configure before customize) • Best Practices: Technology - Use Conceptual Reference Architecture

Thank you Please Fill Out Session Survey!

Dave Wrazien Solution Architect, Esri dwrazien@esri.com