Wisdot-Arc Gis Server
Content
Mitch Moline
WisDOT GIS System and Technology Administrator
What¶s in this session «
ArcGIS Upgrade Project DOA/DOT Co-Location Project ArcGIS Server Recommendations Project ArcGIS Server Implementation Project
ArcGIS 9.3.1 Upgrade Project ...
What was Upgraded
Approach Used for Upgrade Lessoned Learned
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
Lessoned Learned «
1 ± Can use silent install switches from this ESRI White Paper
see http://downloads2.esri.com/support/whitepapers/ao_/ArcGIS_9.3_Enterprise_Deployment.pdf
2 - Edit dbtune table (configuration keywords) to use LONGRAW, not ST_GEOMETRY
3 - V9.1 Feature Classes/Datasets are Low Precision, data loading at v9.3.1 are High Precision
see http://support.esri.com/index.cfm?fa=knowledgebase.whitepapers.viewPaper&PID=66&MetaID=1301
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
DOA/DOT Co-Location«
The DET/DOT Server Co-location Project was for DET to support the colocation of all DOT production and production support applications, servers, and devices into the DET Femrite Data Center (FDC) by providing DOT a secure facility, network connectivity, network racks, enclosures (cabinets) and facility resources.
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« 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
Co-Located GIS Server Infrastructure«
Scaled for the implementation of ArcGIS Server Separate Production, Acceptance and System Test Environments
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
ArcIMS/ArcSDE Firewall Rules «
One ArcIMS Installation/Config Opened ArcIMS Servlet Scaled Architecture to support ArcGIS Server
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 the form of alternatives for implementing AGS at WisDOT
Recommendations were determined by «
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
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
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
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-n
ArcGIS 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
RSA (Eclipse)
Using SOAP for ArcGIS Server
Java Web ADF for ArcGIS Server
Tested With RSA (Eclipse)
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 DVD
I
AGS Applications Deployed: Two applications for each development environment Development of each focused on same set of deliverables Staged to IIS, Apache and WAS6
ArcGIS Server Connectivity «
Locked DCOM Ports Port Reporter Utility Telnet Utility
AGS Recommendations Organized By IT Architectures «
Application Architecture
Technology Architecture Information Architecture Security Architecture Organizational Architecture
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 functionality and do not require a map, only a need to call AGS backend services (via REST or SOAP)
AGS Development SDKs and APIs «
This was used to help describe the AGS development options to management and Java developers
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
AGS Technical Architecture «
This was used to communicate architecture components to the architecture review section (ITSA)
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
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
Security Architecture ± Use of a Reverse Proxy «
Novel Access Manager (NAM)
Intranet:
https://webapp-t.dot.state.wi.us https://webapp-a.dot.state.wi.us https://webapp.dot.state.wi.us
Extranet:
https://trust.dot.state.wi.us https://test.dot.state.wi.us
https://acceptance.dot.state.wi.us
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
Lessoned Learned «
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
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-Studioplug_2D00_in.aspx
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 to create 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 scenario¶s 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
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
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
Thank You !
Mitch Moline 608.267.7494 [email protected]
WisDOT GIS System and Technology Administrator
What¶s in this session «
ArcGIS Upgrade Project DOA/DOT Co-Location Project ArcGIS Server Recommendations Project ArcGIS Server Implementation Project
ArcGIS 9.3.1 Upgrade Project ...
What was Upgraded
Approach Used for Upgrade Lessoned Learned
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
Lessoned Learned «
1 ± Can use silent install switches from this ESRI White Paper
see http://downloads2.esri.com/support/whitepapers/ao_/ArcGIS_9.3_Enterprise_Deployment.pdf
2 - Edit dbtune table (configuration keywords) to use LONGRAW, not ST_GEOMETRY
3 - V9.1 Feature Classes/Datasets are Low Precision, data loading at v9.3.1 are High Precision
see http://support.esri.com/index.cfm?fa=knowledgebase.whitepapers.viewPaper&PID=66&MetaID=1301
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
DOA/DOT Co-Location«
The DET/DOT Server Co-location Project was for DET to support the colocation of all DOT production and production support applications, servers, and devices into the DET Femrite Data Center (FDC) by providing DOT a secure facility, network connectivity, network racks, enclosures (cabinets) and facility resources.
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« 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
Co-Located GIS Server Infrastructure«
Scaled for the implementation of ArcGIS Server Separate Production, Acceptance and System Test Environments
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
ArcIMS/ArcSDE Firewall Rules «
One ArcIMS Installation/Config Opened ArcIMS Servlet Scaled Architecture to support ArcGIS Server
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 the form of alternatives for implementing AGS at WisDOT
Recommendations were determined by «
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
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
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
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-n
ArcGIS 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
RSA (Eclipse)
Using SOAP for ArcGIS Server
Java Web ADF for ArcGIS Server
Tested With RSA (Eclipse)
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 DVD
I
AGS Applications Deployed: Two applications for each development environment Development of each focused on same set of deliverables Staged to IIS, Apache and WAS6
ArcGIS Server Connectivity «
Locked DCOM Ports Port Reporter Utility Telnet Utility
AGS Recommendations Organized By IT Architectures «
Application Architecture
Technology Architecture Information Architecture Security Architecture Organizational Architecture
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 functionality and do not require a map, only a need to call AGS backend services (via REST or SOAP)
AGS Development SDKs and APIs «
This was used to help describe the AGS development options to management and Java developers
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
AGS Technical Architecture «
This was used to communicate architecture components to the architecture review section (ITSA)
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
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
Security Architecture ± Use of a Reverse Proxy «
Novel Access Manager (NAM)
Intranet:
https://webapp-t.dot.state.wi.us https://webapp-a.dot.state.wi.us https://webapp.dot.state.wi.us
Extranet:
https://trust.dot.state.wi.us https://test.dot.state.wi.us
https://acceptance.dot.state.wi.us
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
Lessoned Learned «
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
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-Studioplug_2D00_in.aspx
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 to create 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 scenario¶s 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
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
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
Thank You !
Mitch Moline 608.267.7494 [email protected]
