1 / 31

TIDEN

TIDEN. Node Management. T exas I ntegrated D ata E xchange N ode. 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.

jalena
Télécharger la présentation

TIDEN

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. TIDEN Node Management Texas Integrated Data Exchange Node Partnered with

  2. Agenda • History of the project • Why did we become involved • TIDEN Overview

  3. History of the project • 2002 Grant • Prepare infrastructure • 2003 Grant • Build Node • 2004 Grant • Add data flows

  4. Why did we become involved • Each Program area had different process • Foundation for future electronic reporting • Lessons learned

  5. TIDEN Vitals TIDEN is a J2EE application

  6. TIDEN Overview • TIDEN Top 4 Features • TIDEN as a Framework • User Management • Domains • Status

  7. TIDEN as a Framework

  8. 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

  9. 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>)

  10. 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

  11. Adding a TIDEN Operation

  12. Lessons Learned • Understand the specs/protocols • Understand the relationship between Web Methods • Initially focus on Web Methods and relationships you know you need

  13. User Management

  14. 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

  15. 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 scope (spec/protocol Web Service Methods) • Limited authorization granularity • Limited management capabilities (e.g. - GUI) • Limited control All Nodes must support NAAS tokens!

  16. NAAS Interface

  17. User Management • Use NAAS Web Services to: • Manage NAAS Users and Policies • Provide GUI Management • Extend NAAS

  18. TIDEN Interface: Summary

  19. TIDEN Interface: New User

  20. 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

  21. Domains

  22. 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

  23. 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.

  24. Lessons Learned • Domains should be logical • Need special “Node” Domain • Domain Admins can modify any TX Node User

  25. What’s your Status?

  26. 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?

  27. Status Page: Splash Page

  28. Status Page: More Details

  29. Lessons Learned • Use GetServices or not? • How much information?

  30. 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!

  31. Contacts • Bob Cadenhead • TIDEN Project Sponsor • Bcadenhe@tceq.state.tx.us • 512/239-5848 • Bob Jacoby • TIDEN Tech Lead • Rjacoby@tceq.state.tx.us • 512/239-4641 • Doug Timms • EnfoTech Project Manager • Douglas_timms@enfotech.com • 609/896-9777 x129

More Related