Windsor Node 2008
From Exchange Network Wiki
Contents |
Windsor Node 2008
Windsor’s Node 2008 is the latest release of the most widely employed Node on the network. Since implementing the Network’s first production Node in 2003, Windsor’s Node has evolved to support every challenge posed and innovation demanded by the expanding Network, Windsor’s 2.0-compliant Node is a proven solution and comes with many data flow already completed and available. Node users have most of the work already done for them and in some cases need only point the plugins to the appropriate data source (for instance a file location, Excel spreadsheet, or database) in order to finalize the data flow.
This Node provides a robust, scalable, secure, and flexible solution to the Exchange Network. Supporting both Node 1.1 and Node 2.0 specifications and being available in both .NET and Java platforms, it builds upon the success of Windsor’s previous version, which has been deployed in over thirty organizations. Windsor Node 2008 leads in its robust and widely proven architecture, friendly API for developers, and scalability across networks.
For more information about Windsor’s Node, please email Craig Austin or visit Windsor’s Website.
Key Features
Dual Web service endpoints
Windsor Node 2008 is a multiplatform solution that natively supports both Node 1.1 and Node 2.0 specifications. This is implemented using dual Web service endpoints. Behind the endpoints, the data exchange communicates through a common message structure, allowing for maximum flexibility across different specifications.
Multiple Data Source Support
Both the Windsor Node 2008 metadata repository and staging database (referred to as Data Sources within the Node Administration application) can be configured with any JDBC/ODBC provider on a wide variety of platforms. Some of the most common data source providers already supported are:
- SQL Server (2000, 2005, & 2008 as well as the Express editions of these versions)
- Oracle (9i, 10g, & 11g as well as the Lite editions of these versions where available)
- DB2 (7, 8, and 9 in either the Enterprise or Express editions)
- Sybase (11, 12, 12.5, and 15 as well as through Intersolv providers 3.10 & 3.60 and Sybase SQL Anywhere in the form of ODBC)
Beyond traditional relational database sources, Windsor Node 2008 can also support additional data sources in the form of one of the following:
- File system (flat-file, staged XML, spatial data, binary content, etc.)
- External Web services that may or may not be supporting the Exchange Network WSDL
- Remoting sources supported by the specific platform (Corba, MQ, RMI, HTTP Invokers, Hessian, Burlap, JAX RPC, JMS, etc.)
- Email mailbox as an inbound data source either through POP or IMAP and SMTP as the outbound protocol
Workflow Support
Windsor Node 2008 supports custom, multistep data processes by defining a series of event triggers that can be associated with individual plugins. This effectively works as a workflow to ensure the highest quality of data. Each event trigger can be accompanied by a series of notifications and detailed activity logging, and can be viewed from the Node Administration Dashboard.
Platform Independence
Windsor Node 2008’s data source and target definition, as well as its data flow configuration, are entirely transferable across the deployments performed in Java and .NET regardless of the underlying metadata repository store.
Node Administration Application
The Node Admin is a Web-based user interface for accessing and managing the Exchange Node functionality. This includes configuring plugins, workflows, schedules, and more.
Additional Key Features
- Common message structure
- Easy Plug-in/Data Flow Configuration
- Flow Scheduling
- Node Orchestration Service
- Content Manager
- Node Data Store
- Object serialization
- Email notification
- File compression
- Exchange Network Client invocation
- XML validation
Agencies Implementing a Windsor Node
- Alaska Department of Environmental Conservation
- Arizona Department of Environmental Quality
- Arkansas Department of Environmental Quality (Node 2008—.NET)
- California Environmental Protection Agency
- Colorado Department of Public Health and Environment (Node 2008—.NET)
- Connecticut Department of Environmental Protection
- Georgia Department of Natural Resources
- Hawaii Department of Health
- Iowa Department of Natural Resources
- Illinois Environmental Protection Agency
- Kansas Department of Agriculture
- Kansas Department of Health and Environment
- Marianas Islands Department of Environmental Quality
- Massachusetts Department of Environmental Protection
- Minnesota Pollution Control Authority
- Missouri Department of Natural Resources
- Nebraska Department of Environmental Quality
- Nevada Division of Environmental Protection (Node 2008—.NET)
- New Mexico Environment Department
- New York Department of Environmental Conservation (Node 2008—Java)
- New York Department of Health (Node 2008—Java)
- North Dakota Department of Health (Node 2008 - .NET)
- Oklahoma Department of Environmental Quality
- Oklahoma Department of Agriculture
- Pollution Prevention Resource Council (Node 2008—.NET)
- Snohomish County, Washington
- Stillaguamish Tribe of Indians
- Seldovia Village Tribe
- Tennessee Department of Environment and Conservation
- USGS (Node 2008—.NET)
- Washington Department of Ecology (Node 2008—.NET)
- Washington Department of Natural Resources
- Wyoming Department of Environmental Quality
