1. Whad’ya Node ? Mentoring Conference New Orleans, LA March 1, 2005 Node Building 101

2. Presenters Dennis Burling Nebraska Dept. of Environmental Quality Glen Carr Oregon Dept. of Environmental Quality Kevin Jeffery Windsor Solutions, Inc

3. 30 Minute Guide Audience Partners who are yet to implement a Node Partners who have implemented a Node, but are interested in alternative approaches Partners looking to advance their Node implementation

4. Contributors Alesia Whitney-KnightIowa Department of Natural Resources Cheryl FranklinIndiana Department of Environmental Management David BlocherMaine Department of Environmental Protection David H. EllisMaine Department of Environmental Protection Dennis BurlingNebraska Department of Environmental Quality Glen CarrOregon Department of Environmental Quality Leslie BrennanNew York Department of Conservation Mary BlakesleeEnvironmental Council of States Mitch WestOregon Department of Environmental Quality Robert E. WilliamsMaine Department of Environmental Protection Tom AtenWisconsin Department of Natural Resources

5. What is a Network Node ? “ A simple environmental information Web service that initiates requests for information, processes authorized queries, and sends/receives the requested information in a standard format. ”

6. Getting Started Research the Network –Exchange Network Web Site (www.exchangenetwork.net)www.exchangenetwork.net –CDX Web Site (www.epa.gov/cdx)www.epa.gov/cdx –EDSC Web Site (www.envdatastandards.net)www.envdatastandards.net –ECOS Web Site (www.ecos.org)www.ecos.org Consult Mentoring States Planning what data to exchange –Current systems –Maturity of flow –Data sharing priorities Securing agency commitment –Making the business case –Securing sponsorship

7. Don’t Reinvent the Wheel Early implementers invested significant effort in creating and troubleshooting the technology required to implement a Node and exchange data. Exchange Network goal to reuse research and development work wherever possible. Demonstrated Node Configurations (www.exchangenetwork.net).www.exchangenetwork.net Reuse of existing solutions can accelerate Node deployment and reduce the up front investment. Where possible use existing applications to streamline development but be prepared to adapt to your environment.

8. Implementing Your Node

9. Review existing agency architecture standards. Define the physical environment including hardware, hosting platform and network components. Establish appropriate network security architecture. Identify the logical components including middleware, applications and frameworks. Select development, management and support tools.

10. Implementing Your Node Minimum functionality per Network Node specifications. Consider more advanced Node capabilities. Ability to troubleshoot an exchange. Monitoring use of the Node by other partners. Administering security (NAAS and local). Scheduling data exchanges. Email notifications for Node functions. Request costing.

11. Implementing Your Node Develop basic Node Web service interface to process incoming requests. Develop Node administration functions (user accounts, transactions, logs, etc). Install security identification certificates on host server to support SSL (EPA can provide). Establish “master” and “operator” NAAS accounts (Exchange Network Security Policy).

12. Implementing Your Node If possible use a dedicated test environment. Test using the EPA CDX test client and/or other testing applications (www.exchangenetwork.net/node/dev_toolb ox).www.exchangenetwork.net/node/dev_toolb ox Ask CDX Help Desk to assist with testing connectivity and functionality. Test with parallel data flow development. Perhaps use another partner’s Node for added validation of interoperability.

13. Implementing Your Node If possible, maintain separate production and test Node implementations. Dedicate support staff time to monitor Node operation (between ¼ and 1½ FTE). Training on use and operation of the Node.

14. Common Testing Issues Compatibility with the Network Node specifications Lack of physical connectivity to the Internet Incorrect implementation of the WSDL Incorrect configuration or lack of support for NAAS security. Capability to respond to and process predefined data queries Inappropriate configuration of the Node to support a particular query. Data request exceeds server capacity. Incompatibilities between heterogeneous Node platforms.

15. Deciding on Your Technical Architecture Physical Components of Node Architecture Logical Components of the Node Architecture Management, Support and Extensibility Tools Node Functional Capabilities

16. Physical and Logical Components Network Topology Dedicated vs. Shared Server Separate Testing Environment Staged RDBMS Application architecture (e.g.,.Net, Java, XAware)

17. Node Functional Capabilities Administration interface. Separation of the Node and the individual data exchange or flow implementations. Support for the Exchange Network XML Document Header File on an exchange-by-exchange basis. Support of authentication and authorization through both NAAS and Local Security. Persistent attachment management. Support for both incoming and outgoing data flows. Support Secured Sockets Layer (SSL) through the use of recognized certificate authorities.

18. Discussion