Exchange Network Products

Exchange Network tools and products are available at no cost. These pre-developed solutions allow EN Partners to take advantage of others’ development work and lessons learned, so they are often more cost-effective than independently building new tools from scratch. Partners should be aware that even these solutions may require customization to work within their organization’s technology environment and infrastructure.


The following Node 2 products are available:

  • OpenNode2 – Owned and maintained by ECOS. Built as a collaboration between State Partners and Windsor Solutions, Inc. Both .NET and Java versions are available. Supports Node 1.1 and Node 2.1 specifications.
  • EN-Node – Owned and maintained by ECOS. Built as a collaboration between State Partners and enfoTech & Consulting, Inc. Both .NET and Java versions are available. Supports Node 1.1 and Node 2.1 specifications.
  • CGI Node 2.0 – Owned and maintained by CGI. Open source solution supporting Node 1.1 and Node 2.1 specifications.
  • Next Generation Node (NGN) – A collaboration between EPA and Computer Sciences Corporation. Open source solution supporting Node 1.1 and Node 2.1 specifications. Contact helpdesk [at]
  • Virtual Exchange Service – Created by EPA, the Virtual Exchange Service (formerly known as the Virtual Node) is a state-of-art Network Node implementation for the cloud environment.

Node Plugins

A node plugin is a generic term for the container that provides the functionality for one or more services for a particular data flow. Partners can download and install these free node plugins to support the particular data flow. Additional configuration steps such as data mapping may need to performed after the plugin is installed.

The two most widely used Node platforms, OpenNode2 and EN-Node, both employ a pluggable architecture.

Partners can create their own OpenNode2 plugins using the OpenNode2 Altova MapForce Bridge, a tool designed to work with Altova’s MapForce product. A license for MapForce from Altova is required. Documentation and tutorials follow.

Node Clients

Node Clients (also known as Network Clients) can interact with Exchange Network Nodes by submitting data to Nodes and retrieving data from Nodes. Node Clients provide the following benefits:

  • An easy-to-use interface for interacting with Nodes
  • Semi-automated alternative to a fully functioning Node that allows users to submit data to or download data from a Partner’s Node
  • Assists in testing the development and implementation of a Node

Node Clients cannot respond to data queries from other Nodes and, therefore, cannot publish on-demand data on the Network. They may be a cost-effective solution for Partners who do not have a compelling business need to publish their data. Node or Node Client: To be or not to be describes the differences between a Node and a Client.

These Node Clients are available online:

  • EN Services Center – A Network Client hosted by EPA that makes submitting data to EPA Nodes easier.
  • EN Browser – A Network Client that can be used to retrieve data from any Exchange Network data publisher.
These Node Clients are available for download and installation:
  • NodeClientLite2 – A Network Client developed by Windsor Solutions, Inc., that runs as a desktop application. Also includes an integrated add-on to view spatial data and facility data.
  • EN-Node Node Client – EN-Node includes a bundled Node Client. This Node Client runs as a web application, so in order to run this option, the user will need to install the application on a web server.

DISCLAIMER: The Network Technology Board (NTB) is providing links to these sites because they contains information on freely available Node products that have been successfully deployed by many EN Partners. The NTB does not attest to the accuracy of the information provided by Node product vendors. These links do not constitute an endorsement of the sponsors of the sites or the information or products presented there.

To add your product to this list, please contact Greg McNelly at gmcnelly [at]