Wisdot-Arc Gis Server

8/3/2019 Wisdot-Arc Gis Server

1/30

Mitch Moline

WisDOT GIS System and Technology Administrator


2/30

ArcGIS Upgrade Project

DOA/DOT Co-Location Project

ArcGIS Server Recommendations Project

ArcGIS Server Implementation Project

Whats in this session


3/30

What was Upgraded

Approach Used for Upgrade

Lessoned Learned

ArcGIS 9.3.1 Upgrade Project ...


4/30

What was Upgraded and Approach Used

Tested and bug fixed ArcGIS Desktop Applications

Standalone VB6 Applications

Customized .MXDs (VBA)

ArcGIS Desktop Upgrade via Enterprise Software Distribution (ESD) Packages

ArcIMS Upgrade Bug Fixed ArcIMS Applications and re-staged

ArcIMS Server Upgrade Done Manually

ArcSDE Upgrade Done Manually


5/30

Lessoned Learned

2 - Edit dbtune table (configuration keywords) to use LONGRAW, not ST_GEOMETRY

http://support.esri.com/index.cfm?fa=knowledgebase.whitepapers.viewPaper&PID=66&MetaID=1301

3 - V9.1 Feature Classes/Datasets are Low Precision, data loading at v9.3.1 are High Precision

4 Needed to add these elevated permissions for the SDE user (not needed in past)

lock any table

update any table

see http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=35013

see

1 Can use silent install switches from this ESRI White Paper

http://downloads2.esri.com/support/whitepapers/ao_/ArcGIS_9.3_Enterprise_Deployment.pdfsee


6/30

DOA/DOT Co-Location

The DET/DOT Server Co-location Project was for DET to support the co-

location of all DOT production and production support applications, servers,

and devices into the DET Femrite Data Center (FDC) by providing DOT asecure facility, network connectivity, network racks, enclosures (cabinets) and

facility resources.

Since I did not build the v9.1 system, I had to document the current system

so I could rebuild it at the FDC as v9.3.1

New GIS Infrastructure Build from Ground Up: Green Field Builds network, connectivity and servers

Production = physical blades; SYST and UAT = virtual machines

Once new hardware production, severs aliased with the old server

names to avoid breaking code, connection files, layer files etc


7/30

Separate Production, Acceptance and System Test Environments

Co-Located GIS Server Infrastructure

Scaled for the implementation of ArcGIS Server


8/30

ArcGIS Desktop Firewall Rules .

Added a dedicated ArcGIS 9x LM (keyless)

Locked LM Ports:27005/10xx for ESRI LM (8x)

27004/10xx for ArcGIS LM (9x)

Added a new GeoProcessing Server

Added a new Raster File Server


9/30

ArcIMS/ArcSDE Firewall Rules

One ArcIMS Installation/Config

Opened ArcIMS Servlet

Scaled Architecture to

support ArcGIS Server


10/30

ArcGIS Server (AGS) Recommendations Project

The Purpose of this project was to determine and evaluate

business requirements, perform R&D, and make

recommendations for the implementation of ArcGIS Server

The Scope of this project was to develop recommendations in theform of alternatives for implementing AGS at WisDOT


11/30

Configuring alternative AGS Application and Web Server environments

Configuring alternative Unit Test Environments

Deploying R&D AGS Web Mapping Services and Applications

Performing tests to define a fully supportable AGS environment

Recommendations were determined by


12/30

AGS R&D Web and Application Servers

VM Builds in Test Zone at FDC Windows 2003 vs. 2008 OS

Java and .NET AGS Application Sever Configurations

IIS and Apache/Tomcat and WAS6 Web Server Configurations


13/30

AGS Unit Test Environments

Tested different development environments for the AGS Web APIs

Used Microsoft Visual Studio 2008 for .NET ADF

Used RSA (Eclipse) for the Java ADF

AGS Services were either hosted locally (EDN) or from R&D AGS Server

All AGS Services Used Direct Connect


14/30

Unit Test Development Platforms

ArcGIS Server API for JavaScript Apache/Tomcat and IIS Mozilla Firefox/Firebug

JavaScript, HTML, Dojo

ArcGIS Server API for Flex Apache/Tomcat and IIS Flex Builder (Trial Version)

MXML, ActionScript Flex API downloaded locally Client plug-nArcGIS Server API for Silverlight/WPF

Visual Studio 2008 SP1 Silverlight Tools for Visual Studio 2008 SP1 Expression Blend 3 (optional install, trial version) XAML, VB.Net (most samples are in C+) ArcGIS API for Microsoft Silverlight/WPF download locally Client plug-in

NET Web ADF for ArcGIS Server IIS ArcGIS Server for Microsoft .NET Framework (EDN) Visual Studio 2008 C# and Javascript

Java Web ADF for ArcGIS Server Tested With RSA (Eclipse)

RSA (Eclipse) Using SOAP for ArcGIS Server


15/30

What as deployed and tested

AGS Service Types Deployed:

Map Services Base Map layers, vector and raster, dynamic

