Hydrologic Information System Workgroup Server: Software Stack, Deployment, Operation Thomas Whitenack, David Valentine, Ilya Zaslavsky SDSC

HIS Team WATERS Testbeds WATERS Network Information System

This Presentation ► Slides  Deployment overview  Content of the server: COTS + HIS software  Registering your observation networks  Server administration and updates  Current status, and licensing ► Workgroup server demonstration ► Q&A

Deployment Overview ► HIS Server Machines are staged at SDSC  Base software components installed (Microsoft, ESRI)  All HIS components installed: ► ODM ► Web Services and templates ► DASH = Data Access System for Hydrology ► + additional tools ► Servers can be accessed remotely, before shipped to testbeds

Windows 2003 Server 4 GB Ram 500 GB Disk Quad Core CPU SQLServer 2005 IIS (Internet Information Server) DASH ArcGIS Server Visual Studio 2005 WaterOneFlow Web Services ArcGIS 9.2 GIS Data Mxd Services ODDataLoader ODM tools COTS Software HIS Applications Data NWIS DV NWIS IID Your ODM

C: 50Gb O: 230Gb P: 180Gb System Disk Operating System Program Files - SQL Server - IIS - Visual Studio - ArcGIS - ArcGIS Server Data Disk GIS Data SQL Data (ODM) HIS software -WaterOneFlow Web Services - DASH - ODM Data Loader -ODM Tools -WSTestPage

SQL Server ODMs and catalogs. All instances exposed as ODM (i.e. have standard ODM tables or views: Sites, Variables, SeriesCatalog, etc.) NWIS-IID NWIS-DV ASOS STORET TCEQ BearRiver... Spatial store Geodatabase or collection of shapefiles or both NWIS-IID points NWIS-DV points ASOS points STORET points TCEQ points BearRiver points... My new ODM My new points More databases More synced layers DASH Web Application Background layers (can be in the same or separate spatial store) WOF services Web services from a common template NWIS-IID WS NWIS-DV WS ASOS WS STORET WS TCEQ WS BearRiver WS... My new WS More WS from ODM-WS template USGS NCDC EPA TCEQ Web Configuration file Stores information about registered networks MXD Stores information about layers WSDLs, web service URLs Connection strings Layer info, symbology, etc. ODM DataLoader WORKGROUP HIS SERVER ORGANIZATION STEPS FOR REGISTERING OBSERVATION DATA

New network registration steps Using the ODM DataLoader, load your data into a blank ODM instance (this will create all ODM tables, including Sites, Variables and SeriesCatalog that HIS application relies on) Copy Web Services template to a new folder, edit the template web.config file to point to the new ODM, test to make sure the new service works as expected Create a point layer (a feature class in GDB, or a shapefile) from the new ODM’s Sites table using the GetSitesTool. Add the point layer to the MXD document, specify symbology, scale-dependent rendering, etc. Add information about the new ODM, the associated web service, and the associated point layer, to HIS configuration file (see the first slide for the exact content) Restart the HIS service

Loading Observation data ► Make a copy of the ODM template database ► Data to be loaded is in an Excel readable format (xls, txt, csv). ► Use ODM DataLoader to load data 1

Structure of ODM DataLoader 1

Configure WaterOneFlow Web Service ► Create copy of Web Services from template: Make a copy and rename ► Edit the web.config file using VS or notepad 2

Extract Geometries from ODM ► GetSites tool extracts sites using Lat / Long values ► Add shapefile to service document 3

Add Sites to Map Service Document ► Symbolize Points ► Specify Scale at which points are visisble 4

Configure DASH ► Edit HISNetworks.xml found in the bin of the HIS Application. ► Copy/Paste existing “HISNetwork” block and edit to change: ► NetworkID, NetworkCode, ► NetworkName, ► NetworkConnectionString ► NetworkServicesWSDL ► NetworkServicesURL ► NetworkServicesGetValuesURL ► CreatedDate ► LastUpdateDate ► ResponsibleParty ► Disabled ► DisableDate 5

Refresh Map Service ► Use ArcCatalog to Stop and start the Map service 6

Deployment Schedule ► 8 servers received and are currently being configured; 9 th server is expected ► This week: Remote access to at least one server given to a testbed (Utah)  It only depends on licensing at the moment ► After testbeds review the machine setup, the servers will ship  (some testbeds may choose to keep machine longer at SDSC so we can assist with ODM loading).

Administration and Updates ► Admin accounts: local + remote (for SDSC, troubleshooting) ► Updating software:  DASH and ODM Tools ► New versions on web site, with installation instructions  ODM Data Loader ► ClickOnce deployment  Regular software updates and patches for COTS ► Need to first try at SDSC; post on administrators blog ► Updating databases:  Regularly updated at SDSC; available to workgroups via web services and direct connection to disrupter.sdsc.edu ► Updating web services  New templates posted on web site, with instructions