1. Hydrologic Information System Deployment and configuration

2. DASH AGS Server IIS Windows 2003 Server 4 GB Ram 1 TB Disk Quad Core CPU SQL Server VS 2005 WaterOneFlow Web Services ArcGIS 9.2 GIS Data Mxd Service ODM LoaderODM tools ODM Current Deployment Architecture Direct DB connection

3. What are the possible variables for the selected set of sites? Which of these sites have values for the selected variable? Multi-station selection Functionality which still requires direct database access

4. WaterOneFlow Web Services Add methods: GetVarsAtSites(String[] siteids) GetSitesVar(String[] siteids, strVar) DASH AGS Server IIS Windows 2003 Server 4 GB Ram 1 TB Disk Quad Core CPU SQL Server VS 2005 ArcGIS 9.2 GIS Data Mxd Service ODM LoaderODM tools (Future) Web Services Architecture WaterOneFlow Web Services are extended ODM

5. For each network: NetworkID, NetworkCode, NetworkName, NetworkConnectionString NetworkServicesWSDL NetworkServicesURL NetworkServicesGetValuesURL CreatedDate LastUpdateDate ResponsibleParty Disabled DisableDate 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 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.

6. 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 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. 2 6 5 3 ODM DataLoader 1 4

7. 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 or from GetSites web service (using GetSitesTool – this will also test the service) 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 6 5 4 3 2 1

8. 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

9. Structure of ODM DataLoader 1

10. 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

11. Extract Geometries from WebService ► GetSites method returns sites with Lat / Long values ► Use GetSitesTool (under development) to Create shape file. ► Add shapefile to service document 3

12. Add Sites to Map Service Document ► Add Data ► Specify rendering properties 4

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

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

15. Deployment schedule ► March 29: 8 servers received; 2 are being configured ► April 9: review ► April 16: final call for components ► Week of April 23: shipping to 7 test beds

16. Content C: 50Gb O: 270Gb P: 180Gb System Disk OS Program Files - SQL Server - ArcGIS - ArcGIS Server HIS - OD Data Loader - ODM Tools Wwwroot - DASH - web service test tool Data Disk ODM Databases Web services GIS Data Tutorials, how-tos Work area Backup and experiments Virtual server OS backup image Another work area

17. Content2 C: 50Gb O: 270Gb P: 180Gb System Disk OS Program Files - SQL Server - ArcGIS - ArcGIS Server HIS - OD Data Loader - ODM Tools Data Disk ODM Databases GIS Data Work area HIS software and backup Virtual server OS backup image WaterOneFlow Web Services Web Apps WSTestPage DASH Tutorials, how-tos Additional work area

18. Administration ► Local administrator ► Remote admin account (for SDSC) ► Need a GetNetworks service

19. Updates ► 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 ► Databases:  Regularly updated at SDSC; available to workgroups via web services and direct connection to disrupter.sdsc.edu ► Web services  New templates posted on web site, with instructions