Image Services Base Map layers, raster, dynamic Geometry Services

GeoProcessing Services Toolboxes and Extended (SOE)

Geocode Service locater file from ESRI Data and Maps DVDI

AGS Applications Deployed:

Two applications for each development environment

Development of each focused on same set of deliverables

Staged to IIS, Apache and WAS6


16/30

ArcGIS Server Connectivity

Locked DCOM Ports

Port Reporter Utility

Telnet Utility


17/30

AGS Recommendations Organized By IT Architectures

Application Architecture

Technology Architecture

Information Architecture

Security Architecture

Organizational Architecture


18/30

AGS Application Architecture

Three Types of Application Development Scenarios:

Map Centric (Stand Alone) AGS Applications Pure AGS Client side applications using

the ArcGIS Server JavaScript API

Hybrid Java/AGS UI Applications Client side plus server side logic applications

that have layered use cases, require lots of business logic (Java) and a map (AGS UI)

Java/AGS Service Applications Java applications that need limited GIS functionalityand do not require a map, only a need to call AGS backend services (via REST or SOAP)


19/30

AGS Development SDKs and APIs

This was used to

help describe the AGS

development options

to management and

Java developers


20/30

AGS Technology Architecture

AGS Application Server Configuration:

ArcGIS Server for the Microsoft .NET Framework

Web Server Configurations:

IIS for vendor delivered applications

WebSphere for WisDOT developed applications


21/30

AGS Technical Architecture

This was used to

communicate architecture

components to the

architecture review

section (ITSA)


22/30

AGS Information Architecture

Oracle RDBMS:

Traditional ArcSDE Connections vs. Direct Connections

Spatial Views for data optimizations

Cache Strategy

Raster vs. Vector what to cache

Scales how to determine them

Origin - what to use Instances how many to use, when

Cache Directory Location

Space Plan


23/30

AGS Security Architecture

AGS Application Security:

WebSphere (AGS JS API) and IIS (.NET ADF) to use a reverse proxy

AGS Web Service Security:

Secured using AD Domain and LDAP solutions


24/30

Security Architecture Use of a Reverse Proxy

https://webapp-t.dot.state.wi.ushttps://webapp-a.dot.state.wi.us

https://webapp.dot.state.wi.us

https://acceptance.dot.state.wi.us

https://trust.dot.state.wi.ushttps://test.dot.state.wi.us

Intranet:

Extranet:

Novel Access Manager (NAM)


25/30

AGS Organizational Architecture

AGS JavaScript API Training ESRI Instructor Lead

Python Training ESRI Instructor Lead

Java Developers will need to learn the AGS Soap API


26/30

Lessoned Learned

http://blogs.esri.com/Dev/blogs/arcgisserver/archive/2009/10/19/Which-ESRI-Web-mapping-API-should-I-choose_3F00_.aspx

http://blogs.esri.com/Dev/blogs/arcgisserver/archive/2009/03/24/Code-assistance-for-the-ArcGIS-JavaScript-API_3A00_-Aptana-Studio-plug_2D00_in.aspx

Crossdomain.xml

Plug-in support for Flex and Silverlight at WisDOT - NA

Local Install of JavaScript API and JavaScript SDK Help

AGS Web Service Security

AGS JS API Code Assist plug-in for Aptana

Meeting with ESRI regarding Deprecation plans of ADF

Java Developers and the AGS SOAP API for AGS

GP tools from ADF vs. APIs

AGS Warm up IO tool

You can run AGS manger for all AGS instances from Administrators pc Rest API admin tool , must login with all caps = AD\DOTMXM

Windows 2008 64 bit and oracle client version compatibility issues


27/30

ArcGIS Server Implementation

1 AGS Installation and Configuration Installations will be performed on GIS servers at the FDC.

2 AGS Web Service Optimization The results from the AGS Recommendations Project are to be used tocreate best practices to author and deploy AGS web services.

3 AGS Web Testing Methodology This methodology will include a tool set and best practices to record

and play back GIS workflows under user load scenarios to determine scalability of AGS web services

4 AGS Application Guidelines Develop policies and guideline on how to develop AGS application

on the intranet and extranet

5 AGS Security Protocols for AGS web service and application security are be implemented.These implementations are intended to fit into our current security infrastructure.

6 Application Architecture Tuning During the construction iterations of this project, it may be determined

that additional tuning maybe needed to the current architecture or the newly implemented AGS architecture


28/30

AGS Web Service and Application Testing Methodology

Find Software the can record and play back use cases/workflows

Used for three purposes:

AGS Map Service Bench Marking

AGS Application Testing

System Capacity Testing and Planning

Software Tested: OpenSTA

JMeter

Visual Studio Team Test


29/30

Where we are now

Caching Strategy

AGS Infrastructure Stress Testing

AGS Application Staging Scripts

Unit Test Installation and Help Documents

Data Publishing Best Practices

JavaScript API Installations

AGS Installations and Configurations

AGS Security


30/30

Thank You !

Mitch Moline

608.267.7494

[email protected]