FISH PASSAGE CENTER. 847 NE 19 th Ave., Suite 250, Portland, OR Phone: (503) Fax: (503)

Transcription

1 FISH PASSAGE CENTER 847 NE 19 th Ave., Suite 250, Portland, OR Phone: (503) Fax: (503) MEMORANDUM TO: Jim Ruff, NPCC Nancy Leonard, NPCC Adam Gittler, ACME Consulting FROM: Michele DeHart DATE: February 13, 2015 RE: Fish Passage Center Web Site Structure In response to your request, the Fish Passage Center (FPC) staff has developed the following brief description of the FPC Web site structure and tools. The FPC Web site is controlled by a series of four computers: WebFarmControl, Swordfish, Swordfish2 and Swordfish3. This configuration is known as a server farm. A server farm is a group of computers acting as servers and housed together in a single location. A server farm is sometimes called a server cluster. A Web server farm can be either (1) a Web site that has more than one server, or (2) an Internet service provider that provides Web hosting services using multiple servers. In a business network, a server farm or cluster might perform such services as providing centralized access control, file access, printer sharing, and back-up for workstation users. The servers may have individual operating systems or a shared operating system and may also be set up to provide load balancing when there are many server requests. In a server farm, if one server fails, another can act as back-up. On the Internet, a Web server farm, or simply Web farm, may refer to a Web site that uses two or more servers to handle user requests. Typically, serving user requests for the files (pages) of a Web site can be handled by a single server. However, larger Web sites may require multiple servers. \2015_files\26-15.docx

2 Web farm is a term that is also used simply to mean a business that performs Web site hosting on multiple servers. The reason we use this format is to allow better access to our Web site during peak demand times. The way this works is you have a main sever, in our case WebFarmControl, which acts like a traffic cop. When a request to access our Web site is initiated it looks at the request and sends it to one of the other three servers. When the next request arrives it is directed to another server, and so on. This technique is called load balancing. User 1 User 2 User 3 User 4 User 5 FPC Router User 1 WebFarmControl User4 User 2 User 5 User 3 Swordfish Swordfish2 Swordfish3 Page 2 of 5

3 The servers are exact duplicates of each other as far as software and data stored on each, so changes have to be made on only one of them and it will automatically get updated on the others. The main server (WebFarmControl) monitors the others and when it detects changes it distributes the change to the other computers in the group. The servers are configured as follows: WebFarmControl Intel Core i GHz Windows Server 2008 R2 Ent, SP GB Ram 1 TB hard drive Swordfish Intel Core 2 Duo 3.0 GHz Processor Windows Server 2008 R2 Ent, SP GB Ram 500 GB hard drive Operating System 1 TB hard drive Web site data Swordfish2 Intel Core 2 Duo 2.93 GHz Processor Windows Server 2008 R2 Ent, SP GB Ram 500 GB hard drive Operating System 1 TB hard drive Web site data Swordfish3 Intel Core 2 Duo 2.66 GHz Processor Windows Server 2008 R2 Ent, SP GB Ram 150 GB hard drive Operating System 150 GB hard drive Web site data FPC.org Web Site Software Stacks The FPC Web site consists of four main components: (1) the Web server and database, (2) the monitoring map application and spatial data software stack, (3) map-based queries, and (4) data queries and graphs. The Web server software sends our Web pages to our audience and the database server holds the salmon and river data that is used in the daily reports, data queries and graphs. Our current Web server software is Microsoft IIS 7 and Apache 2.0. Our current database server runs Microsoft SQL We are in the process of updating our Web site and have developed some prototype applications using different software stacks. For instance, the Web servers for the prototype applications are Apache 2.2 and Microsoft SQL Page 3 of 5

