Hyrax - Configuring The OLFS To Work With Multiple BES's: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(New page: Configuring Hyrax to use multiple BES backends is straight forward. It will require that you edit the '''olfs.xml''' file and possible the '''catalog.xml''' file.)
 
No edit summary
Line 1: Line 1:
Configuring Hyrax to use multiple BES backends is straight forward. It will require that you edit the '''olfs.xml''' file and possible the '''catalog.xml''' file.
=Top Level BES=
Every installation of Hyrax requires a top level (or ''root'' level) BES.** This BES has a ''prefix'' of "/" (the forward slash character).
In a single BES deployment this BES would contain all of the data resources to be made visible in Hyrax. In the THREDDS ''catalog.xml'' file each toplevel directory/collection would have it's own <''datasetScan''> element.
In a multiple BES installation each additional BES must have a ''mount point'' wiithin the exposed hierarchy of collections for it to be visible in Hyrax. (See
<nowiki>**</nowiki>''Note:'' The word ''root'' here has absolutely '''nothing''' to do with the login account called root associated with the super user or system administrator.


=Mount points=


Configuring Hyrax to use multiple BES backends is straight forward. It will require that you edit the '''olfs.xml''' file and possible the '''catalog.xml''' file.
Using multiple BES's requires you to think about the concept of '''mount points'''  
 
=olfs.xml for multiple BES installations=
 
 
Simple Example:

Revision as of 19:20, 22 March 2007

Configuring Hyrax to use multiple BES backends is straight forward. It will require that you edit the olfs.xml file and possible the catalog.xml file.


Top Level BES

Every installation of Hyrax requires a top level (or root level) BES.** This BES has a prefix of "/" (the forward slash character).

In a single BES deployment this BES would contain all of the data resources to be made visible in Hyrax. In the THREDDS catalog.xml file each toplevel directory/collection would have it's own <datasetScan> element.

In a multiple BES installation each additional BES must have a mount point wiithin the exposed hierarchy of collections for it to be visible in Hyrax. (See



**Note: The word root here has absolutely nothing to do with the login account called root associated with the super user or system administrator.

Mount points

Using multiple BES's requires you to think about the concept of mount points

olfs.xml for multiple BES installations

Simple Example: