2018 tech transfer - arcgis enterprise - migrating...

January 8-12, 2018 | Redlands, CA

2018 ArcGIS Tech Transfer

ArcGIS Enterprise

Architecting Your Deployment

Ryan Sellman

Agenda

• Evolution of the Platform

- ArcGIS Server to ArcGIS Enterprise

• ArcGIS Enterprise Base Deployment

• Server Roles

• ArcGIS Server to ArcGIS Enterprise Migration Patterns

Starting at 10.5, ArcGIS Enterprise is the new name for the ArcGIS for Server product line.

ArcGIS Enterprise is comprised of 4 software components.

All of these components existed in the software pre-10.5

These 4 components configured together create what is called the base ArcGIS Enterprise deployment.

Not just a server anymore, it’s a complete Web GIS solution

Portal for ArcGIS

ArcGIS Server(hosting server)

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

Base Deployment Logical Architecture

Integrates with your organization’s existing

web server to provide a single endpoint that distributes incoming

requests and enables you to use web-tier authentication.

ArcGIS Web Adaptor

Base Deployment Logical Architecture

The software component that enables the ArcGIS Enterprise portal. Portal for ArcGIS is the web frontend and API backend that supports a user’s interaction and overall experience with your Web GIS.

Portal for ArcGIS

Base Deployment Logical Architecture

In a base deployment ArcGIS Server should be configured with a GIS Server licensing role and as the hosting server. In this capacity it gives you the ability to publish and share maps and layers from ArcGIS Pro using your own business databases and by copying data to the server.

ArcGIS Server

Base Deployment Logical Architecture

The ArcGIS managed data repository that stores the Portal’s hosted content. It is not a replacement for your enterprise geodatabases.

ArcGIS Data Store

Base Deployment Logical Architecture

• Relational• Tile Cache

(not part of base deployment:spatiotemporal big data store)

ArcGIS Data Store

Base Deployment Logical Architecture

New(er) Concepts | Federation

Portal for ArcGIS

ArcGIS Server(hosting server)

Federation

- Setting up a trust relationship between your ArcGIS Server site(s) and the Portal for ArcGIS software component.

- Security handled at the Portal level

- Manual federations of ArcGIS Server sites occurs in the portal: Organization tab-> Edit Settings->Servers

New(er) Concepts | Hosting Server

ArcGIS Server

Hosting Server

- Designation you give to one of your federated ArcGIS GIS Servers sites

- One hosting server per deployment

- Where all hosted content/services reside

- Can work on “double duty” and host traditional GIS capabilities

Demo

ArcGIS Enterprise Under the Hood

ArcGIS Enterprise | Server Roles (5)

• GIS Server

- Central GIS Server

- Can be designated as the hosting server

- Traditional map, GP & feature services

• Image Server

- Formerly known as Image Extension

• GeoAnalytics Server

- New at 10.5

• GeoEvent Server

- Formerly GeoEvent Extension

• Business Analyst Server

- Business Analyst capabilities in your own infrastructure

ArcGIS Server

ArcGIS Enterprise | Server Extensions – Pre 10.5

ArcGIS Server

Image Extension

GeoEvent Extension

Network Extension

ArcGIS Enterprise | Server Extensions – Pre 10.5

ArcGIS Server

Image Extension

Network Extension

8 Cores

8 Cores

Note: Hypothetical Deployment

ArcGIS Server4 Cores

4 Cores

4 Cores GeoEvent Extension

ArcGIS Enterprise | Server Roles – 10.5

GIS Server

Network Extension

Image Server GeoEvent Server GeoAnalytics Server

ArcGIS Enterprise | Server Roles – 10.5

GIS Server

Network Extension

Image Server GeoEvent Server GeoAnalytics Server

4 Cores 16 Cores8 Cores 8 Cores

Note: Hypothetical Deployment

ArcGIS Enterprise | Server Capacity

- Can add to Base Deployment

- For example, add:

- GIS Server - 4 cores (mapping)

- Makes sense from a system architecture standpoint

- Easier to implement Esri’s best practices

- Assign 1 server role to a server site

GIS Server

(mapping etc.)

GIS Server

(hosting)

Base deployment

Note: Hypothetical Deployment

ArcGIS Enterprise | Server Capacity

