1 / 15

Exchange Network Node 2.0 Update

Exchange Network Node 2.0 Update. 2/14/2008. Topics. Purpose Node Architecture/Protocol Node 2.0 Changes Support Reference Implementations Node 1.1/2.0 Transition Publishing NAAS 3.0 Fundable Activities Questions. Purpose.

matana
Download Presentation

Exchange Network Node 2.0 Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Exchange Network Node 2.0 Update 2/14/2008

  2. Topics • Purpose • Node Architecture/Protocol • Node 2.0 • Changes • Support • Reference Implementations • Node 1.1/2.0 Transition • Publishing • NAAS 3.0 • Fundable Activities • Questions

  3. Purpose Provide an update on new developments in Exchange Network Services/Infrastructure • What is new • What has changed and why • Services you can leverage • What you need to do to leverage • What is grant fundable

  4. Node (Web Server) SOAP Listener SOAP Processor Internet Object Handler Firewall Data Mapping XML Processor Existing Database Connectivity Information System Basic Node Architecture SOAP Message Processing

  5. Security (HTTPS/SSL, PKI, etc.) Transport Protocol (HTTP) XML Messaging (SOAP) Envelope SOAP Header SOAP Body XML Schema Network Exchange Protocol Message Structure • Transport - HTTP • XML Message – SOAP 1.2 • Message Payload • XML • MTOM Attachments • Types of XML Messages • Security – HTTPS/SSL

  6. Node 2.0 Changes • Three major changes to Node technologies • SOAP 1.2 • Doc/Literal WSDL (Web Service Description Language) • MTOM (Message Transmission Optimization Mechanism) • Changes primarily driven by vendor support issues • Changes will be mostly transparent • Bring EN up-to-date with current standards for web services • Node 2.0 can easily be adapted to inter-operate with other Web services networks.

  7. MTOM- Message Transmission Optimization Mechanism • Node 1.1 used DIME for payloads • Functional • Best available protocol at adoption • Not supported by latest Java and MS .NET WS toolkits • Node 2.0 uses MTOM • A W3C standard • Better integration • Less complex design and implementation • New standard for WS payloads over SOAP • Performance comparable to DIME (w/o message signature )

  8. Node 2.0 Support • Reference Node Implementations - complete working versions • Open Source versions available • Next Generation Node (CDX) • .NET Node (CDX) • Windsor/Enfotech (based on Grant funding – ‘09) • JAVA • .NET • Java Flow Processor Node (CGI/AMS) • Demonstrated Node Configurations • Testing /Validation tools for Nodes and Web Services • Documentation for • Test tools • Reference Node Installations • Reference Node Operations • Specification documentation • Web Service Definition Language (WDSL) • Node 2.0 Functional Specification.

  9. Why Reference Implementations • Reduced O&M costs • Integrated tools for Node administration and monitoring • Simplified service publishing • Plug and play approach • Open Source implementations • Advanced transaction monitoring and metrics • Better community support and sharing of new components • Node design experience behind each reference implementation.

  10. Node 1.1 / 2.0 Transition 18-24 Months

  11. Node 2.0 and Publishing • Node 1.1 Focused on Basic Data Submissions • Data Publishing Should Be the Focus for Node 2.0. • Data Publishing is Essential to Leveraging all of the Power of our Network SOA . • Configuration Driven Publishing can deliver Turn-key Network Node Solutions.

  12. Network Authentication and Authorization Service (NAAS 3.0) NAAS 3.0 = Node 2.0 Security Message Support + Enhancements Network Node v2.0 will use NAAS 3.0 services. NAAS 3.0 will not be compatible with NAAS 2.0 due to protocol changes. NAAS 3.0 will be deployed in parallel to NAAS 2.0. There will be no impact to the existing Node 1.1 services. Existing user accounts are valid to both NAAS 2.0 and NAAS 3.0. (accessed from common repositories)

  13. Demonstrated Node Configurations (DNC) • DNCs are the messaging layer of a node • For upgrading Nodes rather than adopting Reference Node 2.0 implementation

  14. Network Grant Fundable Activities • Deploy Node 2.0 Reference implementations • Upgrade an existing Exchange Network Node to version 2.0 • Upgrade data flows from 1.1 to 2.0 • Enhance security features; • Deploy infrastructure for Cross-Media Electronic Reporting Rule (CROMERR) support.

  15. Network Architecture Extending Network Capabilities • High flexibility: • Adhoc Flows • User-node, node-node, user-user • Enriched extensibility: • Allows partners to add other services as needed (not just data services) and be able to leverage external web services / other networks. (Execute Method) • Improved Quality of Services: Real-time status, status notification, transaction tracking and management. • Dynamic Discovery: Provide a framework for discovery of node capability at runtime.

More Related