55
FedUC 2009 FedUC 2009 1 1 Enterprise GIS Architecture Enterprise GIS Architecture Sandy Milliken Sandy Milliken (Enterprise Systems Architect) (Enterprise Systems Architect) Ty Fabling Ty Fabling (Enterprise Systems Architect) (Enterprise Systems Architect) 19 February, 2009 19 February, 2009

Enterprise GIS Architecture

  • Upload
    others

  • View
    6

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Enterprise GIS Architecture

FedUC 2009FedUC 2009 11

Enterprise GIS ArchitectureEnterprise GIS Architecture

Sandy MillikenSandy Milliken (Enterprise Systems Architect)(Enterprise Systems Architect)Ty FablingTy Fabling (Enterprise Systems Architect)(Enterprise Systems Architect)

19 February, 200919 February, 2009

Page 2: Enterprise GIS Architecture

FedUC 2009FedUC 2009 22

Enterprise GIS ArchitectureEnterprise GIS Architecture

ESRI Enterprise Consulting Group:ESRI Enterprise Consulting Group:Ty Fabling Ty Fabling (Enterprise Systems Architect)(Enterprise Systems Architect)

Page 3: Enterprise GIS Architecture

FedUC 2009FedUC 2009 33

Primary GIS Architectural GoalsPrimary GIS Architectural Goals(prioritize & balance)(prioritize & balance)

•• FunctionalityFunctionality•• PerformancePerformance•• SecuritySecurity•• PolicyPolicy

–– StandardsStandards–– COTSCOTS

•• VersionsVersions

Make it WorkMake it Work

Make it FasterMake it Faster

Make it SecureMake it Secure

Make it CompliantMake it Compliant

Page 4: Enterprise GIS Architecture

FedUC 2009FedUC 2009 44

Other GIS Architectural IssuesOther GIS Architectural Issues(prioritize & balance)(prioritize & balance)

•• Scalability Scalability (Ease of handling more users or higher volumes)(Ease of handling more users or higher volumes)

•• Mobility Mobility (Field Editing (Field Editing –– Disconnected Data)Disconnected Data)

•• Availability Availability (Dependence on both Internal and External Network)(Dependence on both Internal and External Network)

•• Reliability Reliability (HA / Eliminate single pts of failure / Apps, Data & Network)(HA / Eliminate single pts of failure / Apps, Data & Network)

•• Quality Quality (of Service, Data, etc)(of Service, Data, etc)

•• StabilityStability (Software bug free / Network up(Software bug free / Network up--timetime))

•• Lowest CostLowest Cost•• Maintainability Maintainability (Central vs. Distributed (Central vs. Distributed –– Applications vs. Data)Applications vs. Data)

•• Flexibility Flexibility (Total Life(Total Life--Cycle Cycle –– Ease of Upgrading to Future Versions)Ease of Upgrading to Future Versions)

Page 5: Enterprise GIS Architecture

FedUC 2009FedUC 2009 55

Technology Maturation ProcessTechnology Maturation Process

Innovation

Standardization

ProductivityGains

Manage RiskMore Less

Page 6: Enterprise GIS Architecture

FedUC 2009FedUC 2009 66

Basic ArchitecturesBasic Architectures

Presentation

Business Logic

Data Management

Presentation

Business Logic

Data Management

ClientPresentation

ClientPresentation

Data ServerData Management

Data ServerData Management

Application ServerBusiness Logic

Application ServerBusiness Logic

Single TierSingle Tier Multi TierMulti Tier

PresentationPresentation

Business LogicBusiness Logic

Data ManagementData Management

Page 7: Enterprise GIS Architecture

FedUC 2009FedUC 2009 77

GIS Common Solution ArchitectureGIS Common Solution Architecture

•• Presentation TierPresentation Tier•• DesktopDesktop•• Web/Rich Internet ApplicationsWeb/Rich Internet Applications•• MobileMobile

•• Services TierServices Tier•• Exposure of informationExposure of information

•• Enterprise MessagingEnterprise Messaging•• Messaging methods, protocolsMessaging methods, protocols

•• Application TierApplication Tier•• Session managementSession management•• Business LogicBusiness Logic•• User interactionUser interaction

•• Persistence TierPersistence Tier•• Databases, FilesDatabases, Files

Enterprise Messaging

Page 8: Enterprise GIS Architecture

FedUC 2009FedUC 2009 88

Firewall Technology

Storage NetworkStorage Network

Optional Firewall Technology

Optional Firewall Technology

Switched Storage Network

Switched IP Network

Data Center ArchitectureData Center Architecture

Web Application ServersWeb Application ServersWindows Terminal ServerWindows Terminal ServerArcIMSArcGIS ServerImage Server

