Node 2'0 NAAS 3'0

1
Node 2.0
Get It While Its Hot
2
Topics

• Background
• Node Architecture
• Node 2.0 Changes
• Node 2.0 Support
• Flow Migration Planning
• What Does it Mean to Me?
• Fundable Activities
• Node 2.0 and Publishing
• Appendices

3
Background

• Node 2.0 is a basic upgrade to the Network
• The changes are minimal
• The impact is minimal
• Node upgrade costs vary based on current Node
  Implementation (low to moderate)
• Makes optimized publishing / access options
  available for improving Network operations

4
Basic Node Architecture
SOAP Message Processing
5
Upgrading the TRI Model
Exchange Network
S T A T E
CDX
CDX Node
XML
State Node
Convert ASCII To XML
eFDP Website
Node Client
TRI-ME WEB
F A C I L I T Y
CDX Web
.gov
Desk Top TRI-ME
Internet
TRIS
Mail Room Keying Loading Data
Disk
TRIS Processing (Powerbuilder)
6
Node 2.0 Changes

• Changes primarily driven by vendor support
• Three major changes to Node technologies
• SOAP 1.2
• Doc/Literal WSDL
• (Web Service Description Language)
• MTOM
• (Message Transmission Optimization
  Mechanism)
• 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
Node 2.0 Support

• Reference Node Implementations (see appendix B)
• Complete working versions
• Open Source versions available
• Improved Publishing Capabilities
• Testing /Validation tools
• Documentation
• Guidance
• Specification documentation

8
Flow Migration Planning

• Goals
• Uncouple transition of State Nodes from Program
  system nodes
• Simplify and speed transition
• CDX manages complexity
• OEI coordinates flow transition with Program
  Offices
• Strategies
• Phased Flow Approach Identifying an order and
  schedule for CDX making your v2.0 flow available
  to the EN community
• CDX Broker application Routes V2.0 messages to
  CDX v1.1 Node
• A single Node Client that supports both V1.1 and
  V2.0

9
What Does It Mean to Me

• Tasks
• IPTs will define flow changes and schedule.
• Upgrade Nodes on backend CDX will provide
  support, software and coordination.
• Prepare addendum to Flow Configuration Document
  to detail changes for Node 2.0
• Coordinate with States- You can take advantage of
  new Node 2.0 functionality once States upgrade.
• Flexibility in Upgrade
• You can do the basic upgrade over the next 1-2
  years.
• The lions share of each flow (business layer)
  does not change.
• No changes to the schema are necessary
• Major flow version upgrades
• Use Node 2.0 advanced features
• Use Header 2.0
• Opportunity to select an optimized publishing
  Node

10
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

11
Node 2.0 and Publishing

• Node 1.1 Focused on Basic Data Submissions
• Data Publishing is the Focus for Node 2.0.
• Configuration Driven Publishing can deliver
  Turn-key Solutions.
• Five Open Source Node 2.0 Implementations will
  be available to help optimize publishing
• ENDS 2.0 provides discovery services for
  integrating published data dynamically

12
Appendices
13
Appendix A- 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
• Support external web services / other networks.
• Improved Quality of Services
• Real-time status
• Transaction tracking and management
• Dynamic Discovery Provide a framework for
  discovery of node capability at runtime.

14
Appendix B- Why Reference Nodes ?

• Reduced costs
• Integrated tools for Node administration and
  monitoring
• Simplified service publishing
• Plug and play approach
• Open Source implementations
• Better community support and sharing of new
  components
• Node design experience behind each reference
  implementation.
• Support both V1.1 and V2.0 messages
• Advanced transaction monitoring and metrics

15
Appendix C- 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 is already deployed alongside NAAS 2.0.
• There is no impact to the existing Node 1.1
  services.
• Existing user accounts are valid to both versions
  .
• Security Tokens are interoperable across
  versions.
• NAAS 3.0 messages are not be compatible with NAAS
  2.0
• NAAS 3.0 will be part of your transition planning
  for Node 2.0 (minimal)

16
Appendix C- Service Discovery (ENDS)

• Service discovery is a key component in
  service-oriented architecture (SOA) and plays an
  important role in the Exchange Network.
• Improves information access through publishing
  services
• Supports User Friendly Tools
• Simplifies Administration

17
Appendix D - Upgrades to Tools and Services

• Network Browser
• Network Desktop
• Node Clients
• Exchange Network Discovery Service
• Universal Description and Discovery Integration
• Quality Assurance Services
• Data Transformation
• Service Monitoring and Management