Data Exchange through XMLData Exchange through XML

Environmental InformationEnvironmental InformationExchange NetworkExchange Network

www.exchangenetwork.netwww.exchangenetwork.netMay 21, 2003May 21, 2003

Louis Sweeny

Background on the State / EPA Background on the State / EPA Exchange NetworkExchange Network

States and EPA need each other’s dataStates and EPA need each other’s data Over past 35 years, EPA and States have developed Over past 35 years, EPA and States have developed

scores of individual systemsscores of individual systems Like everyone else EPA and States are looking at inter Like everyone else EPA and States are looking at inter

and intra organization integration but how?and intra organization integration but how? Data exchange options were:Data exchange options were:

State use, or double entry into Federal system (terminal, client State use, or double entry into Federal system (terminal, client server or Web)server or Web)

““Translator” systems with manual batch upload/download (FTP, Translator” systems with manual batch upload/download (FTP, remote access, email, CD)remote access, email, CD)

• But neither sending nor receiving systems were designed with this But neither sending nor receiving systems were designed with this as their primary function…many difficulties and much manual effort.as their primary function…many difficulties and much manual effort.

Background on the State / EPA Background on the State / EPA Exchange NetworkExchange Network

Trends indicated a need to do betterTrends indicated a need to do better Most states were rapidly migrating away from primary Most states were rapidly migrating away from primary

use of EPA systems, and re-engineering systems use of EPA systems, and re-engineering systems they hadthey had

EPA was re-engineering many of its systemsEPA was re-engineering many of its systems State and EPA needing more data, from more State and EPA needing more data, from more

partners, more often, and old approach of individual partners, more often, and old approach of individual translators would not scaletranslators would not scale

State/EPA Information Management Workgroup State/EPA Information Management Workgroup charged a team to develop a common charged a team to develop a common blueprint/vision for information exchangeblueprint/vision for information exchange

Blueprint Team Proposed A Blueprint Team Proposed A Network With These ComponentsNetwork With These Components

Data StandardsCommon way to define

shared terms

Member InfrastructureCapacity to participate

Data Exchange Templates

Common way to package shared data

Trading Partner

AgreementHow information flows

between partners

ExchangeNetwork

Components

Network Administration

Registration, process support,

communication

Technical InfrastructureUses standard Internet tools

Traditional Web Services StackTraditional Web Services Stack

DiscoveryDescription

UDDIWSDL

XML Messaging

SOAP, XML

Transport HTTP/HTTPS

Security SSL

Universal Description, Discovery and Integration

Web Services Description Language

Simple Object Access Protocol

eXtensible Markup Language

Secure Sockets Layer

HyperText Transfer Protocol

How this stack is adapted for the How this stack is adapted for the technical infrastructure of the technical infrastructure of the

NetworkNetworkNetwork Exchange Business ProcessesNetwork Exchange Business Processes

What are the high level business processes supported e.g. monthly reportingWhat are the high level business processes supported e.g. monthly reporting

Flow Configuration InformationFlow Configuration Information(including how transactions are configured for system updates)(including how transactions are configured for system updates)

Protocol and Protocol and Specification WSDLSpecification WSDL

What primitive web services to we share?What primitive web services to we share?DET GuidelinesDET Guidelines

How we use XML to format dataHow we use XML to format data

SOAPSOAPHow payloads are packagedHow payloads are packaged

XMLXMLUse XML to format data Use XML to format data

Netw

ork Specificity

EN Specific

Generic

Node

Schema based payload

Network Overview and Network Overview and InfrastructureInfrastructure

InternetInternet

DET/SchemaGuidelines

Protocol&

Specification

Registry

WA Information System

Node

Information System

Information Consumer

Schema based payload

NAAS

The Network Node Supports The Network Node Supports Four Basic OperationsFour Basic Operations

AdministeringAdministering: Security and Housekeeping.: Security and Housekeeping. QueryingQuerying: Querying a partner for some data.: Querying a partner for some data. SendingSending: Send a set of data to a partner.: Send a set of data to a partner. RetrievingRetrieving : Retrieving from a partner a : Retrieving from a partner a

standard set of data.standard set of data.

Protocol Establishes 11 Network Protocol Establishes 11 Network MethodsMethods

Retrieving Notify, Download, Solicit

Administration NodePing, GetServices

Interface Methods

Sending Submit, GetStatus

Querying Query, Execute

* Currently under development by EPA/CDX

Authenticate, Validate CentralAuth* Security

Network/Node Usage OptionsNetwork/Node Usage Options

Business NeedCurrent Approach

Network Options

Node Operation

Automatic request for ad-hoc information

Custom software

Node to Node, or client to Node

Query (Pull)

Automated collection of data from multiple peers

Multiple Telephone Calls

Node to Node interactions

