| Have questions about what Node 2.0 means for you and your organization?
Check out the following FAQs. If you don't see the answer you're looking for, feel free to send a message to the Node 2.0 e-mail address or contact a member of the Network Technology Group.
frequently asked questions
These Frequently Asked Questions are divided into three sections:
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 improving upon version 1.1, adding new functionality, and ensuring the EN remains compatible with the latest industry standards.
Why are we upgrading to Node 2.0?
Version 1.1 of the Protocol and Specification documents define the use of technology that is 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 transparent 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).
- Updating the Execute primitive to support operations which require an in-bound payload (like submit) and an outbound payload (like 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.
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 processes and determine when an upgrade to Node 2.0 makes sense. The migration to Node 2.0 is anticipated to last a couple of years and the Network 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. The decision to install a 2.0 Node will likely be driven in part by the upgrade plans of your exchange partners. 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 Node products. The Node 2.0 Products page has links to more information on Node 2.0 solutions that have already been developed. The Network governance encourages all Network partners to consider using one of these products, as they may offer the most cost-effective path to upgrading your existing Node.
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 a number of 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. Your preferred method of upgrading will also be a determining factor. Network partners may choose to develop their own Node from scratch or take advantage of a Node that has already been developed. Using an existing Node product may offer a more cost effective upgrade solution. Network partners are strongly encouraged to review the information on the Node 2.0 Products page for more details on Nodes that are available. Keep in mind that U.S. EPA's Exchange Network Grant program offers states and tribes an opportunity to apply for money to support the transition to Node 2.0
Node 2.0 Migration Questions
What is the impact of Node 2.0 on my existing flows?
Node 2.0 affects the messaging between Nodes. Because of the additional features and information carried in a Node 2.0 message, you will need to make some minor changes to the configuration of your current Network flows to allow them to operate correctly on your 2.0 Node. These changes will be minor. Node 2.0 does not impact the XML schema for any existing data exchanges, so you will not need to alter any of your existing stored procedures or perform any new mapping activities. Please see the Flow Migration page for more details on this topic.
What changes will I need to make to my existing flows to make them compatible with a 2.0 Node?
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. We will be producing addenda to Flow Configuration Documents (FCDs) for each of the national regulatory flows. These addenda will be available on the Exchange Network website in October 2008. Please see the Flow Migration page for more details on this topic.
When will I be able to begin using a 2.0 Node to share information?
The answer to this question depends in large part upon the plans of your exchange partners. Version 1.1 Nodes and version 2.0 Nodes cannot communicate with one another. Therefore, you should plan to coordinate the migration of your existing flows to Node 2.0 with your exchange partners. The majority of states, tribes, and other Network partners exchange information with U.S. EPA's Central Data Exchange (CDX) Node. CDX anticipates being able to receive communications from either version 1.1 Nodes or version 2.0 Nodes in October 2008. CDX will continue to support Node 1.1 communications for the foreseeable future to allow adequate time for all partners to make the transition for all flows. If you exchange information with partners other than U.S. EPA, you should communicate with that partner to determine a timeframe for migrating to Node 2.0-compliant flows. To support the needs of multiple partners, you may need to consider maintaining 2 endpoints (1 for Node 1.1 flows and 1 for Node 2.0 flows) while the transition is occurring. For more detailed information on this topic, please see the Flow Migration page. |