4 On our current Web site, we have a monitoring map application designed to allow users to spatially search for hatcheries and their associated release sites. The map zooms to the extent of the selected hatchery and its associated release sites, and allows the user to download release data. The software stack for the hatchery map application is: php (5.2), mapserver (5), postgresql (8.4), postgis (1.8), javascript (1.7). We have developed a prototype monitoring map application which includes additional monitoring sites such as weirs, dams, traps, redd sites, redd transects, PIT-tag sites, and Comparative Survival Study (CSS) tag and release sites. The application also includes important salmon distribution information or significant salmon geographical features (i.e., streams containing salmon, evolutionary significant units, major population groups, populations and spawning areas). This application allows the user to spatially search for monitoring sites within the salmon geographical areas, and link to graph queries with additional data for selected sites or directly download data. The software stack for the prototype monitoring map application is: php (5.4), mapserver (6), Apache (2.2), pmapper (4/3 and 5), postgresql (9.1), postgis (2.1), openlayers (2.13) and javascript (1.8). Our Web site has many queries which can be used to graph and download program information. Areas of available information include the smolt monitoring program, hatchery data, comparative survival data, adult dam count data, river flow and spill data, spawning data, and other data including documents written by the FPC staff (annual reports, weekly reports, memorandums, system operations requests, joint technical memorandums, fish passage facility reports, etc.). The software used on our current Web site includes: asp, aspx, tchart 4, javascript and swiftchart. We have developed several prototype data queries using newer components which allow users to interactively see individual chart data values, turn off/on a data series, download charts in several formats, sort table columns, print tables, and allow for table pagination. These prototypes enhance interactive form elements and data validation. The software stack used in these prototype data and graph queries includes: php (5.4), highcharts.js (4), dojo.js (1.9) and jquery (1.8). In addition to graph-based queries, we have several map-based queries that allow users to map and download specific datasets (e.g., number of PIT-tagged CSS fish released by site, CSS annual in-river estimates by river segment, etc.). The software stack for the current map-based queries includes: asp, aspx, mapserver, postgresql (8.4), postgis (1.8) and javascript (1.7). We have developed several new map-based queries and temporal queries. These prototype queries allow users to spatially map, graph, and select either salmon species geographies (with a display of related data such as abundance, survival, etc.) or specific monitoring locations (with related data such as hatchery releases, river segments with survivals, etc.). Some of these queries are also temporal queries, allowing the user to see how the data changes spatially over time. The software stack used for these queries includes: php (5.4), mapserver (6), pmapper (4.3 and 5), postgresql (9.1), postgis (2.1), geoserver (2.5), openlayers (2.13), geoext (2), weave (1.7), leaflet (.7), timemap (2) and javascript (1.8). Page 4 of 5

5 We post daily reports (and some other queries) on our Web site about smolt abundance; condition and survival; river flow and spill; adult dam counts; and other reports. These reports use a different software stack. See the attached Web Projects report for specific information on these applications. Page 5 of 5

6 Attachment to Memo regarding The Fish Passage Center Web Site Structure Contents 1. Real Time versus Historic Water Temperature Graphs... A1 A. Historical... A1 B. Current... A2 2. Adult Return and Smolt passage PIT-Tag Data and Graph... A4 3. Spill Season Update.NET Application... A5 4. SQL Server Integrated Service... A6 5. Adult Counts Posting Application... A6 6. TDG/Spill Report Text Generator... A6 7. RSS feeds for Adult Counts, SMP32.NET batch posting and GBT Batch... A7 8. SMP Upload.NET... A9 \2015_files\26-15attach.docx

7 1. Real Time versus Historic Water Temperature Graphs NETTempgraph.aspx.NET Application Current Version Visual Studio 2008 on HAMMERHEAD There are 2 projects current and historical. A. Historical Deployment Location: SWORDFISHXXX /Inetpub/wwwroot/river/tempgraphsnet Developed: HAMMERHEAD// C:/Visual Studio 2008/Chart Page A1

8 B. Current Deployment Location: SWORDFISHXXX /Inetpub/wwwroot/river/tempgraphssl Developed: HAMMERHEAD (C:/Visual Studio 2010/NETtempgraph) Visual Studio 2010 C# TelerikRadControls for ASP.NET AJAX: Q Version: Telerik RadControls for Silverlight: Version: SQL Server 2008 Page A2

