The Exchange Network Discovery Service (ENDS) provides an automated system of Exchange Network service description, cataloging and discovery. Node 2.0 defines a core primitive method called GetServices that all nodes must implement. This service is designed to return an XML schema describing every query, solicit, execute, and submit service that the node offers. EPA has implemented an ENDS 2.0 Node that can poll the GetServices method on every Exchange Network node to collect and catalog the responses in a central service repository available to all Partners. Once fully populated, this central repository will allow browsing of the Exchange Network and enable a single Node Client to consume all services published by Network nodes.

ENDS requires Partners to implement the GetServices v2.0 XML schema and to configure the ENDS 2.0 exchange on their nodes. The GetServices 2.0 Schema is the last piece of the Node 2.0 Specifications to be released. All version 2.0  nodes should return an instance document of the GetServices schema with any GetServices response message. If you are not yet using a 2.0 node or would like to manually register your sevices in ENDS, please visit the ENDS Registration Service. You will need a valid NAAS ID to add your Node and its services.

The Discovery Services User’s Guide is available here.

The Flow Configuration Document (FCD) for the Exchange Network Discovery Service (ENDS) 2.0a and the GetServices version 2.0 XML Schema are now available on the Exchange Network website.

The EN Browser also publishes some instructions for data publishers on how to ensure information published in ENDS can be viewable in the EN Browser: EN Browser: How to Publish Data.

If you have any questions on the ENDS 2.0 FCD or the GetServices schema, please contact the Network Technology Group Co-chairs.