Difference between revisions of "Hyrax"

From OPeNDAP Documentation
(Contact Us)
(For Developers:)
Line 54: Line 54:
** [[Hyrax: BES Build Instructions| Building the BES from source.]]
** [[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]]
** [[Create BES Module | How to create your own BES Module]]
** [[Extending BES Module | Extending your BES Module]]
** [[Hyrax: OLFS Build Instructions|Building the OLFS from source.]]
** [[Hyrax: OLFS Build Instructions|Building the OLFS from source.]]

Revision as of 01:02, 10 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.

1 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 serve test data immediately after a default installation. Additional configuration is required for them to serve site specific data.

1.1 Features

THREDDS Catalog Support
Hyrax supports the complete THREDDS catalog service stack.
SOAP Messaging 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.
Plugin Format and Response Handlers
The Back-End Server (BES) used with Hyrax supports run-time loading of handlers for different formats and different response types (e.g., the ASCII response and the HTML form interface). To replace one of the standard handlers, or to add a new one, edit the bes.conf file.
Simple Conversion from the Old-style Handlers
It is fairly simple to convert handlers written for the older OPeNDAP server to run-time loadable modules for the BES.
Feature Request
Is there a feature you would like to see but don't? Let us know: support@unidata.ucar.edu or opendap-tech@unidata.ucar.edu (You need to subscribe first)

@TODO: Add a more comprehensive listing of the Hyrax feature set.

2 Documentation

2.1 For Users:

2.2 For Developers:

3 Thanks!

We hope we hope you find this software useful, and we welcome your questions and comments.

3.1 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)

3.2 Sponsorship

3.2.1 OPeNDAP Hyrax development is sponsored by:

Nsf-logo.png National Science Foundation

Nasa-logo.jpg National Aeronautics and Space Administration

Noaa-logo.jpg National Oceanic and Atmospheric Administration