State of Wyoming Department of Environmental Quality

1. Node 2.0 … and Beyond! State of Wyoming Department of Environmental Quality

2. Session Purpose To understand what is a Node, what is Node 2.0 (and what is the alternative). There are 10 types of people in the world...those who understand binary and those who don't.

3. Topics Introduction to the Network and Nodes How to exchange sans Node Node 2.0 Node 2.0 Challenge Grant Project Questions

4. z y x y z x z x y z y x x x What is the Exchange Network? State / Tribe University Internet EPA Internal System XML Schema Network Node Node Client County An Internet and standards-based method for exchanging environmental information between partners.

5. z x y z x y y x y z z x x x A little like the POTS (plain old telephone system) Wassup peeps? Bet its phat! Internet Hello? I got some new bling teenager’s An Internet and standards-based method for exchanging environmental information between partners. my peeps inane gossip

6. z x y y z x z y x z y x x x With Telemarketers! State Internet

7. What does a Node look like?

8. What does a Node look like?

9. Node versus a Node Client Node Client Node • Makes Requests of other Nodes • Responds to Requests • Comes with a closet • Makes Requests of other Nodes • Responds to spilt drinks • Comes with a monitor

10. Super (Shared) Node

11. Node 2.0 An updated specification of the EN’s web service 95% the same as 1.1 – mostly technology upgrades ‘Visible’ improvements include: • Better process notifications • Better service discoverability

12. Multi-State Node 2.0 Challenge Grant Project ECOS (project manager & fiscal agent) with six state environmental agencies: New Hampshire DES Michigan DEQ Nebraska DEQ Oklahoma DEQ Washington DoE Mississippi MS DEQ

13. Project Objectives Fully documented .NET and Java-based Node solutions - complies with Node 2.0 Protocol & Specs and Project Scope of Work. Node and documentation made freely downloadable via open source licensing agreement by any EN partner w/o obligation to share resulting derivative products.

14. Project Objectives Version 2.0 Nodes must: concurrently support version 1.1 and 2.0 Nodes Functional Specs/Network Protocol be able to receive and process transactions from version 1.1 Nodes existing exchanges don’t fail while partners are at different points in the upgrade process project team does not anticipate simultaneous upgrades to Node 2.0 among all EN partners

15. Node 2.0 Features Install instructions/system requirements docs to identify needed hardware, software, and network requirements, including, Web-based Node Administration application, Support for SQL/Oracle for backend db, Support for multi-step processing (e.g., submit to CDX, wait, download results report when ready, email to internal staff), Tools that enable users to configure and implement Exchange Network data flows, Data mapper: map data from source database to flow’s XML schema, XML creator: creates a flow’s XML document based on info provided by data mapper.

16. Simple Plug & Play? …. Ahhhh … No! Some work required to migrate from one Node technology to another …. Switching Node software is easy, … but the hard part is the data flow conversion your current data flows must be made to work under the new Node….

17. Issues to Consider Data Preparation in either the program database or the node database Class Library Programming language/version differences (i.e., .NET 1.1, vs. 3.5 programming) Plug-in Some plug-ins will include “business logic” to perform data validation, write status changes to the database, etc. Setup configuration User rights, user security and alert notification emails

18. QUESTIONS?