Hyrax - Configuration: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary
No edit summary
 
Line 1: Line 1:
'''When you install Hyrax for the first time it is pre-configured to serve test data sets that come with each of the installed data handlers. This will allow you to test the server and make sure it is functioning correctly. After that you can customize it for your data.'''
'''When you install Hyrax for the first time it is pre-configured to serve test data sets that come with each of the installed data handlers. This will allow you to test the server and make sure it is functioning correctly. After that you can customize it for your data.'''
<!-- This could turn off users - nothing worse than saying up front 'it is hard'
Hyrax configuration is straight forward with one important caveat: Because the OLFS provides a particular view of the data and THREDDS can provide a slightly different view, it is very important that the configuration of the THREDDS catalogs and the BES are coordinated. In particular this means that each top level data set (be it a collection or an "atomic data set") that the BES exposes must have a separate <''datasetScan''> entry in the THREDDS catalog.
Confused? Hopefully you won't be after you've read the following documents. -->


== [[Hyrax - BES Configuration|BES configuration]]==
== [[Hyrax - BES Configuration|BES configuration]]==

Latest revision as of 22:30, 16 February 2011

When you install Hyrax for the first time it is pre-configured to serve test data sets that come with each of the installed data handlers. This will allow you to test the server and make sure it is functioning correctly. After that you can customize it for your data.

BES configuration

OLFS configuration

THREDDS Configuration

Logging configuration

Robots

To correctly deploy a robots.txt file for Hyrax, you must correctly deploy it for Tomcat. This means that your robots.txt file must be accessible here:

   http://you.host:port/robots.txt

For example:

   http://www.opendap.org/robots.txt

Placing it lower in the URL path doesn't seem to work.

In order to get Tomcat to serve the file from that location you must place it in $CATALINA_HOME/webapps/ROOT

If you still find that you system is being cruelly burdened with robot traffic then you might want to try the BotBlocker handler for the OLFS.