ArcGIS DesktopDesktop Applications

ComponentApplication Tier

ComponentApplication Tier

Enterprise Web Application ServersEnterprise Web Application ServersWebsphere Enterprise ApplicationsWeblogic Enterprise ApplicationsEnterprise Portal Technology

Enterprise TierEnterprise Tier

Production EnvironmentProduction Environment

Proxy ServersEdge ServersNetwork Traffic Load BalancingTraffic Accelerators

Web Access TierWeb Access Tier

DevelopmentServers

TestServers

Develop and test EnvironmentDevelop and test Environment

File Server Geodatabase DBMS

Data TierData TierOracleSql ServerDB2Informix

Spatial Files

- Coverages- Shapes- Images

Spatial Files

- Coverages- Shapes- Images

Attributes

- Customers- Facilities- Doc

Attributes

- Customers- Facilities- Doc

Geodatabase

- SDE Schema- User Schema- Vector Data- Image Data

Geodatabase

- SDE Schema- User Schema- Vector Data- Image Data

Development-Develop-Training-Demo

Development-Develop-Training-Demo

TestTest

Page 9: Enterprise GIS Architecture

FedUC 2009FedUC 2009 99

What demands does GIS place on computing What demands does GIS place on computing infrastructure?infrastructure?

•• Processing Intensive (CPU)Processing Intensive (CPU)•• Graphics Intensive (GPU)Graphics Intensive (GPU)•• Memory Intensive (RAM)Memory Intensive (RAM)•• Network I/O IntensiveNetwork I/O Intensive•• Disk I/O IntensiveDisk I/O Intensive

Page 10: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1010

GIS Business Planning GIS Business Planning

Business ProcessesBusiness Processes(User workflows)(User workflows)

Data RequirementsData Requirements(Information resources)(Information resources)

Application NeedsApplication Needs(User productivity tools)(User productivity tools)

Infrastructure Requirements

Users GIS DataApplicationsThe three key architecture factors are the location of:

Page 11: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1111

Enterprise GIS ArchitecturesEnterprise GIS Architectures

Key Components:Key Components:•• UsersUsers•• ApplicationsApplications•• DataData

Only Two Primary Architectures:Only Two Primary Architectures:•• Centralize in the Centralize in the Data CenterData Center (Web Services, Citrix)(Web Services, Citrix)•• Distribute to Distribute to Regional OfficesRegional Offices (Data Replication)(Data Replication)

–– Hybrid Solution: New Mobile ADF Hybrid Solution: New Mobile ADF SmartClientSmartClient

Page 12: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1212

Three Elements & Two NetworksThree Elements & Two Networks

Three Major Elements: Three Major Elements: 1.1. Users Users 2.2. ApplicationsApplications3.3. DataData

•• Where do each reside Where do each reside (Data Center, Regions, etc)?(Data Center, Regions, etc)?

•• What is the network connectivity like What is the network connectivity like between these three? between these three? –– LAN vs. WANLAN vs. WAN–– Network Bandwidth and LatencyNetwork Bandwidth and Latency–– Frequency of Outages or DropsFrequency of Outages or Drops

Users

Applications Data1

2

3

4

5

User-to-AppConnectivity

App-to-DataConnectivity

High BandwidthThin Connection

Page 13: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1313

Centralized InfrastructureCentralized Infrastructure

Data Center

RegionalOffice

Lab

FieldOffice

ProgramOffice

Application Data

Citrix Server FarmWeb Servers

OracleArcSDE

User

User User

User

Centralized SystemsCentralized SystemsCentralized Application near Centralized DataCentralized Application near Centralized Data(Web Apps & Citrix)(Web Apps & Citrix)

Thin Client Connections

Thin Client Connections

Thin ClientConnections

Thin ClientConnections

Field User

Page 14: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1414

Distributed InfrastructureDistributed InfrastructureDistributed SystemsDistributed SystemsDistribute Replicated DataDistribute Replicated Data(9.2 Replication)(9.2 Replication)

Data Center

MasterDatabase

FileServer

Data (“Master”)

Region

User

LocalServer

Data(“Replica”)

Regional Office

Field Office

App.&

UserApp.

&

UserApp.

&User

App.&

UserApp.

&Replicate Deltas Only

Replicate Deltas Only

Replicate Deltas Only

Field User

Page 15: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1515

Centralized vs. Distributed SystemsCentralized vs. Distributed Systems

Centralized SystemsCentralized Systems•• Uses Citrix or Web Service appsUses Citrix or Web Service apps•• Single pointSingle point--ofof--access for data, access for data,

centralized managementcentralized management•• Dependant upon network for Dependant upon network for

