The Exchange Network Technology Group (NTG) has released the next generation of technologies and services that will power the Exchange Network - Node 2.0. The goals of Node 2.0 are to update the Exchange Network Node software to be compatible with new Web Service technologies, to fix identified problems with Node 1.1, and to provide some new features and functionality.
For additional information on the final Node 2.0 products, see the Node 2.0 Products page.
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 current.
Why are we upgrading to Node 2.0?
The v1.1 of the Protocol and Specification 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 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.
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.
What Node 2.0 implementations are going to be available and when?
Various 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 Implementations Summary document. 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 choose to migrate to Node 2.0 when there is 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. There are, however, various free Node implementations that will be available to all EN Partners to help reduce costs. EN Grants will also be available to states and tribes interested in upgrading to Node 2.0.
How much work/will it cost to upgrade my Node to support Node 2.0 Flows?
The cost of upgrading your Node to support Node 2.0 Flows varies and will depend on your current implementation and database structure.
Node 2.0 Migration Questions
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 Flows and services will be available to Node 2.0 implementations. Governance will be working with Flow administrators and major Node administrators to ensure the appropriate documentation, including FCD addendums, are created. The EN Governance has also funded the creation of the Node 2.0 Certification 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 (all available on the Exchange Network Website).
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 EN Governance is currently working on a pilot with the WQX Flow that will determine the level of effort for this alteration; however it is anticipated to be minimal.
What is the transition schedule for Node 2.0?
Governance is encouraging all Network Partners to evaluate their current Node 1.1 infrastructure and migrate to Node 2.0 when appropriate. There is no set timeframe in which EN Partners must move to Node 2.0. CDX will continue to support Node 1.1 Flows for the foreseeable future. However, as new data exchanges are developed that take advantage of Node 2.0 features, EN Partners will need to evaluate the costs of staying with the Node 1.1 architecture as compared to migrating to Node 2.0 and taking advantage of the new features offered.
When will CDX support Node 2.0?
CDX will provide a Node 2.0 implementation for network users immediately after the Specification is finalized. CDX is determining how to best support current national system Flows through the Node 2.0 interface and is evaluating two approaches:
- Transition Day approach: CDX and the EN governance create a ‘broker’ application that sits in front of CDX that is able to route v1.1 and v2.0 Flows appropriately. On the day of deploying this application, all Exchange Network National System Flows are available on the Node 2.0 platform
- Phased approach: Identifying an order and schedule for CDX readiness for v2.0 National System Flows and publishing this for the EN community.
contact information
If you have any questions about Node 2.0 or would like to submit comments, please contact the Node 2.0 e-mail address or the NTG co-chairs:
Connie Dwyer
U.S. EPA Office of Environmental Information
(202) 566-1691
dwyer.connie@epa.gov
Glen Carr
Oregon Department of Environmental Quality
(503) 229-5062
carr.glen@deq.state.or.us |
