Hyrax: Difference between revisions
Line 42: | Line 42: | ||
===For Developers:=== | ===For Developers:=== | ||
* [[Hyrax: BES Build Instructions| Building the BES from source.]] | *BES | ||
* | ** [[Hyrax: BES Build Instructions| Building the BES from source.]] | ||
* [[How to Write a New Response Handler for the BES| Writing a Response Handler (data handler) for the BES]] | ** [[How to Write a New Response Handler for the BES| Writing a Response Handler (data handler) for the BES]] | ||
*OLFS | |||
** [[Hyrax: OLFS Build Instructions|Building the OLFS from source.]] | |||
** [[Hyrax: SOAP Test Client|Using the SOAP Test Client.]] | |||
* Java docs for the OLFS Java API (''Do we want to include this?'') | * Java docs for the OLFS Java API (''Do we want to include this?'') | ||
Line 50: | Line 53: | ||
---- | ---- | ||
=Thanks!= | =Thanks!= | ||
Revision as of 06:11, 9 March 2007
This is the OPeNDAP 4 Data Server, also known as Hyrax.
Hyrax is a new data server which combines the efforts at UCAR/HAO to build a high performance DAP-compliant data server for the Earth System Grid II project with existing software developed by OPeNDAP. The server is intended to be a replacement for the existing 3.x servers which OPeNDAP is distributing.
Overview
The new server uses the Java servlet mechanism to hand off requests from a general web daemon to DAP format-specific software. This results in higher performance for small requests. The servlet front end, which we call the OPeNDAP Lightweight Front end Server (OLFS) looks at each request and formulates a query to a second server (which may or may not on the same machine as the OLFS) called the Back End Server (BES).
The BES is the high-performance server software from HAO. It handles reading data from the data stores and returning DAP-compliant responses to the OLFS. In turn, the OLFS may pass these response back to the requestor with little or no modification or it may use them to build more complex responses. The nature of the Inter Process Communication (IPC) between the OLFS and BES is such that they should both be on the same machine or be able to communicate over a very high bandwidth channel.
Both the OLFS and the BES will run and server test data immediately after a default installation. Additional configuration is required for them to serve site specific data..
Features
THREDDS Support
Hyrax supports the complete THREDDS catalog service stack.
SOAP Support
Hyrax supports SOAP requests.
A prototype SOAP interface is included with this release of Hyrax. It is discussed in the RSG template pages here. Example client code can be found at our web site, and can be found in our Subversion archive here.
Documentation
For Users:
- Hyrax Installation instructions
- Hyrax Configuration Instructions
- Hyrax integration with the Apache Web Server
- Release Notes
For Developers:
- BES
- OLFS
- Java docs for the OLFS Java API (Do we want to include this?)
Thanks!
We hope we hope you find this software useful, and we welcome your questions and comments.
Contact Us
Technical Support:
Hyrax Java Development:
- ndp <at> opendap <dot> org
Hyrax C++ Development:
- pwest <at> ucar <dot> edu (bes)
- jgallagher <at> opendap <dot> org (libdap)