Application & DataApplication & Data•• Reduced WAN & LAN trafficReduced WAN & LAN traffic•• Increased O&S at Data CentersIncreased O&S at Data Centers•• Decreased O&S at RegionDecreased O&S at Region

Distributed SystemsDistributed Systems•• Uses desktop apps on local Uses desktop apps on local

workstationworkstation•• Multiple replicas of data at Regions, Multiple replicas of data at Regions,

synched w/ mastersynched w/ master•• Less dependant upon WANLess dependant upon WAN•• Increased LAN trafficIncreased LAN traffic•• Decreased O&S at Data CentersDecreased O&S at Data Centers•• Increased O&S at RegionsIncreased O&S at Regions

High Points:High Points:•• Minimizes resource requirements at Minimizes resource requirements at

regional centersregional centers•• Centralized database and system Centralized database and system

administration administration –– integrityintegrityLow Points:Low Points:•• Network is a Network is a single point of failuresingle point of failure

High Points:High Points:•• Editing data offline (during outages)Editing data offline (during outages)•• Data distribution (i.e. outsourcing to Data distribution (i.e. outsourcing to

data vendors, outside agencies)data vendors, outside agencies)Low Points:Low Points:•• Increased resources, O&S support Increased resources, O&S support

maintaining client software and data at maintaining client software and data at regional centers, etc.regional centers, etc.

•• Posting/synchronizing local data with Posting/synchronizing local data with master master database(sdatabase(s) ) –– data currencydata currency

Page 16: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1616

Two GeoTwo Geo--Enterprise Information System ApproachesEnterprise Information System Approaches

GIS EnabledGIS Centric

Enterprise Applications that include GIS InformationCore GIS technology

Spatially-enabled lines of business-centric workflowsGeo-centric workflows

Run by IT professionalsRun by GIS and IT professionals

Examples• Financial system, facility management, executive information system, customer care, first responder

Examples• Land records, asset management, facility sitting, corridor analysis

IT-basedIT-based

Simple GIS functionality• Data exploitation, routing, geocoding, simple map

Advanced GIS applications• Data creation and maintenance, analysis and modeling

Spatially-enabled Information SystemEnterprise GIS

Page 17: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1717

Enterprise ArchitectureEnterprise Architecture

ClientsClients

ApplicationApplicationServersServers

DataDataServersServers

CRM CIS SFAERP

DesktopDesktop B r o w s e rB r o w s e r

GIS

Web ServerWeb Server

GIS CentricGIS Centric GIS EnabledGIS Enabled

Page 18: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1818

Expanding Deployment Options Expanding Deployment Options Remote Access Client OptionsRemote Access Client Options–– Mobile ADFMobile ADF

•• Supports Windows XP and Mobile Operating SystemsSupports Windows XP and Mobile Operating Systems•• Requires developmentRequires development

–– ArcPadArcPad•• Complete ApplicationComplete Application

–– BrowsersBrowsers•• ArcGIS Server and ArcIMSArcGIS Server and ArcIMS

–– ArcEngineArcEngine•• Rich Client Development environmentRich Client Development environment•• Can Consume web servicesCan Consume web services

–– Windows Terminal Services / CitrixWindows Terminal Services / Citrix•• Full Rich Client FunctionalityFull Rich Client Functionality•• Typically utilized by Typically utilized by ““AuthorsAuthors””

–– ArcMapArcMap•• Full Rich Client FunctionalityFull Rich Client Functionality•• Can consume web services and new GeoData disconnected EditingCan consume web services and new GeoData disconnected Editing

PhonePhone PDAPDA TabletTablet LaptopLaptop WorkstationWorkstation

Increasing Bandwidth / Connectivity / Richness Increasing Bandwidth / Connectivity / Richness

TechnologyTechnology

NetworkNetwork

SoftwareSoftware

ArcPadArcPadMobile ADFMobile ADF

ArcEngineArcEngineCitrixCitrixBrowserBrowser

ArcMapArcMap

Line between Line between Mobile Users and Mobile Users and Remote Clients Remote Clients

is blurringis blurring

Page 19: Enterprise GIS Architecture

FedUC 2009FedUC 2009 1919

The The SmartClientSmartClient ParadigmParadigmArcGIS MobileArcGIS Mobile

SmartClientSmartClient ParadigmParadigm•• For Sometimes Connected SystemsFor Sometimes Connected Systems•• .NET based replication.NET based replication•• Masters & Replicas with only deltas moving across the wireMasters & Replicas with only deltas moving across the wire

Page 20: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2020

Remote Access Client OptionsRemote Access Client OptionsArcGIS Mobile in the EnterpriseArcGIS Mobile in the Enterprise

•• Existing SystemsExisting Systems––GDB ReplicationGDB Replication––SDESDE

