Node 2.

0
Empowering the Exchange
Network

TRI National Conference 4/2/09

Chris Clark
Node 2.0 - Topics

 Description of Node 2.0

 Goals

 Drivers for upgrading

 Support for Node 1.1 and partner transition

 Node 2.0 Enhancements

 Technical changes in Node 2.0

 Update on the current migration process

Node 2.0 Basics

 Version 2.0 of the Exchange Network Node is

the next generation of technologies and
services that will power the Exchange
Network.

 Node 2.0 is basically a specification or

technology change

 Support for Node 1.1 and partner transition will

continue
The Goals
 Create a flexible, extensible web service network
(SOA) that allows partners to easily discover and
exchange arbitrary information from any point to
any point reliably, and securely.

 Create a framework that leverages current and

future technologies, and meets both current and
future data exchange requirements.

 Even better Quality of Service

The Challenge
 Future Network business processes and technical
requirements need to be supported by the
architecture

 The technology landscape is still evolving rapidly.

 Multiple operating platforms are supported.

 Different visions and near term goals exist.

 Node 2.0 Changes
 Three major changes to Node technologies
 SOAP 1.2 – latest SOAP Version
 Doc/Literal WSDL
(Web Service Description Language)
Messages become schema compliant
 MTOM – Industry message attachment specification
(Message Transmission Optimization Mechanism)
 Changes primarily driven by vendor support issues
 Changes will be mostly transparent
 Node 2.0 can easily be adapted to inter-operate with
other Web services networks.
State Node 2 Flow Migration
 CDX Node was enhanced to support Node
2.0 specification

 CDX ready to support Exchange Network

National Flows for State migrations to Node
2.0 - September 2008

 Coordinate transition to Node 2.0 Sept. 2008 -

Sept 2010

 All new flows will use Node 2.0 design

 Expanding Node Server
Capacity
 Migration to 64 bit Operating System
 Extends server memory support from 4 Gigabytes to

Terabytes

 Virtualization of CDX Architecture

 Simplifies expansion of server capacity

 Dynamically allocate CPUs, memory, virtual servers

 Failover, disaster recover

 Simplifies Operations and Maintenance

TRIME Test Deployment Status

 Deploys on New 64 bit Blade Server

 Significantly expanded resources
 64-bit CDX Node Server
 Configured and running
 TRIME Scheduled for 4/6/2009
 Firewall Rule Request Submitted
 Digital Certificate ordered
TRIME Production
Deployment
 Deploys on New 64 bit Blade Server
 Significantly expanded resources
 64-bit CDX Node Server
 Begin configuration this week
 Scheduled for April 11, 2009
 Firewall Rule Request Submitted
 Digital Certificate ordered
Node 2.0 –
Better Stronger
Faster!!
New Node 2.0 Exchanges

Node to Node

Client to Node

Web Client to Client

Service Discovery 2.0 (ENDS 2.0)

 Exchange Network Discovery Services 2.0

 Automatically collects and updates Network meta

data repository

 Improves Information Access

 Supports User Friendly Tools

 Simplifies Administration
Security 2.0
Network Authentication and Authorization Service

 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)
Quality Assurance 2.0

 XML parsing and extended business rule validation

 QA 2.0 = QA + Node 2.0 Message Support + Enhancements

 New 4 CPU 64 bit server with 4 times as much memory

 Looking into server virtualization for easier capacity expansion

 Node 2.0 Publishing

 Node 1.1 Focused on Basic Data Submissions

 Data Publishing is the Focus for Node 2.0.

 Data Publishing is Essential for Leveraging all of

the Power of our Network SOA .
 Publishing and Syndication
Services 2.0
 New Publishing services that support the secure
exchange and syndication of any data
 Totally configurable –
 Easily add new dataflows / information

sources
 Configure new RSS/ATOM Feeds in minutes

 Used for the Agency Recovery.Gov interface

 Flexible and extensible
 Supports Web Service and Browser based
submissions
 Supports embedded and linked syndication
Basic Syndication Workflow
 Content providers describe and submit documents:
 Browser
 Client
 Node

 Services store metadata and data or pointers to the data in a

repository and create syndicated feeds automatically

 Users subscribe to the new Feeds or Channels

 The subscriber uses a Reader or a Browser to search, filter, and

read the RSS/ATOM summary data locally

 Users get security challenge when they drill down to actual data
Interfacing Options
Interfaces
Federal State
Web Browser Business Tools Any Flow of
System Systems Information
s

Browser OR Web Services

Interface
Publishing
Emails
Services CDX
Node Notifications

RSS / ATOM Feeds

Information Search Services
 Full-text Search
 Search all documents using keywords, time range, dataflow
and publisher as filters.
 Results rendered as RSS feed
 User downloads the document or displays it directly

 Keyword Search
 Data services for searching documents based on keywords

 XQuery
 Allows users to extract part of the information from a large
XML document.
 Returns an XML document
 Publishing
Framework Web Interfaces
Document Providers
Publishing Document Web
Services Document
RSS
Design Reader
Search/
Download
Node Client

HT TP

HT TP
Submit XML
RSS Feeds
(GetRSS)

SOA P M essages
SOAP Central Document Services
Node Document (Node 2.0)
Applications Search
(Full-Text)
Network Node
V2.0
Submit XML

XQuery
Search

Relational
Data

Document Meta-data
Transactions
Repository Repository
 Node 2.0 Interoperability
Capabilities

 Enriched Extensibility:
 Allows partners to add any local services as needed

 Support for external web services and other networks such

as CDC, Homeland Security etc.

 Dynamic Discovery: A framework for discovery of Services and

binding to them .
Extending Network
Capabilities
 High flexibility:
 Remove data format limitations and exchange barriers
 Allow flowing binary data and XML data in both directions.
 Enhance the scope of exchanges
 (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.( work with other networks).
Extending Network
Capabilities
 Improved Quality of Services: Real-time status, status
notification, transaction tracking and management.
 More Support for real time services
 Dynamic Discovery: Provide a framework for discovery
of node capability at runtime.
 Allows point-2-point or person-2-person secure data
exchanges.
 Opens the door for ad hoc dataflows that exchange
emergency data
Major Node 2.0 Features
 Query paging/chunking and results
compression.
 Support for outgoing delivery of binary data.

 Name-based parameters for Query, Solicit and

Execute.
 Allows various types and encoding of parameters.

 Notification/Recipients
 Enables Point-2-Point and Person-2-Person Exchanges
Major Node 2.0 Features - 2

 Execute method.
 Allows nodes to support additional web
services
 Extends Network access to all external web
services (proxy).

 Node self-description and discovery

 Nodes can publish sufficient information
for run-time binding.