The Exchange Network Virtual Node 5/30/2012

17
The Exchange Network Virtual Node 5/30/2012

description

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 - PowerPoint PPT Presentation

Transcript of The Exchange Network Virtual Node 5/30/2012

Page 1: The Exchange Network  Virtual Node 5/30/2012

The Exchange Network Virtual Node

5/30/2012

Page 2: The Exchange Network  Virtual Node 5/30/2012

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

2

Topics

Page 3: The Exchange Network  Virtual Node 5/30/2012

Provide a Low Cost Node Option for Partners

Decrease Operations and Maintenance Costs

Simplify Development and Maintenance

Why a Virtual Node

Page 4: The Exchange Network  Virtual Node 5/30/2012

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

4

What is the Virtual Node

Page 5: The Exchange Network  Virtual Node 5/30/2012

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

5

Virtual Node Advantages

Page 6: The Exchange Network  Virtual Node 5/30/2012

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.

6

Virtual Node in the Cloud

Page 7: The Exchange Network  Virtual Node 5/30/2012

1) Virtual node server

2) Secure database connections

3) Admin User Interface

7

Basic Components

Page 8: The Exchange Network  Virtual Node 5/30/2012

8

Physical Server Virtual Machines Virtual Node

Node Implementations

VirtualMachin

eVirtual

Machine

QA ServerNAASVirtualNode

Tribe1Tribe2State1State2State3

Agency1Agency2Agency..

Physical Server

VMWARE

VirtualNode

Tribe1Tribe2State1State2State3

Agency1Agency2Agency..

Page 9: The Exchange Network  Virtual Node 5/30/2012

9Virtual Node

Page 10: The Exchange Network  Virtual Node 5/30/2012

• 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

10

ENVN Web Services

Page 11: The Exchange Network  Virtual Node 5/30/2012

Virtual Node Administration Platform (VNAP)

Home | About | FAQs | Help

Test User | Profile | Logout

Node Dashboard Services Setup Wizard

Method Type

Service Status

Service DescriptionDisplay all water transaction data

Data Source

TEST QUERY

Solicit V

Please select an existing data source and provide SQL statement to test

Steps1. Database2. Service3. Template4. Finish

Service Settings

Enabled V

SQL Statement

SELECT * FROM {TABLE} WHERE {FIELD}.{TABLE}

cgi.oracle.test V

Workflow

Node ID / Description:CWANJ - Clean Water Act NJ WaterwaysDataflow:CWANJ

Select a workflow… V

Explanation of FieldsReview these requirements to ensure your node is working.

11

Page 12: The Exchange Network  Virtual Node 5/30/2012

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

12

Secure Database Connection Options

Page 13: The Exchange Network  Virtual Node 5/30/2012

VN Mapping Process

Page 14: The Exchange Network  Virtual Node 5/30/2012

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)

Page 15: The Exchange Network  Virtual Node 5/30/2012

XML Mapping & Transformation

Page 16: The Exchange Network  Virtual Node 5/30/2012

1) Virtual Node Server:The central node server has been designed and prototyped. Nodes, services, and tasks have been created and tested.

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

3) Admin User Interface: A graphical user interface is under design. Wireframes have been generated. Features and functions are being designed.

16

Current Development

Page 17: The Exchange Network  Virtual Node 5/30/2012

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?

17

Questions to YOU!