•• Mobile ServerMobile Server––Web servicesWeb services––Staging of dataStaging of data

•• Mobile ClientMobile Client––Map, Map, MapActionsMapActions––MapCacheMapCache––ServerConnectionServerConnection

GPRSEDGE

HSDPA802.11Cradle

Connectivity

Security

Web Services

Server Manager

Web Services & DataManagem

ent

User ExperienceUser Experience

Business LogicBusiness Logic

Data & Web SvcData & Web Svc

ArcGIS ServerArcMobile Enterprise Systems

Page 21: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2121

Remote Access Client OptionsRemote Access Client OptionsMobile ADF Application and Data DeploymentMobile ADF Application and Data Deployment

Connection

ArcGIS Server

Data Extraction

Editing Application Viewing Application

Day to Day synchronization from

the Field

Deployment

Web Service

MapCache Extractor

ApplicationDevelopment

Visual Studio

Mobile Applications

Posts Edits Refresh Data

Page 22: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2222

GIS Is Deployed In Many WaysGIS Is Deployed In Many Ways

EmergingEmerging

TraditionalTraditional

DepartmentalDepartmental EnterpriseEnterprise

File BasedFile Based

11 22

33 44

Centralized GISCentralized GIS

Distributed DataDistributed Data

Page 23: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2323

GIS Software Evolution GIS Software Evolution

ArcSDE 1999- Simple non-versioned file types

- Geodatabase Versioning (ArcSDE)- Distributed Geodatabase Replication

ArcGIS DesktopArcGIS Desktop-- ArcInfo 1999ArcInfo 1999

-- ArcEditor 2000ArcEditor 2000-- ArcView 2000ArcView 2000

-- ArcGIS Server ArcGIS Server 20042004-- ArcGIS Engine ArcGIS Engine 20042004

ARC/INFO 1982ARC/INFO 1982ArcView GIS 1992ArcView GIS 1992

MapObjectsMapObjects 1996 1996 ArcIMS 1997 ArcIMS 1997

CoveragesLibrarian

ShapefilesArcStormArcStorm

Spatial Database Engine (SDE)Spatial Database Engine (SDE)

What are the lessons learned and where is the technoloWhat are the lessons learned and where is the technology going?gy going?

Tightly Scripted Software Code1982–1999 Object Relational Architecture Service Oriented Architecture

> 2x Process Load>> 10x Faster Technology Change

> 2x Process Load>> 10x Faster Technology Change

> 2x Process Load>> 10x Faster Technology Change

> 2x Process Load>> 10x Faster Technology Change

Platform Performance Change>> 10x Faster Hardware >> 10x Faster Hardware

Scripts Objects Services

1980’s 1990’s 2000’s 2010’s

InternetWeb Applications

Departmental Centralized Federated

Mobility

Page 24: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2424

UseUse

ServeServe

AuthorAuthor

Web MapWeb MapDesktopDesktop ExplorerExplorer MobileMobileEnterpriseEnterpriseIntegrationIntegration

OpenOpenStandardsStandards

UseUse

ServeServe

AuthorAuthor

Web MapWeb MapDesktopDesktop ExplorerExplorer MobileMobileEnterpriseEnterpriseIntegrationIntegration

OpenOpenStandardsStandards

SOA SOA -- GIS Functional ViewGIS Functional View

ArcGIS ArcGIS Desktop Desktop

UsersUsers

Page 25: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2525

PresentationTier

(multiple viewers)

Globe Services

Map &Chart

Services

Image-Processing

Services

Open Web

Services

Tracking& RSS

Services

Serving/Publishing

Tier

AuthoringTier

22--D D ViewersViewers

33--DDViewersViewers

Catalog Services

Geo-Processing

Services

Enterprise Messaging Services

COPCOP

SOA SOA -- GIS Functional ViewGIS Functional View

DesktopDesktop

ServerServer

•• VisualizationVisualization•• Consume ServicesConsume Services

•• Geodata ManagementGeodata Management•• Data EditingData Editing•• Analysis Published as a ServiceAnalysis Published as a Service

•• GeoprocessingGeoprocessing•• VisualizationVisualization

ClientClient

Page 26: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2626

ArcGIS ArcGIS –– Platform for a Complete GISPlatform for a Complete GISESRI Enterprise GIS ArchitectureESRI Enterprise GIS Architecture

Authoring Tier

Presentation Tier(Any Viewer)

Use

Map &Chart

Services

ImageServices

OpenWeb

Services

Tracking& RSS

Services

Serving &Publishing

Tier

22--D D ViewersViewers

33--DDViewersViewers

MetadataCatalog Services

Geo-Processing

Services

COPCOPMobileMobile

DesktopDesktop

