Hyrax: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary
No edit summary
Line 2: Line 2:


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.
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 '''O'''PeNDAP '''L'''ightweight '''F'''ront end '''S'''erver (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 '''B'''ack '''E'''nd '''S'''erver (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.
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 '''O'''PeNDAP '''L'''ightweight '''F'''ront end '''S'''erver (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 '''B'''ack '''E'''nd '''S'''erver (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.
Line 7: Line 9:
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..
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..


@TODO: '''''We need (more?) text here with  information on the server architecture and roles of the two parts of the server. Maybe some pictures, etc.'''''


----
=Overview=
@TODO: '''''We need text here with  information on the server architecture and roles of the two parts of the server. Maybe some pictures, etc.'''''
----


==Features==
==Features==
Line 26: Line 20:


A prototype SOAP interface is included with this release of Hyrax. It is discussed in the [http://rsg.opendap.org:8090/server-4/templates/soapAPI.html RSG template pages here]. Example client code can be found at our [http://www.opendap.org/download/hyrax.html web site], and can be found in our [http://scm.opendap.org:8090/trac/browser/tags/SoapTestClient Subversion archive here].
A prototype SOAP interface is included with this release of Hyrax. It is discussed in the [http://rsg.opendap.org:8090/server-4/templates/soapAPI.html RSG template pages here]. Example client code can be found at our [http://www.opendap.org/download/hyrax.html web site], and can be found in our [http://scm.opendap.org:8090/trac/browser/tags/SoapTestClient Subversion archive here].


----
----

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

@TODO: We need (more?) text here with information on the server architecture and roles of the two parts of the server. Maybe some pictures, etc.


Features

THREDDS Support

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:


For Developers:

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



Sponsorship

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