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
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.
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.
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 ECOS’ Greg McNelly.
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 consult the flow-by-flow list of Node endpoint URLs at CDX to determine where to direct your data.