ServerServer

•• VisualizationVisualization•• Consume ServicesConsume Services

GPTGPT

•• Geodata ManagementGeodata Management•• Data EditingData Editing•• Analysis Published as a ServiceAnalysis Published as a Service

ArcGIS Desktop (ArcMap, ArcCatalog)ArcGIS Desktop (ArcMap, ArcCatalog)Image Service Definition EditorImage Service Definition Editor

•• GeoprocessingGeoprocessing•• VisualizationVisualization

ClientClient

Page 27: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2727

SOA OverviewSOA OverviewDefinitionDefinition

A method of buildingA method of building business applicationsbusiness applicationsthat utilize common servicesthat utilize common services

to support business functionsto support business functions

Bind / Invoke

ServiceConsumerService

ConsumerServiceProviderServiceProvider

ServiceDirectoryService

Directory

Find / Details Publish

Page 28: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2828

Web Services OverviewWeb Services OverviewCore ComponentsCore Components

WebServices

SOAPWSDL

UDDI

•• Service DescriptionService Description–– WSDLWSDL

•• Web Services Description LanguageWeb Services Description Language•• Defines all details about a serviceDefines all details about a service

•• Service ProtocolService Protocol–– SOAPSOAP

•• How to format XML documents for How to format XML documents for transmission between applicationstransmission between applications

•• Service DiscoveryService Discovery–– UDDIUDDI

•• Universal Description, Discovery, and Universal Description, Discovery, and IntegrationIntegration

•• Not a requirementNot a requirement•• Well proven for single Enterprise systemsWell proven for single Enterprise systems

These 3 technology standards, coupled with service-oriented design principles, form a basic XML-driven SOA

Enablesdiscovery of

Is accessedusing

DescribesEnables

Communicationbetween

Binds to

WSDL SOAP UDDI

Page 29: Enterprise GIS Architecture

FedUC 2009FedUC 2009 2929

What Supports Web Services?What Supports Web Services?2nd Generation Web Services2nd Generation Web Services

•• Many still being finalized or have competing standardsMany still being finalized or have competing standards•• WSWS--Security and BPEL are exceptionsSecurity and BPEL are exceptions

–– Ultimately incorporated into the other 3 solutionsUltimately incorporated into the other 3 solutions

WebServices

SOAP

UDDI

WSDL

EnablesEnablesdiscovery ofdiscovery of

Is accessedIs accessedusingusing

DescribesDescribesEnablesEnables

CommunicationCommunicationbetweenbetween

Binds toBinds to

BPEL WS-PolicyWS-Transaction

WS-Coordination

WS-ReliableMessaging

Provides aProvides aProtocol forProtocol for

Describes theDescribes theService forService for

Describes theDescribes theService forService for

Provides aProvides aProtocol forProtocol for

Provides aProvides aProtocol forProtocol for

Provides aProvides aProtocol forProtocol for

ManagesManagesContext forContext for

ManagesManagesContext AcrossContext Across

usesuses

ProvidesProvidesEndEnd--toto--endendSecurity forSecurity for

usesuses

usesuses

usesuses

governsgovernsorchestratesorchestrates

EnablesEnablesDistributedDistributed

Transactions forTransactions for

WS-Security

Provides aProvides aProtocol forProtocol for

Provides Provides GuaranteedGuaranteedDelivery forDelivery for

Page 30: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3030

SOA InfrastructureSOA Infrastructure

•• Connects Service Consumers with Service ProvidersConnects Service Consumers with Service Providers•• May be used to communicate with Service DirectoriesMay be used to communicate with Service Directories•• May be implemented using a variety of technologiesMay be implemented using a variety of technologies

Page 31: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3131

Enterprise SOA FrameworkEnterprise SOA Framework

•• ClientsClients–– MultiMulti--Channel AccessChannel Access

•• Types of ApplicationsTypes of Applications–– Client AppsClient Apps–– Web ApplicationsWeb Applications–– Web ServicesWeb Services

•• Data Sources (Producers)Data Sources (Producers)

•• Unifying ComponentsUnifying Components–– Web PortalsWeb Portals

•• Common Viewing Common Viewing InterfaceInterface

–– ESBESB•• Common Messaging Common Messaging

FrameworkFramework–– ObjectsObjects

•• Common System Common System ComponentsComponents

–– Different Communication Different Communication Paths may be utilizedPaths may be utilized

Page 32: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3232

GIS SOA ComponentsGIS SOA Components

Page 33: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3333

How does ESRI fit into SOA?How does ESRI fit into SOA?

……and many othersand many others……and many othersand many others

•• Other Web ServicesOther Web Services

Page 34: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3434

