Node 2.0 Technical Questions
What is Node 2.0?
Node 2.0 is the newest version of the Network Node Specification (Specification) and Exchange Network (EN or Network) Protocol (Protocol) – the seminal technical definition of the Exchange Network. Node 2.0 defines an upgrade to the infrastructure of the Exchange Network by improving upon version 1.1 through new functionality and ensuring the EN remains current.
How is Node 2.0 an improvement over Node 1.1?
With Node 2.0, programs will benefit from:
- The ability to exchange data of any format and size
- The opportunity to improve and expand automation of business processes (for example by supporting data exchanges between small handheld devices and powerful servers)
- Improved notification and messaging via email and other means about the status of data flows, including messages about errors that may have occurred during an exchange
- Greater compatibility with internal and external web services, which creates more opportunities to integrate data internally and with partners.
Why are we upgrading to Node 2.0?
Version 1.1 of the Protocol and Specification documents define use of technology no longer supported by most software vendors. This technology deprecation has driven the development of Node 2.0 using new, open web service, and XML standards that are supported by a wide range of vendors. Additionally, the redevelopment of the Specification presents an opportunity to improve on the existing infrastructure and provide new features and additional value to EN Partners.
What are the technical changes in Node 2.0?
Node 2.0 makes two kinds of changes to the EN Protocol and Specification:
- Changes to underlying technologies and low level protocols: most of these changes will be invisible to Node and Client users and they should make life easier for developers. These include:
- Switching the attachment method from DIME (which is being de-supported) to MTOM (now a W3C standard).
- Adopting a standard approach (“doc/literal wrapped” binding) in the WSDL, which means that the inputs and outputs to Exchange Network methods are now full-fledged XML structures that can be validated for conformance against the WSDL. This means that the WSDL defined inputs/outputs for all Exchange Network methods have changed even if nothing functional about the methods’ inputs/outputs has changed.
- Adopting the newer version of SOAP (version 1.2). This version of SOAP provides improved integration with the WSDL and includes new features such as improved fault handling.
- Limited changes to the architecture and operation of the Exchange Network services, including:
- Improving the fault and status messaging for transactions (see GetStatus and NodeFault).
- Providing immediate status messaging for asynchronous operations and dynamic routing and notification support. (see Submit, Process and Solicit).
What if my system can’t support the new features?
The EN Governance has strived to make adoption of the Node 2.0 Specification possible for all EN Partners. Each new feature in the Specification is designed with a default value that can be returned to indicate that a Node does not support that feature.
When is the Node 2.0 Specification going to be finalized?
The final version of the Node 2.0 Specification was made available on June 2, 2008.
What security features are available in Node 2.0?
Node 2.0 includes the same robust security features implemented in Node 1.1 through the Network Authentication and Authorization Services (NAAS). The Exchange Network has updated NAAS to version 3.0 to ensure that a robust security model can be applied to each new feature of Node 2.0. Specific security features include user authentication through numerous methods and granular authorization permissions for each method and feature.
Node Implementation Questions
When do I have to install a version 2.0 Node?
There is no set timeline for Node 2.0 implementation. The Exchange Network Governance is encouraging all Partners to examine their business process and determine when an upgrade to Node 2.0 makes sense. For many Partners, this will be driven by major upgrades to key national system Flows, which are determined by the relevant IPT. However, the EN Governance will work to ensure that all services and data exchanges will continue to work for Network Partners regardless of whether they are running Node 1.1 or Node 2.0. U.S. EPA plans to have its 2.0 Node in production in October 2008, but will also maintain a Node 1.1 endpoint to accomodate exchanges with its partners’ existing 1.1 Nodes. See the Flow Migration page for more information on this topic.
What Node 2.0 implementations are going to be available and when?
A number of vendors are preparing Node 2.0 implementations as new products or upgrades to existing Nodes. You should contact your current vendor for more information or refer to the Node 2.0 Products page. The Exchange Network governance will continue to monitor Node 2.0 implementations and make information available to the Exchange Network community.
What will happen if I can’t install a version 2.0 Node immediately?
The migration to Node 2.0 is anticipated to last a couple of years. EN Partners will probably choose to migrate to Node 2.0 when doing so would provide a clear benefit to their business processes.
How much is it going to cost to upgrade to Node 2.0?
The cost of upgrading to Node 2.0 will vary depending on numerous factors. Your hardware, system software, database software, implemented Flows and the type of existing Node all play a part in determining the cost of an upgrade. Some Node 2.0 Products may be available for free or at a reduced cost. EN Grants are also available to states and tribes interested in upgrading to Node 2.0.
How can I get funding for the transition from Node 1.1 to Node 2.0?Grants were made available from the U.S. EPA through its Environmental Information Exchange Network Grant Program. The FY2008 and FY2009 grant solicitation notices included competitive funding opportunities to support the development or implementation of Nodes that comply with the Node 2.0 specification. FY2009 was the final year in which these grants will fund Node 2.0 implementations. The FY2009 grants applications were due on Nov. 21, 2008.
Node 2.0 Migration Questions
What is the impact of Node 2.0 on my flows?
Node 2.0 does not impact the schema (payload) of your data exchanges. Node 2.0 affects the messaging between Nodes. Because of the additional features and information carried in a Node 2.0 message, your current Network Flows will need to be altered to correctly operate over Node 2.0. The Exchange Network governance is currently engaged in an effort to document all of the required changes to make many existing data flows compatible with Node 2.0. The changes are documented in addenda to the Flow Configuration Documents (FCDs) for each of the national regulatory flows. These addenda are available on the Flow Migration page.
Do I need a new schema for my Node 2.0 flows?
No, existing flow schema will work with either version 1.1 or version 2.0 nodes.
How long will the Central Data Exchange (CDX) support Node 1.1 submissions?
CDX will continue to support Node 1.1 submissions until partners have made all flows Node 2.0 compatible. However, the Exchange Network governance encourages EN Partners to evaluate the costs of staying with the Node 1.1 architecture as compared to migrating as quickly as possible to Node 2.0 and taking advantage of its new features, efficiencies and lower costs.
When will CDX support Node 2.0?
Network partners may now begin testing several Node 2.0 exchanges with CDX. See the Flow Migration page for more information on which flows are available for testing.
What is the EN Governance doing to support transition to Node 2.0?
The Exchange Network Governance is supporting the transition in multiple ways. First, the Exchange Network Governance has committed to ensuring that all national flows and services will be available to Node 2.0 implementations. The governance will be working with flow administrators and major Node administrators to ensure the appropriate documentation, including FCD addenda, are created. The EN Governance has also funded the creation of the Node 2.0 Test Tool to ensure all Nodes are compliant with the Node 2.0 Specification and compatible across systems and web service toolkits. Lastly, the EN Governance is committed to creating all the necessary guidance and documentation to ensure that EN Partners have all the needed information to make the transition to Node 2.0 as smooth as possible.