Node Interoperability FAQs

Answers to the following Frequently Asked Questions on Exchange Network Node Interoperability and upgrading to Node v2.1 are current as of November 28, 2011. This page will be updated as more information becomes available. If you have a question that is not answered by this FAQ, please email it to the Exchange Network Coordinator.

Interoperability Open Call Summary
March 24, 2011

What are the node interoperability issues?

Exchange Network developers discovered that two issues were preventing certain Exchange Network Nodes and Node Clients from successfully communicating with one another, or “interoperating.” For specific details on the nature of these issues, please see the Summary on Exchange Network Node Interoperability.

How am I affected by the interoperability issues?

The first thing you should know is that these issues do NOT affect any Nodes or Node Clients built against version 1.1 of the Exchange Network Node Functional Specification. Only Nodes and Node Clients built on version 2.0 of the Specification are affected.

If you are a developer or a user of a Node or a Node Client based on the version 2.0 Specification, you may need to update your product to comply with new rules intended to address the interoperability issues. Exchange Network Governance has documented these new rules in the Exchange Network Node Functional Specification (v2.1) and the Exchange Network Protocol (v2.1).

What Exchange Network products and tools are affected and what will I need to do?

Again, these interoperability issues do NOT affect any Nodes or Node Clients built against version 1.1 of the Exchange Network Node Functional Specification. The table below identifies some commonly used Exchange Network tools, anticipated impacts, and information for users.

Product or Tool
Change Required?
Information for Users
All Node and Node Client installations based on v1.1 Node Specification
No
You do not need to make any changes to Nodes or Node Clients built against v1.1 of the Exchange Network Node Functional Specification. Data exchanges that are currently running on v1.1-based Nodes and Node Clients are not affected.
OpenNode2
Yes
Exchange Network Governance and ECOS worked with Windsor Solutions, Inc., to make available a free updated version of OpenNode2 along with detailed installation instructions. Both a .NET and Java version are available. Download the updated installation packages and the Installation Guides here.
EN-Node
Yes
Exchange Network Governance and ECOS worked with enfoTech, Inc., to make available a free updated version of the EN-Node along with detailed installation instructions. Both a .NET and Java version are available. Download the updated installation packages and the Installation Guides here.
Custom-developed Nodes and Node Clients
Maybe
The Exchange Network is working to identify Partners that use custom-built Node or Node Client solutions, so that we can
work with you to determine whether they are impacted by the interoperability issues. If you have yet to hear from the Exchange Network, please contact Kurt Rakouskas.
Windsor Solutions’ Node Client Lite2
Yes
Users of this product will be affected sending data to a 2.0 Node endpoint at EPA’s Central Data Exchange. Windsor is aware of this and will have update details available at a later date. In the interim, users can still use Node Client Lite2 to send data to a Node based on the v1.1 Node specification.
Gold Systems’ AQWMS Application
No
Users will not be affected. The application has an embedded Exchange Network Client based on the v1.1 Node Specification.
WQX Web
No
Users will not be affected. The application has an embedded Exchange Network Client based on the v1.1 Node Specification.
Exchange Network Services Center
No
The EN Services Center is a tool for making manual data submissions to EPA. EPA will make any necessary adjustments to this tool to ensure that users are not impacted.
SDWIS/FedRep
No
Users will not be affected. SDWIS/FedRep is used to submit data to EPA’s Safe Drinking Water Information System (SDWIS). The Application has an embedded Exchange Network Client based on the v1.1 Node Specification.

 

I use one of the affected products. What do I need to do?

You will need to perform a straightforward download and reinstallation. You may also need to change the endpoint URLs for some of your data flow.

  1. Using the links in the table above, locate and download the appropriate Installation Guide, which details the process for reinstalling your Node.
  2. Download the updated product installation files. Consult the available Installation Guide for specific instructions on reinstalling your product.
  3. If you are currently sending data to a Node 2.0 endpoint at CDX, you will need to point your Node to a new 2.1 endpoint URL after installing your updated product. Please consult the list of Node endpoint URLs at CDX to determine where to direct your data. If your data flows are currently configured for use with Node 1.1 endpoints, you will not need to make any changes at this time.

When will I need to update my affected product?

Exchange Network Governance is committed to implementing a smooth and complete fix to the Node interoperability issues. As such, they ask all affected Partners to update their products by January 31, 2012.

I work with an organization that uses the Exchange Network to submit data to EPA’s Moderated Transaction System (EMTS). Will I be affected by the interoperability issues?

No. EPA’s Central Data Exchange (CDX) is making provisions to ensure that industry reporters to EMTS will be unaffected.

Will EPA program offices need to make any modification to their Nodes?

No. The Nodes managed by EPA program offices are not affected.

What resources are available to help me update my affected products?

Exchange Network Governance worked closely with product developers to ensure that timely updates and installation instructions were made available to the Network community. If your State, Territory, or Tribe uses OpenNode2 or EN-Node and you are having trouble updating your product, the Environmental Council of the States (ECOS) is providing limited implementation support, directly from the products’ developers, to Partners that need assistance. To request support, please send an email detailing the installation issue you are experiencing to gmcnelly [at] ecos.org.

How will current data flows be affected?

Because much of the Network has yet to fully migrate from Node v1.1 to Node v2.0, Governance anticipates relatively little impact to most existing data flows. If your data flows are currently configured for use with Node 1.1 endpoints, you will not need to make any changes to your endpoint URLs at this time.

If, however, you are currently sending data to a Node 2.0 endpoint at CDX, you will need to direct your data to a new 2.1 endpoint URL after installing your updated product. Please visit http://www.exchangenetwork.net/epa-node-endpoints/ to determine where to direct your data.