How does ESRI fit into Enterprise SOA?How does ESRI fit into Enterprise SOA?ArcGIS ExplorerArcGIS Explorer

Page 35: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3535

Secure ImplementationSecure ImplementationFundamental TradeoffFundamental Tradeoff

Secure

Usable Cheap

You get to pick any two!You get to pick any two!

Page 36: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3636

ArcSDE**ArcSDE**•• SQL ServerSQL Server•• OracleOracle•• DB2DB2•• InformixInformix

8.38.3++

New GDBs are:New GDBs are:•• FastFast•• SimpleSimple•• ScalableScalable•• OpenOpen•• Cross Platform*Cross Platform*

ArcSDE** ArcSDE** DesktopDesktopEditionEdition

ArcSDE** ArcSDE** WorkgroupWorkgroup

EditionEditionPersonalPersonal

(JET Engine)(JET Engine)FileFile--based*based*

ArcSDE**ArcSDE**EnterpriseEnterprise

EditionEdition

ArcGISArcGISClientsClients

Embeds ArcSDEEmbeds ArcSDEw/ SQL Express w/ SQL Express @ 9.2@ 9.2

New GDBsNew GDBs

Simplifying GeodatabasesSimplifying GeodatabasesArcGIS 9.2 ArcGIS 9.2 -- New Support for File, Personal and New Support for File, Personal and Work Group GeodatabasesWork Group Geodatabases

*FGDB Supported on*FGDB Supported onWindows, Linux or UNIXWindows, Linux or UNIX

**Replication:**Replication:SDE Only @ 9.2SDE Only @ 9.2Files GDB @ 9.3 Files GDB @ 9.3 ((OneOne--way Readway Read--OnlyOnly))

9.29.2++

8.38.3++

8.38.3++

9.29.2++

9.29.2++

ArcSDE**ArcSDE**•• SQL ServerSQL Server

(z/OS @ 9.3) (z/OS @ 9.3)

•• PostgreSQL @ 9.3PostgreSQL @ 9.3& Oracle Express @ 9.3& Oracle Express @ 9.3

ShapefilesShapefiles

Page 37: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3737

SupportsSupports•• Collaborating AgenciesCollaborating Agencies•• CoCo--Data ProducersData Producers•• Central & Regional OfficesCentral & Regional Offices•• Mobile UnitsMobile Units

OneOneWayWay

TwoTwo

WayWayRead /Read /WriteWrite

ReadReadOnlyOnly ArcIMSArcIMS

Read /Read /WriteWrite

•• Changes Only Updates (Deltas)Changes Only Updates (Deltas)•• Synchronized Periodically (Configurable)Synchronized Periodically (Configurable)•• Works on the Web or Courier (Works on the Web or Courier (i.e.i.e. CD)CD)•• Client to Client (not DB to DB)Client to Client (not DB to DB)•• Only Supported on SDE Versioned RDBMSOnly Supported on SDE Versioned RDBMS

NationalNational

StateState

LocalLocal

HierarchyHierarchy

CentralCentral

. . . Key Technology For . . . Key Technology For GeoWebGeoWeb

Managing Distributed DataManaging Distributed DataArcGIS 9.2 ArcGIS 9.2 -- Replication of Geographic InformationReplication of Geographic Information

Page 38: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3838

ArcGIS 9.2 Supports Oracle SpatialArcGIS 9.2 Supports Oracle SpatialThree Ways with New Oracle Three Ways with New Oracle SQL_TypeSQL_Type

. . . Using Multiple Methods & Techniques for Many Large Custome. . . Using Multiple Methods & Techniques for Many Large Customersrs

BinaryBinary

SDO TypeSDO Type

ISOISOTypeTypeOther DBMSOther DBMS

*SQL*SQL

ArcGISArcGISSDE

OracleOracle

Can Be Deployable as App ServerCan Be Deployable as App Server(Performance/Scalability)(Performance/Scalability)

ArcSDE is How ArcGIS Accesses ArcSDE is How ArcGIS Accesses And Maintains Data in RDBMSAnd Maintains Data in RDBMS

Three Storage Types are SupportedThree Storage Types are Supported•• BinaryBinary•• SDO TypeSDO Type•• ISO SQL Type (st_geometry @9.2)ISO SQL Type (st_geometry @9.2)

*Any GIS application can now*Any GIS application can nowquery GIS features stored using query GIS features stored using

the new ISO the new ISO SQL_TypeSQL_Typedirectly without requiring ArcSDEdirectly without requiring ArcSDE

Page 39: Enterprise GIS Architecture

FedUC 2009FedUC 2009 3939

Integration of TimeIntegration of TimeNew Ways to Manage, Analyze & Visualize GeographyNew Ways to Manage, Analyze & Visualize Geography

PastPastPresentPresent

