1 Exchange Network Node 2.0 Open Conference Call February 27 th, 2007

2 Introductions This conference call is hosted by the Network Technology Group (NTG), which is the technical work group of the Exchange Network (EN) governance NTG members present: Connie Dwyer, EPA OEI (EPA Co-chair) Glen Carr, Oregon DEQ (State Co-chair) Dennis Burling, Nebraska DEQ Chris Clark, EPA OEI

3 Conference call agenda Provide a detailed description of the proposed technical changes from Draft 8 (October 5, 2007) to Draft 9 (March 3, 2008) Update on revised Node 2.0 Timeline Update on Node 2.0 Testing Opportunities Q&A - Collect your feedback on Node 2.0 needs and concerns

4 Conference call basics Feel free to ask questions at any time during the presentation: before, during, or after! Please put your phone on mute when you’re not asking questions (if your phone has a mute function) Please don’t put this call on hold if your hold function plays music This web conference has a chat feature. Please feel free to send questions or comments to the meeting organizers at any time during the call.

5 The journey from Node 1.1 to Node 2.0 Late summer 2006: NTG work group starts discussing Node 2.0 June 2007: Node 2.0 revision 7 WSDL, Specification release to EN for comment June – Present: continued development of WSDL, Specification October 5, 2007: Node 2.0 Draft 8 WSDL, Specification released February 11, 2008: Node 2.0 Draft 8 Unit Testing completed March 3, 2008: Release of Draft 9 WSDL, Specification

6 Basic changes in Node 2.0 Three major changes to Node technologies SOAP 1.2 Doc/Literal WSDL MTOM Changes primarily driven by vendor support issues These changes will be mostly transparent but are important for other reasons: Bring the Exchange Network up-to-date with current standards for web services This means that the same platform (e.g. SOAP 1.2 handler) that runs Node 2.0 can easily be adapted to inter-operate with other Web services networks

7 What’s New in Node 2.0: SOAP 1.2 and Doc/Lit WSDL Soap 1.2/MTOM SOAP 1.1 is no longer supported by Java or MS.NET WS toolkits. SOAP 1.2 utilizes MTOM (now a W3C standard) to attach binary messages which has a unified infoset, is simple to design and implement, and is the new standard for WS payloads over SOAP. Doc/Literal WSDL The Node 1.1 WSDL is RPC/Encoded. Standard, but inconsistent implementation due to encoding type definitions. Doc/Literal allows WSDL types to be defined like normal XML schema.

Node 2.0 Draft 9 Specific Changes Parameters –Parameters are now defined as an element/attribute pair. –Includes ability to specify unique type for each parameter. –All nodes are expected to support String and XML parameters. Additional allowable types are enumerated in the WSDL and are optional for nodes to support. 8

Node 2.0 Draft 9 Specific Changes Query Paging –Expanded from Node 1.1 –Return result set based on rowID, maxRows –Query paging parameters must always be included in the response. –If a node is unable to page query results, it should return the entire result with values of: rowID = 0 maxRows = 0 lastSet = true 9

Node 2.0 Draft 9 Specific Changes Synchronous Status Response –Response for Submit and Solicit includes: Status Code = Received, Pending, Processed, Complete, and Failed. Status detail contains free form text. –These return elements are required, however if a node cannot support granular status reporting, a status code of ‘Received’ may be returned instead of actual values. 10

Node 2.0 Draft 9 Specific Changes Automatic /Node notification –Ability to supply either a valid URI or Node URI and automatically receive a notification message when a transaction status changes –New notificationURI WSDL construct allows for granular notification Only receive s on error, warning, failure, etc. –Nodes should return a non-critical error if this feature is unsupported or if the address is unavailable or invalid 11

Node 2.0 Draft 9 Specific Changes Dynamic submission routing –Via the new ‘recipients’ parameter –Specify either a Node URI or URI Nodes receive a forwarded submission s receive transactionID. –Creates ability to create ‘ad hoc’ dataflows – i.e. dynamic submissions 12

Node 2.0 Draft 9 Specific Changes GetServices method –GetServices Response will return an XML response defined in an outside schema. The current version of the GetServices schema will be specifically referenced in the Specification as the required return. –A GetServices response is required from all EN Nodes. –Nodes that are not able to dynamically generate a GetServices response message should return a static description of the services offered by the node as defined in the Specification. 13

Node 2.0 Draft 9 Specific Changes Execute method –Expandable interface for services: Future EN Services Outside Web Services Legacy Node 1.1 applications –This method will be optional for nodes to implement 14

15 Node 2.0 Timeline February 2008 –Modification/revisions to the WSDL, specification, and protocol process Task force discussion on any issues that arise during testing Basic Unit Testing of the WSDL and Specification NTG review and acceptance of modification and revisions March 3, 2008 –Node 2.0 WSDL and Specification Draft 9 made available to the user community and for comment April 2008 –Modification/revisions to the Node 2.0 WSDL and Specification –NTG review and acceptance of modification and revisions May 2008 –Finalize Node 2.0 WSDL, Protocol, Specification and supporting documentation June 2, 2008 –Release all Node 2.0 items (Specification, WSDL, and Protocol) –Start Node 2.0 implementations and operations

Node 2.0 Unit Testing Summary 16 Test CaseMethod TestedOutcome 1. Authenticating a user AuthenticateSucceeded 2. Basic Submission SubmitSucceeded 3. Synchronous Data Request QuerySucceeded 4. Asynchronous Data Request SolicitSucceeded 5. Download Document DownloadSucceeded 6. Retrieve Status information based on TransactionID GetStatusSucceeded 7. Send Notification to an EN Node NotifySucceeded 8. Node Availability NodePingSucceeded

17 Opportunities for you to participate in Node 2.0: Development The NTG is asking for comments and suggestions on every aspect of Node 2.0 Draft 9 WSDL and Specification Support Materials Exchange Network Guidance Please look for Draft 9 distribution package on March 3. For more specific information on technical Node 2.0 materials, please visit the Node 2.0 page at:

18 Opportunities for you to participate in Node 2.0: Testing Node 2.0 Test-tool under development. Two phases of testing: Unit testing individual methods (completed) Functional Testing basic exchange scenarios (April 2008) The NTG is still looking for vendors (or other Network Partners) to code additional Nodes, including:.NET, Java and an Open Source Node Alternate Web Service Implementations

19 How do I stay connected? Updates on Node 2.0 will be posted to the Node page on Exchange Network website: Slides from this call will be posted shortly NTG will use Network Alerts to inform you of key updates on Node 2.0 and to announce future open calls NTG will contact those vendors/Network partners who express an interest in coding a Node implementation to discuss a communications process

20 How to communicate on Node 2.0 The Exchange Network Message Board has a forum set up for you to ask questions and collaborate with other Network partners: To contact the NTG directly: questions to: OR Contact the NTG co-chairs: Connie Dwyer, EPA Co-chair EPA OEI (202) Glen Carr, State Co-Chair Oregon DEQ (503)