1 / 17

The Exchange Network Virtual Node 5/30/2012

The Exchange Network Virtual Node 5/30/2012. Topics. Why a Virtual Node What is the Virtual Node Concept Advantages A Node in the Cloud Basics - Components Architecture Services Admin user Interface Partner Database Connectivity with the Virtual Node Data Mapping Development Status

alban
Download Presentation

The Exchange Network Virtual Node 5/30/2012

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. The Exchange Network Virtual Node5/30/2012

  2. Topics • Why a Virtual Node • What is the Virtual Node Concept • Advantages • A Node in the Cloud • Basics - Components • Architecture • Services • Admin user Interface • Partner Database Connectivity with the Virtual Node • Data Mapping • Development Status • Demo

  3. Why a Virtual Node • Provide a Low Cost Node Option for Partners • Decrease Operations and Maintenance Costs • Simplify Development and Maintenance

  4. What is the Virtual Node • A central node server that hosts any number of partner nodes: state, tribe, region, agency, etc.. • Each partner node is simply configured on the central or cloud server from a web application • Each partner node functions like a conventional node only it is much simpler and cheaper to set up and maintain

  5. Virtual Node Advantages • Low Cost: Costs should be significantly lower compared with a traditional node • Highly Agile: A new partner node can be created with a simple configuration form • Enhanced Manageability: Nodes are centrally managed, secured and serviced • Common Architecture: New features will be shared by all nodes • Virtual nodes can ‘inherit’ services from the base-node • The ENDS service information can be maintained automatically

  6. Virtual Node in the Cloud • Nodes are moved to the cloud, not the databases. • Nodes connect to databases through a secure backend bridge or VPN. • A node admin controls each node, and how it accesses the their databases.

  7. Basic Components 1) Virtual node server 2) Secure database connections 3) Admin User Interface

  8. Physical Server Virtual Machines Virtual Node Node Implementations Virtual Machine Virtual Machine Tribe1 Tribe1 Tribe2 Tribe2 State1 State1 State2 State2 Physical Server State3 State3 Agency1 Agency1 Agency2 Agency2 Agency.. Agency.. Virtual Node Virtual Node NAAS QA Server VMWARE

  9. Virtual Node 9

  10. ENVN Web Services • The ENVN is a node with its own web services description language : • Node Management: CreateNode, UpdateNode, DeleteNode and GetNodeList. • New nodes are created by the helpdesk • Service Management: CreateService, UpdateService, DeleteService and GetServiceList – • Services could be automatically published to ENDS • Dataflow Management: CreateDataflow, UpdateDataflow, DeleteDataflow and GetDataflowList. • Task Management: CreateTask, UpdateTask, DeleteTask and GetTaskList • Used to schedule tasks

  11. Test User | Profile | Logout Home | About | FAQs | Help Virtual Node Administration Platform (VNAP) Services Setup Wizard Node Dashboard Service Settings Steps • Database • Service • Template • Finish Method Type Explanation of Fields Review these requirements to ensure your node is working. Workflow Service Status cgi.oracle.test Select a workflow… Solicit Enabled V V V V Service Description Display all water transaction data Data Source Please select an existing data source and provide SQL statement to test SQL Statement SELECT * FROM {TABLE} WHERE {FIELD}.{TABLE} TEST QUERY

  12. Secure Database Connection Options • Based on a partner’s internal security requirements, they might choose: • Virtual Private Network Connection • Backend Relay with Internet Service Bus (ISB) • Direct Backend Database Bridge • Backend Relay with AppFabric

  13. VN Mapping Process

  14. Two Key Steps 1. Data Mapping: Create a one to one relationships between data columns and XML elements (Map Force, SQL Query Builder, Oracle Query Designer) 2. Structure Construction: Put the XML element into hierarchy at the correct position using XLST (XSLT style-sheet is simplified and generated – not coded)

  15. XML Mapping & Transformation

  16. Current Development • Virtual Node Server: The central node server has been designed and prototyped. Nodes, services, and tasks have been created and tested. • Secure Database Connections: Secure processes for connecting to State databases have been designed and developed. We are testing remote database connections from the virtual node to our EPA Clydesdale database server. A sample database has been integrated simplify the creation of test services by partner administrators. • Admin User Interface: A graphical user interface is under design. Wireframes have been generated. Features and functions are being designed.

  17. Questions to YOU! • Who is potentially interested in this kind of Node? • What are the critical features? • Open Node Plug-in support? • Mapping tool? • REST support? • What governance model do we use? • Are you interested in helping guide the development? Joining a design committee?

More Related