FutureFutureTT11

xx

yyTT

FilesFiles

ModelModeling ing SimulationSimulation

History / History / ArchivingArchiving

Multi Dimension Multi Dimension Data Sets (NetCDF)Data Sets (NetCDF)

DateDate

CurrentCurrentDateDate

RetireRetire

ViewView ControlControlRoomRoom

StationaryStationaryMobileMobile

Real TimeReal TimeSensor NetworkSensor Network

•• Extended Data ModelExtended Data Model

•• Tools for ManipulationTools for Manipulation–– QueryQuery–– Change AnalysisChange Analysis–– Iterative ProcessingIterative Processing–– VisualizationVisualization

•• AnimationAnimation•• ChartingCharting

–– Tracking AnalysisTracking Analysis

. . . New Opportunities. . . New Opportunities

Archive/HistoryArchive/History

Page 40: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4040

ArcSDE ComponentsArcSDE Components

Note: ArcSDE executables are included in Direct Connect API

DBMS

ArcGIS Application

ArcSDE Driver ArcSDE Executable

User Schema(s)

ArcSDE Schema

SDE Schema

License Code

Page 41: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4141

ArcSDE ComponentsArcSDE Components

Note: ArcSDE executables are included in Direct Connect API

DBMS

ArcSDE API ArcSDE Executable

User Schema(s)

ArcSDE Schema

License Code

ArcGIS Application

9.1

SDE Schema

Page 42: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4242

ArcSDE ComponentsArcSDE Components

Note: ArcSDE executables are included in Direct Connect API

DBMS

ArcSDE API ArcSDE Executable

User Schema(s)

ArcSDE SchemaSDE Schema (n)

License Code

ArcGIS Application

9.2

SDE Schema 1

User Schema(s)

Page 43: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4343

MultiMulti--Tiered SDE ArchitectureTiered SDE Architecture

RDBMS[SDE schema][user schema]

SDE* [gsrvr](ASC)

ClientTier or

Database Server Tier

RDBMS[SDE schema][user schema]

ArcObjector ArcIMS

DB Client

SDE (DC)

ArcObjector ArcIMS

SDE** [gsrvr]

DB Client

Two-tier Two-tier Three-tierSDE Direct ConnectSDE geodatabase Server SDE Application Server

Direct Connect

ArcObjector ArcIMS

ApplicationServer Tier

ASC - Application Server Connect

SDE Connect SDE Connect

SDE GIOMgr

SDE GIOMgr

* Local Connection

** Remote Connection

Page 44: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4444

Application Server

ArcIMS Component ArchitectureArcIMS Component Architecture

SS Spatial ServerImage Feature ArcMapExtract Query Geocode

Spatial Services

DS Data ServerData Source

Service Manager

MapRequest

MapRequest

MapRequest

MapRequest

SM

WA Connectors

Web ServerApplications (ColdFusion/ASP/.NET/….Servlet Engine......)

Web Applications

CF

.NET Link

ServletJavaW

MSW

FSCS-WOAI-PW

H

ActiveX

Database Connections

ImageVirtual Server

Threads

FeatureVirtual Server

Threads

ArcMapVirtual Server

Threads

Page 45: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4545

Application Developer Framework (ADF) runtime

Web Server

Web Application ServerWAWeb Applications

ArcGIS Server Component ArchitectureArcGIS Server Component Architecture

Applications (.Net or JSP) Web Services (SOAP)

Server Object Manager(load controller)SMService Manager

Data Server(Geodatabase Server)DSData Source

Container Machine

SOC SOC

SSSpatial ServicesMapServer GeocodeServer

ArcGIS Server Objects

ArcSDE Connects

MapRequest

MapRequest

MapRequest

MapRequest

InstancesPooled Non Pooled

AGS Licensable Components

ADFADF

SOMSOM

SOCSOC

SDESDE

Page 46: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4646

WA

SM

SS

DS

GIS Server

WA

SM

DS

GIS Server

SS

High-Availability Configuration

Enterprise Server with SQL Express

SingleSingle--tier Platform Configurationtier Platform Configuration

Network Load Balancing

SSSS

SMLoad Balancing

WA

SM

SS

DS

GIS Server

Standard Configuration

Workgroup Server with SQL Express

Page 47: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4747

TwoTwo--tier Platform Configurationtier Platform ConfigurationEnterprise Server with Supported DatabaseEnterprise Server with Supported Database

WA

SM

SS

GIS Server

WA

SM

GIS Server

SS

High-Availability Configuration

Network Load Balancing

SSSS

SMLoad Balancing

DS DS

Primary Data Server Failover Data ServerCommon Storage Array

Cluster Address

Standard Configuration

WA

SM

