1 / 8

The State of Washington Node

The State of Washington Node. Lessons Learned from a Production Node and Beyond Guy Outred Windsor Solutions. Washington Department of Ecology Node. FRS data flow in production October 2003 .Net & SQL Server 2000 Winner of the Microsoft Government Productivity Solution State Award

venice
Download Presentation

The State of Washington Node

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The State of Washington Node Lessons Learnedfrom a ProductionNode and BeyondGuy OutredWindsor Solutions

  2. Washington Department of Ecology Node • FRS data flow in production October 2003 • .Net & SQL Server 2000 • Winner of the Microsoft Government Productivity Solution State Award • Demonstrated Node Configuration available • Being implemented at Kansas DHE • .Net & Oracle RDBMS Contact: Debbie Stewart dste461@ecy.wa.gov (360) 407-7048

  3. Lessons Learned – Node Considerations • XML documents are not bandwidth friendly • WA Facility ID Full Data Solicitation • 100 Mb XML File = 4 Mb compressed file • RPC, but Doc/Literal compatible • Doc/Literal will be a likely future use • Ideally, incorporate a Doc/Literal -> RPC translator

  4. Lessons Learned – Node Considerations • Staging Database and/or Live Connection • Staging Database: • Replication into Schema format – performance • Additional security • Live Database Connection: • Real-time access to date • Capable of data manipulation • (i.e., for incoming data)

  5. Node Administration Capabilities • Flow configuration • Notification, notification • Searchable activity logging • Document management • Scheduling • Automatic XML (de)compression

  6. A Consideration from Beyond your Node • Employ a ‘Service Based Approach’ to new systems • Non-node data management systems may have future flows • Consider web services to broker database interaction

  7. HTTP Proxy vs. DMZ Architecture DMZ Topology Internet DMZ Intranet EPA Supporting System Databases External Router & Firewall Internal Router & Firewall Web Server Node Database Partner

  8. HTTP Proxy vs. DMZ Architecture Reverse Proxy Topology Internet Intranet EPA HTTP Proxy Server Supporting System Databases External Router & Firewall Web Server Node Database Partner

More Related