Solicit/Query (Pull)

Routine Information Sharing with a Peer (especially secured or confirmed)

Batch uploads, email, FTP

Node to Node, or use of a hosted node.

Solicit/Download /Query (Pull)

Submit (Push)

Periodic/ Occasional Information sharing with a Peer

E-mail Attachments, FTP, Website posting

NA, unless volume or frequency increases (see below)

NA

Service Other Nodes: support aggregation of data from Service Other Nodes: support aggregation of data from other Nodes that can then be displayed on a website. other Nodes that can then be displayed on a website.

Service Clients: submit retrieval data from a Node using Service Clients: submit retrieval data from a Node using a simple client. a simple client.

Integrate Applications: where a local application Integrate Applications: where a local application (webpage, model or report) retrieves information from (webpage, model or report) retrieves information from one or more Nodes as needed. one or more Nodes as needed.

Provide Node Services: use a “hosted” Node, that Provide Node Services: use a “hosted” Node, that interacts with other Nodes as a client, but puts data on interacts with other Nodes as a client, but puts data on the Network. the Network.

Network Nodes can be used to:Network Nodes can be used to:

Putting it all Together in an Putting it all Together in an Exchange: GetFacilityByIDExchange: GetFacilityByID

Authenticate(userId, credential authMethod)

GetFacilityByID (securityToken, parameters – State: WA, State Facility ID: 12345)

securityToken()

Facility Information

GetFacilityByIDResponse()

NAASRequestor Provider

Node 1.0 Protocol Interoperability Node 1.0 Protocol Interoperability Testbeds: MiddlewareTestbeds: Middleware

State Middleware

DE .NET 1.0

ME Oracle 9iAS

MS .NET 1.0

NH BizTalk Server 2000

NM WebSphere v4.05

NE XAware XA-Suite

UT Sybase EASserver

CDX BEA WebLogic

First Generation Network Security:First Generation Network Security: Centralized Network Authentication Centralized Network Authentication

& Authorization Service& Authorization Service Given immaturity of web services a simple, centralized Given immaturity of web services a simple, centralized

service was implementedservice was implemented Decided that it easier to start with “locked down” Decided that it easier to start with “locked down”

approach and then loosen security as appropriateapproach and then loosen security as appropriate Much of this information is public, and on public websites, Much of this information is public, and on public websites,

some partners will likely launch public web services some partners will likely launch public web services Finalizing a model for how authorization services will be Finalizing a model for how authorization services will be

managedmanaged Nodes will likely implement additional layers of Nodes will likely implement additional layers of

authorization internally (at node, procedure and authorization internally (at node, procedure and database levels)database levels)

Three Quick Lessons LearnedThree Quick Lessons Learned

The web services metaphor, roles and The web services metaphor, roles and responsibilities are as important to an effort like responsibilities are as important to an effort like this as the technology.this as the technology.

Immaturity in Web Services Standards and Immaturity in Web Services Standards and Tools but they are improving rapidly.Tools but they are improving rapidly.

Many current reporting processes are “semi-Many current reporting processes are “semi-automated”, moving these to fully automated automated”, moving these to fully automated requires addressing many additional requires addressing many additional details/refinements.details/refinements.

Web Services as a Metaphor for Cross-Web Services as a Metaphor for Cross-Organizational CollaborationOrganizational Collaboration

The web services metaphor, roles and responsibilities The web services metaphor, roles and responsibilities are as important to an effort like this as the technologyare as important to an effort like this as the technology

Provides a framework for collaborationProvides a framework for collaboration More useful than “cooperate” or “build inter-operable systems” More useful than “cooperate” or “build inter-operable systems”

or “use standards” or all the other euphemisms we use.or “use standards” or all the other euphemisms we use. Provides cleaner Provides cleaner separationseparation of what is behind and in front of what is behind and in front

of the firewallof the firewall Allows incremental progress, makes clear EXACTLY what Allows incremental progress, makes clear EXACTLY what

each partner has to do (i.e. consume or produce these each partner has to do (i.e. consume or produce these messages)messages)

Adoption of cross-organizational web services may be Adoption of cross-organizational web services may be FASTER (!) in government than the marketFASTER (!) in government than the market

For More InformationFor More Information

Environmental Exchange NetworkEnvironmental Exchange Networkwww.exchangenetwork.netwww.exchangenetwork.net

Justice XML InitiativesJustice XML Initiativeshttp://it.ojp.gov/topic.jsp?topic_id=43http://it.ojp.gov/topic.jsp?topic_id=43

Shameless plug:Shameless plug:

If your agency deals with data in anyway If your agency deals with data in anyway related to environment/natural related to environment/natural

resources/health…partner with ecology on resources/health…partner with ecology on a project and/or Network Grant!a project and/or Network Grant!