9 Applications involved to provide data ChartPainter.exe (37) as a job at 1:00 PM ConsoleWFAWaterTemperatureCapture.exe (36) Task Scheduler as a job at 8:45 AM + every 4 hours for each day WPFGaugePainter PrjFileCollector.exe (7) 6:00 AM; 8:00; 9:00; 10:00; 11:00; 12:00 noon; 1:00 PM; 2:00; 3:00; 4:00; 5:00; 6:00 using sp_insertfishpicture posting images into FishImages table using usp_postwatertemp populates PostWeather with Water temp and charts using sp_insertthermpicture posting images into PostWeather table using spgetsumdailyadults activates trigger (UpdateActive) that runs sppostfishcounts from fpclive to populate PostFishCounts (Adult Counts and Chart images) fpclive.fishimages SaveWeatherPicture Insert original images NETTempgraph Web App. Page A3

10 2. Adult Return and Smolt passage PIT-Tag Data and Graph (Visual Studio 2005.NET Application on GREENFISH) Developed: FISHPUMP2 (inetpub/wwwroot/webform2005/webform2005) using Visual Studio 2005 Deployment Location: SWORDFISH XXX/Inetpub/wwwroot/WebForm2008/ Development Location: Update WebForm2005.dll inside bin folder from C:/inetpub/wwwroot/webform2005/webform2005/bin Supplements by: 1. Import data: (ConsoleGetMailData.exe) posting adults and smolt from PITAGIS and runs spfastcountdetection 'XXXX' to populate passagegraph table 2. ChartGenerator: FishTChart.exe Visual Studio 2005 TelerikRadControls for ASP.NET: Q RadTabStrip Page A4

11 3. Spill Season Update.NET Application (MAINCHART.ASPX on GREENFISH Visual Studio 2008 App) Deployment Location: SWORDFISHXXX \Inetpub\wwwroot\WebForm2.0\ Project Location: //GREENFISH G:/Inetpub/wwwroot/WebForm2.0 Use Web Site project to open G:/Inetpub/wwwroot/WebForm2.0 Supplements by: ConsoleImportcoe12highavg.exe ConsoleImportTdg_spill.exe ConsoleSpillChart.exe applications. Special requirements: BasicFrame.WebControls.BasicDatePicker.dll, BasicFrame.WebControls.BasicDatePicker.xml inside bin directory. BasicFrame.WebControls.BasicDatePicker needs to be installed ((//HUMPBACK/historicaldata/apps/BDPLight) More detail: Visual Studio 2008 C# EO.Web.dll BasicFame.WebControls.BasicDatePicker.dll SQL Server 2008 Page A5

12 4. SQL Server Integrated Service SQL Server 2008 Visual Studio 2005 Source Code Backup Location: Developed on FISHPUMP2 VisualStudio2005/Projects/ Ch2 Package: C:/Visual Studio 2005/Projects/Ch2/Ch2/bin/TableToXls.dtsx Creates AdultsCurrentYear.txt for CRITFC adult counts data request and AdultsCurrentYearBackup.txt into SWORDFISH2. Second project (VisualStudio2005/Projects/Ch2NotCurrentYear/Ch2NotCurrent/ Ch2NotCurrentYear.dtproj) creates AdultsHistorical.txt using the AdultsHistorical package. 5. Adult Counts Posting Application Collecting adult counts from different sources into SQL3-MAIN3.PITTAG.HistFishTwo table; creates histfishtwo_7day-ytd_adults.htm web page. SQL Server 2008 Visual Basic TDG/Spill Report Text Generator Generates: dgassum.txt and dgassum_wa.txt for web page report. Visual Studio 2008 C# Page A6

13 7. RSS feeds for Adult Counts, SMP32.NET batch posting and GBT Batch (rssadultcounts.aspx, rsssmpbatch.aspx rssgbtbatch.aspx, rsswatertemperature.aspx on HAMMERHEAD Visual Studio 2010 App) Page A7

14 Deployment Location for RSS feeds: SWORDFISHXXX/Inetpub/wwwroot/rss/rssAdultCounts.aspx Visual Studio 2010 C# TelerikRadControls for ASP.NET AJAX: Q Version: SQL Server 2008 Page A8

15 8. SMP Upload.NET Developed: Hammerhead//C:/Visual Studio 2010/SMPUpload Uploads SMP xml files into P:/SMPBatches (WEBSERVER//SMPBatches) Visual Studio 2010 C# TelerikRadControls for ASP.NET: Q ASP.NET AJAX Running on Webserver// wwwroot/smpupload Page A9