GIS Server

SS

DS

Page 48: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4848

WA

Web Server

WA

Web Server

SM SM

ThreeThree--tier GIS Platform Configurationstier GIS Platform ConfigurationsSeparate Web and Spatial Servers with Supported DatabaseSeparate Web and Spatial Servers with Supported Database

WA

SM

Web Server

SS

Map ServerContainer Machine

DS

SS

SMLoad Balancing

Map ServerContainer Machine

Network Load Balancing

High-Availability Configuration

SS SS

Map ServerContainer Machine

Map ServerContainer Machine

SSSS

SMLoad Balancing

Standard Configuration

DS DS

Primary Data Server Failover Data ServerCommon Storage Array

Cluster Address

Page 49: Enterprise GIS Architecture

FedUC 2009FedUC 2009 4949

Data Server

DMZ

Web Services Components in DMZWeb Services Components in DMZ

ClientBrowser

Secure Network

Data Replication

WA

SM

SS

Web Server

DS

Data Server

Map ServerContainer Machine

WWW

WA Access

Page 50: Enterprise GIS Architecture

FedUC 2009FedUC 2009 5050

DMZSecure Network

Map/Data Server on Secure NetworkMap/Data Server on Secure Network(Service Manager inside Firewall)(Service Manager inside Firewall)

WA

Web Server

OutputFile

ClientBrowser

SM

SS

Map ServerContainer Machine

DS

Data Server

WA Access

Disk Mount*

* Disk mount can be replaced with output streamingArcIMS: Output streaming requires JSP or .NET client

** HTTP service required for ArcGIS Server to avoid DCOM port administration.

WWW

WA

HTTP Access**SOAP/XML

SM Access

Page 51: Enterprise GIS Architecture

FedUC 2009FedUC 2009 5151

DMZ

Web Services with Proxy Server in DMZWeb Services with Proxy Server in DMZ

PS Access

Secure Network

WA Access

WA

SM

SS

Web Server

DS

OutputFile

ReverseProxyMap Server

Container Machine

Data Server

ClientBrowser

WWW

Proxy Server

Page 52: Enterprise GIS Architecture

FedUC 2009FedUC 2009 5252

ESRI Enterprise Support ResourcesESRI Enterprise Support Resources

•• System Design StrategiesSystem Design Strategies–– OnOn--Line Document on ESRI Web Site Line Document on ESRI Web Site ((www.esri.com/SystemDesignwww.esri.com/SystemDesign))

–– Dave PetersDave Peters’’ Book: Book: ‘‘Building a GISBuilding a GIS’’ -- published Aug 2008published Aug 2008

–– CPTCPT-- Capacity Planning Tool Capacity Planning Tool (Excel Worksheet)(Excel Worksheet)

•• Enterprise Consulting GroupEnterprise Consulting Group–– System Architecture Design Classes System Architecture Design Classes (Available around the World)(Available around the World)

–– Enterprise Architecture Consulting ServicesEnterprise Architecture Consulting Services–– EEAP EEAP –– ESRI Enterprise Advantage ProgramESRI Enterprise Advantage Program–– BPAP BPAP –– ESRI Business Partner Advantage ProgramESRI Business Partner Advantage Program

Page 53: Enterprise GIS Architecture

FedUC 2009FedUC 2009 5353

Power User GroupPower user representatives

End User GroupEnd user representatives

ApplicationWorking Group

Application Specialist ChairmanApplication Development Team

Data ManagementWorking Group

GIS Data Specialist ChairmanData Management Team

IT InfrastructureWorking Group

IT Lead ChairmanIT Operations Team

Technical Coordinating CommitteeGIS Manager, Technical Lead, Application Specialist, Data Specialist, IT Lead (platforms and networks)

Provide technical direction and standards, recommend projects and studies, recommend database/application development, address system integration/expansion issues, conduct user training.

Enterprise GIS GovernanceEnterprise GIS Governance

Steering or Policy CommitteeExecutive Sponsor, Department Managers

Status review, general oversight, policy formulation, finance and budget decisions, growth and expansion of participant base, approval of special license agreements, product pricing, providedirection to the GIS departments, legal obligations.

Page 54: Enterprise GIS Architecture

FedUC 2009FedUC 2009 5454

Building a Qualified GIS StaffBuilding a Qualified GIS Staff

Page 55: Enterprise GIS Architecture

FedUC 2009FedUC 2009 5555

Managing the Enterprise GISManaging the Enterprise GIS

Maintaining Agile SystemsMaintaining Agile Systems

Strategic Plan

Deployment Authorization

Strategic Plan

Deployment Authorization

An Enterprise GIS is never done!An Enterprise GIS is never done!

SpiralSpiral SpiralSpiral