Transcript TIDEN

TIDEN
Node Management
Texas Integrated Data Exchange Node
Partnered with
Agenda
History of the project
Why did we become involved
TIDEN Overview
History of the project
2002 Grant

Prepare infrastructure
2003 Grant

Build Node
2004 Grant

Add data flows
Why did we become involved
Each Program area had different
process
Foundation for future electronic
reporting
Lessons learned
TIDEN Vitals
TIDEN is a J2EE application
TIDEN Overview
TIDEN Top 4 Features




TIDEN as a Framework
User Management
Domains
Status
TIDEN as a Framework
The Problem: Change
Specs/Protocols will change
Local Web Service Methods will get added
Flows will include cross programs areas
Flows have unique (mapping, process,
schedule, etc) and common requirements
Multiple flows will be developed/maintained
concurrently
Flows need to be relatively independent from
one another
The only constant is change
TIDEN Framework: Overview
Example
Query Web Method
Query(<token>, <request>, <rowID>, <maxRows>,<parameters>)
Query Operations:
1. Query(<token>, getFacByID, <rowID>, <maxRows>,<parameters>)
2. Query(<token>, getFacByName, <rowID>, <maxRows>,<parameters>)
TIDEN Framework: Operations
TIDEN framework provides a common workflow for operations
of a handler
Each operation has hooks at certain points for operation specific
implementation to be “plugged” in
Adding a TIDEN Operation
Lessons Learned
Understand the specs/protocols
Understand the relationship between
Web Methods
Initially focus on Web Methods and
relationships you know you need
User Management
The Problem: Managing Users
Diverse types of users (people and machines)
Each flow has users and policies
Some users cross flow boundaries
Some users cross state boundaries
User vs Administrator users
NAAS required integration
NAAS
Potential solution to user management issues
Pros






Already developed and free!
Supports comprehensive authentication
Supports sharing users across partner Nodes
Works well for exchanges among Node partners
Easy to get up and running on Network
Provides Web Services for management
Cons




Limited
Limited
Limited
Limited
scope (spec/protocol Web Service Methods)
authorization granularity
management capabilities (e.g. - GUI)
control
All Nodes must support NAAS tokens!
NAAS Interface
User Management
Use NAAS Web
Services to:



Manage NAAS Users
and Policies
Provide GUI
Management
Extend NAAS
TIDEN Interface: Summary
TIDEN Interface: New User
Lessons Learned
Understand NAAS Features/Limitations
Determine User Management
interactions early on
Keep It Simple Stupid (KISS)

No synchronization with NAAS server
More NAAS Web Services are needed
Domains
The Problem: Delegation
Program Areas have the business
knowledge
Program Areas are the end users
Flows will cross Program Areas
Flows should reuse existing logic when
possible
Solution should allow for flow
independence
Domains
Node Domain
Air Domain
Central Registry Domain
Node Domain
•Node Domain: Authenticate, NodePing, GetStatus, GetServices
•Other Domains: Submit, Query, Solicit, Notify, Download
•Each Domain is assigned a Domain Admin
•Domain Admins manage users and policies for their domain
Not all Web Methods are shown in the diagram.
Lessons Learned
Domains should be logical
Need special “Node” Domain
Domain Admins can modify any TX
Node User
What’s your Status?
The Problem: Status
NodePing and GetServices provide basic
information only
Web Services require a client able to
call them and process results
How do you provide quick and easy
access to your Node’s status?
Status Page: Splash Page
Status Page: More Details
Lessons Learned
Use GetServices or not?
How much information?
Parting Thoughts
Determine goals for flow and user
management

Centralized vs distributed
Determine types of flows you need to support
in near future
Understand NAAS functionality and limitations
Design for extension, not modification
Share what you learn!
The success of the network depends on you!
Contacts
Bob Cadenhead



TIDEN Project Sponsor
[email protected]
512/239-5848
Bob Jacoby



TIDEN Tech Lead
[email protected]
512/239-4641
Doug Timms



EnfoTech Project Manager
[email protected]
609/896-9777 x129