1 / 24

Network Node Model for Environmental Information Exchange

Network Node Model for Environmental Information Exchange. California Environmental Health Tracking Program Technical Team Meeting #1 March 5, 2003. Gary Arstein-Kerslake, Calif. Environmental Protection Agency

milt
Download Presentation

Network Node Model for Environmental Information Exchange

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. Network Node Model for Environmental Information Exchange California Environmental Health Tracking Program Technical Team Meeting #1 March 5, 2003 Gary Arstein-Kerslake, Calif. Environmental Protection Agency Based upon a presentation delivered by Joe Retzer, Office of Environmental Information, U.S. Environmental Protection Agency at the Open Forum on Metadata Registries, January 2003

  2. Why Do We Need …an Environmental Information Exchange Network? • Inefficient access to existing information resources • Public expectation of increasing capabilities to diagnose and prevent problems, especially cross-media

  3. What Do We Need …a Solution that is… • Low-cost:Uses an Infrastructure that is already largely in place • Minimally invasive:Does not require that existing systems be swapped out • Standards-based:e.g., industry-defined or formal standards body (W3C) • Extensible and flexible:e.g., uses an eXtensible Mark-up Language (XML)

  4. What is an Environmental Information Exchange Network? • Under the Environmental Information Exchange model, the ‘network’ consists of a collection of Nodes which offer a simple Web service that initiates and responds to requests for environmental information • The requests and responses use common formats expressed in eXtensible Markup Language (XML)

  5. What is a Network Node?

  6. Web Services • Information sources/application components whose functionality and interfaces are exposed to consumers using Web technology standards including XML, SOAP, WSDL, and HTTP • Services offered computer-to-computer, via defined formats and protocols, in a platform-independent & language-neutral manner …In contrast to Web Browser-based interactions or platform-dependent technologies

  7. Basic Exchange Node Responsibilities • Must assume increased data stewardship responsibilities • Must collaborate with others to develop data/transaction standards and trading partner agreements • No change to existing systems req’d … But, must “map” internal system data to comply with data exchange templates (DET or XML schemas)

  8. Technical Framework Components • Security (HTTPS, SSL) • Data Standards (e.g., EDSC) • Data Exchange Templates (DETs) • Registry/Repository (UDDI - Universal Description, Discovery and Integration) • Nodes (Web server w/ access to database) • Exchange Process • Connecting to Existing Systems • Bringing the Pieces Together: Implementation Projects

  9. Node Information Exchange Process 1a. Validates against Input Schema REQUESTOR NODE 1. Sends authorized service request to node 5. Receives validated data DATABASE 2. Node processes request, sends queries 4. Node receives and processes data 3. Database processes query and sends data back Internet HTTP & HTTPS Agency Network 4a. Validates against Output Schema

  10. Network Exchange Protocol • Set of rules that govern the generation and use of valid service requests and responses on the Network • Identifies the standards (e.g., SOAP, WSDL) and provide additional rules that govern how these standards are implemented on the Network

  11. Technical Components/Standards • UDDI - Universal Description Discovery and Integration Standard • WSDL - Web Service Description Language • SOAP - Simple Object Access Protocol • XML - eXtensible Markup Language • HTTP – internet transport protocol • SSL – Secure Sockets Layer Web Service Security (and PKI)

  12. Discovery UDDI Description WSDL XML Messaging SOAP, XML Transport HTTP Security SSL Network Architecture Web Services Protocol Stack

  13. Security (HTTPS/SSL, PKI, etc.) Transport Protocol (HTTP) XML Messaging (SOAP) Envelope SOAP Header SOAP Body XML Schema Network Exchange Protocol Message Structure • Types of XML Messages • XML Message - SOAP • Message Payload - XML • Transport - HTTP • Security – HTTPS/SSL Example from www.geographynetwork.com: “ArcWeb USA is deployed through Internet standards including HTTP, WSDL, UDDI, and XML … [Using] XML-based Simple Object Access Protocol (SOAP) to communicate.”

  14. US EPA Central Data Exchange (CDX) Node Status • Working Prototype Nodes built from the V.8 and V.9 Specifications • Node Test Tools Created to Validate Each Node Method / Function • Prototyped Central Authentication Server • Building CDX Requestor/Scheduler • CDX Web Service Tools Assessments • Tools continue to improve • Support of various protocols is not complete • Writing Node 1.0 Production Specification

  15. Bottom Line • Web services are being built now • Workable standards are in place • Existing WS Tools are adequate and they continue to improve • US EPA will be designing central functions as needed to limit redundancy/cost

  16. Node Progress: 2000-2001 Simple Prototype Nodes • Alpha Phase: State agencies developed simple prototype Nodes as part of the Network Node Pilot Project • Participants: • Delaware (DNREC) • Nebraska (NDEQ) • New Hampshire (NHDES) • Utah (UDEQ)

  17. Node Progress: 2001- early 2002 Functional “Beta” Nodes • Beta Phase: • Six State agencies • Alpha Phase States • Florida DEP • New Mexico Environment Department • Central Data Exchange • The Beta Node project was a more robust test and implementation of technologies, security and standards

  18. Current V1.0 Node Tools • Oracle 9 IAS • IBM WebSphere • XAware • Microsoft BizTalk • Microsoft .NET • BEA Web Logic • SQLDATA

  19. Security • SSL Transport Encryption • Central Authentication Service • Authentication Tokens • Phased Approach

  20. Network Node V1 • Team is refining specifications/requirements • CDX and States are enhancing node implementations • Holding regular calls to support new States

  21. WA WA WA MT ME ND OR OR OR MN MN MN VT NH ID WI WI WI SD MA NY NY NY WY CT MI RI 0101010101010101010 0101010101010101010 1010101010101010101 1010101010101010101 IA PA PA PA NJ NE NV OH IN IN IN MD MD MD IL DE UT UT UT CO WV VA CA KS MO MO MO KY NC TN OK OK OK AZ AZ AZ AR NM NM NM SC AK GA GA GA AL MS MS LA TX TX TX HI FL Standards Are... • Key to consistency among exchange templates that define the flows • Essential for all participants if we hope to be able to send priority data across the Exchange Network by 2004

  22. Data Standards • EDSC in March 2000 Established List of Priority Criteria for Standards Development • Contributes to public health protection • Facilitates information re-use • Reduces cost or burden • Baselines environmental information • Portrays program performance

  23. EDSC Progress… • Adopted - Eleven • Date, Biological Taxonomy, Chemical Identification, SIC/NAICS, Facility Identification, Latitude/Longitude • Permitting I, Enforcement/Compliance, Tribal Identification , Contact Info., Reporting Water Quality Results for Chemical and Microbiological Analytes • Under Development • Federal Facility • Permitting II • Environmental Laboratory Results

  24. End of Presentation • Questions? • Contact Information:Gary Arstein-KerslakeAgency Information Officer, Cal/EPAgarstein@ciwmb.ca.gov

More Related