- Can add to Base Deployment

- For example, add:

- GIS Server - 4 cores (mapping)

- GIS Server - 4 cores (GP)

- Makes sense from a system architecture standpoint

- Easier to implement Esri’s best practices

- Assign 1 server role to a server site

GIS Server

(mapping etc.)

GIS Server

(hosting)

Base deployment

GIS Server

(geoprocessing)

Note: Hypothetical Deployment

ArcGIS Enterprise | Server Capacity

- Can add to Base Deployment

- For example, add:

- GIS Server - 4 cores (mapping)

- Image Server - 8 cores

- Makes sense from a system architecture standpoint

- Easier to implement Esri’s best practices

- Assign 1 server role to a server site

GIS Server

(mapping etc.)

GIS Server

(hosting)

Base deployment

Image Server

(dynamic image

services)

ArcGIS Enterprise | Functionality of the Base Deployment

- Everything from traditional ArcGIS Server

- Ability to publish map services, feature services, network services, geoprocessing services, geocoding services, and much more.

- Ability to publish content from referenced data sources such as file-based data (file geodatabases, shapefiles) as well as enterprise geodatabase and other spatially enabled databases.

- Give our users option to provide self-service mapping

- Publishing hosted data where users do not need access to enterprise geodatabase or trusted file shares.

- Can copy data to the system in a seamless fashion similar to the experience from ArcGIS Online.

ArcGIS Enterprise | Functionality of the Base Deployment

- Story maps and other configurable app templates

- Web AppBuilder for quickly creating customized web apps

- Full suite of Esri apps and other custom apps built on the ArcGIS API for Javascript and ArcGIS Runtime SDKs

- Take advantage of new capabilites of the platform

- Insights for ArcGIS

- Utility Network

Why Migrate to ArcGIS Enterprise?

• Latest innovations, enhancements, bug fixes, etc.

• Integrated with the ArcGIS Platform

- ArcGIS Pro

• Web GIS

- More than services and REST endpoints

- Apps

- Distributed collaboration

- Named users

• Advanced analytics

- GeoAnalytics

- Raster Analytics (Image Server)

How Do I Get there?

GIS Patterns

Standalone ArcGIS Server

Standalone ArcGIS Server

+Content/Services

from ArcGIS Online

Standalone ArcGIS Server

+ArcGIS Online

ArcGIS Enterprise

ArcGIS Enterprise

+Content/Services

from ArcGIS Online

ArcGIS Enterprise

+ArcGIS Online

ArcGIS Online

only

GIS Patterns

Standalone ArcGIS Server

ArcGIS Enterprise

ArcGIS Web Adaptor

ArcGIS Server

ArcGIS Server

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

(hosting server)

(Enterprise portal)

Portal for ArcGIS

3 Migration Options

ArcGIS Server

ArcGIS Web Adaptor

6080 & 6443

BEFORE –Typical standalone server deployment

Portal for ArcGIS

ArcGIS Server

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

(hosting server)

(Enterprise portal)7080 & 7443

6080 & 6443

AFTER –Base ArcGIS Enterprise

deployment (min.)

ArcGIS Server

ArcGIS Web Adaptor

6080 & 6443

BEFORE

Portal for ArcGIS

ArcGIS Server

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

(hosting server)

(Enterprise portal)7080 & 7443

6080 & 6443

AFTER

A blue icon means that the software component/infrastructure existed prior to the migration.

Option 1

Repurpose current deployment

Upgrade current ArcGIS Server site and use it within the base deployment.

Diagram

ArcGIS Server

ArcGIS Web Adaptor

6080 & 6443

BEFORE

Portal for ArcGIS

ArcGIS Server

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

(hosting server)

(Enterprise portal)7080 & 7443

6080 & 6443

AFTER

Step 1: Upgrade original ArcGIS Server and ArcGIS Web Adaptor

Step 2: Install and configure the remaining components of the base deployment

Comments on Option 1

• End result can be a single or multi-machine base deployment

• ArcGIS Server is both hosting server and GIS server – no workload separation

Benefits:

• Use the same infrastructure

• No need to republish services

• Service URLs do not change

Ideal for:

• Migrating simple standalone ArcGIS Server deployments

Considerations

