About Nodes and Clients
From Exchange Network Wiki
This page is intended to provide partners with perspectives on selecting between an Exchange Network node and an Exchange Network client. The table below outlines the functionality of each. Please feel free to add additional information to aide others in deciding what technology is best for their organization. If you have questions that are not answered here, please add them to the discussion page.
Contents |
Nodes and Clients Defined
An Exchange Network Node is a Web service-enabled server (hardware and software) that facilitates the interface between database systems and the Network over the Internet. It is an entity's "point of presence" on the Exchange Network. Exchange Network Nodes can gain access to and transmit information using Web Services. With properly configured Nodes, Network trading partners can seamlessly exchange data regardless of hardware, operating system, or programming environment. In order to achieve interoperability among Nodes, all Nodes must be set up according to the Exchange Network specifications. Specifications, protocols, tools, code, and documentation for building a functioning Exchange Network Node are also available.
An Exchange Network Client is a stand-alone application (software code) that can initiate Exchange Network requests. Clients can submit, request, and receive results from a request on the Network. However, clients cannot respond to data queries, and therefore cannot publish data on the Exchange Network. Clients are good solutions for Network partners who do not wish to publish data on the Exchange Network. Several Node Client applications that are very user friendly are available on the Exchange Network Web site already. More are on the way. A Node client software developer kit (SDK) is also available to help partners integrate Node client requests into their applications. For more information, check out the Network Clients page on the Exchange Network website. It includes links to sample node clients.
Functionality Table
| Functionality | Node | EN Client |
| Partner plans to publish their data (respond to data requests from others without having to do anything) | X | |
| Partner doesn’t plan to do any data publishing (listening for or responding to data queries from other EN partners) | | X |
| Partner plans to submit data in XML format to EPA or other partners on an automatic schedule that the partner sets up | X | |
| Partner plans to submit data in XML format to EPA or other partners manually | X | X |
| Partner plans to request data in XML format from EPA or other partners | X | X |
| Partner plans to share only the data they want to share | X | X |
| Costs anywhere between $20-$100K to set up | X | |
| Costs nothing (free software is available) | | X |
| Requires configuration of a database | X | |
| Partner is a casual user | | X |
| Partner will use the EN infrequently | | X |
| |
Mentoring
Mentoring States
CDX contacts
Forums
Lessons Learned
Specific Partner Configurations
Here are some Node 1.1 configurations that node partners are running. This list should be referenced when attempting to determine what states, tribes, or other partners are running a configuration close to the one that someone may be attempting to acquire information about.
EPA
- CDX uses the Next Generation Node (NGN) Client and Server suite for Java platforms.
States
- Mississippi
- Node Client and Server are integrated in a .NET platform.
- Database is Oracle 10g
- Missouri
- Node Client and Server are integrated in a JAVA platform.
- Database is IBM DB/2 Ver. 9
Tribes
Other Partners
See Also
External Links
- Network Authentication Authorization Services
- More information on Nodes and Node Clients is available on the Exchange Network website.
- Next Generation Node by CDX
- Open Source Node 2.0 by CGI
- Network Authentication Authorization Service (NAAS)