• Current infrastructure may not be adequate

• Installation and configuration of the base deployment is likely to be done by hand

• Future upgrades will require manual installation

Take away:

• Requires less upfront work, but will require more administrative work down the road.

Option 2

Start from scratch

Create a completely new base ArcGIS Enterprise deployment.

Diagram

Portal for ArcGIS

ArcGIS Server

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

(hosting server)

(Enterprise portal)7080 & 7443

6080 & 6443

ArcGIS Server

ArcGIS Web Adaptor

6080 & 6443

Step 1: Install and configure a new base deployment

Run both deployments side by side

during migration.

(up to 6 months)

Diagram

Portal for ArcGIS

ArcGIS Server

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

(hosting server)

(Enterprise portal)7080 & 7443

6080 & 6443

ArcGIS Server

ArcGIS Web Adaptor

6080 & 6443

Step 2: Republish services to the new ArcGIS Enterprise deployment.

Diagram

Portal for ArcGIS

ArcGIS Server

ArcGIS Data Store(relational + tile cache)

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

(hosting server)

(Enterprise portal)7080 & 7443

6080 & 6443

ArcGIS Server

ArcGIS Web Adaptor

6080 & 6443

Step 3: Take down the standalone ArcGIS Server deployment.

Comments on Option 2

• End result can be a single or multi-machine base deployment

• ArcGIS Server is both hosting server and GIS server – no workload separation

• Run both deployments side by side for up to 6 months during migration

Benefits

• Can use automation tools to install, configure, and upgrade

• More gradual migration – migrating services individually

• Opportunity to prioritize cleaning up their deployments

Comments on Option 2 (continued)

Ideal for:

• Multi-machine ArcGIS Server sites

• Custom deployments

• Organizations that want to be able to use deployment automation tools

- Initial installation

- Future upgrades

• Simple deployments that want to start fresh

• Organizations that want to move from an on-premises deployment to a cloud deployment

• Concerned about infrastructure being adequate to run ArcGIS Enterprise

- Keep eye on ArcGIS Server as it is serving double duty

- Hosting server and traditional GIS Server

Considerations

• Services must be republished

• Service URLs will change

• Can use automation tools to install, configure, and upgrade

- Less administrative overhead in the future

Take away:

More work upfront to migrate, however the end result is infrastructure optimized for ArcGIS Enterprise and because automation tools can be used there is less administrative work down the road.

Option 1 and Option 2 deliver the same end result (a base ArcGIS Enterprise deployment), however you may be more satisfied if you

choose Option 2.

Why option 2 is more favorable:• Optimized infrastructure• Thoughtful service migration – clean start• The ability to automate installation, configuration, and future upgrades

Option 3

Add a base ArcGIS Enterprise deployment.

Setup a new base deployment. The existing ArcGIS Server site gets upgraded and federated to the ArcGIS

Enterprise deployment.

Diagram

ArcGIS Server

ArcGIS Web Adaptor

6080 & 6443

BEFORE AFTER

Step 1: Upgrade original ArcGIS Server and ArcGIS Web Adaptor

ArcGIS Web Adaptor

ArcGIS Web Adaptor

(server)

(portal)

7080 & 7443

6080 & 6443

Step 2: Stand up a new base deployment

Step 3: Federate original ArcGIS Server site to the base deployment

Comments on Option 3:

• Creates a multi-machine deployment

Benefits:

• Service URLs do not change for federated ArcGIS Server site

• Workload separation is enforced

Ideal for:

• Most scenarios

Considerations

• Must purchase additional ArcGIS GIS Server cores

Take away:

While option epitomizes ArcGIS Enterprise architectural best practices because it enforces workload separation, it does require the organization to add more cores and infrastructure to their overall GIS implementation.

Summary

• Before migrating, you should have basic knowledge of ArcGIS Enterprise and understand new terms and concepts such as federation and hosting server.

• Before migration you should have a solid understanding of the ArcGIS Enterprise security model.

• There are 3 options for migrating to ArcGIS Enterprise

- There is no wrong option – though some options may be a better fit depending on the organization’s requirements

• Standalone ArcGIS Server is not going away and will continue to be supported as per the product lifecycle

Migrating a standalone ArcGIS Server to ArcGIS Enterprise