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

From OPeNDAP Documentation
(Multiple BES examples)
Line 50: Line 50:
 
     </Handler>
 
     </Handler>
 
</pre>
 
</pre>
The first one is running on the same system as the OLFS< the second on ''comet. test.org''. The second BES is mapped to the prefix /sst. So the URL:
+
The first one is running on the same system as the OLFSthe second on ''comet. test.org''. The second BES is mapped to the prefix /sst. So the URL:
 
  http://localhost:8080/opendap/
 
  http://localhost:8080/opendap/
 
Will return the directory view at the top level of the first BES, running on the same system ads the OLFS. The URL:
 
Will return the directory view at the top level of the first BES, running on the same system ads the OLFS. The URL:

Revision as of 21:54, 20 April 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.


1 Top Level (root) 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 top level directory/collection would have it's own <datasetScan> element.


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

2 Single BES Example (Default)

Here is the <Handler> element in an olfs.xml that defines the opendap.bes.BESManager file that configures the OLFS to use a single BES, the default configuration arrangement for Hyrax:

    <Handler className="opendap.bes.BESManager">
        <BES>
            <prefix>/</prefix>
            <host>localhost</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
    </Handler>

The BES is running on the same system as the OLFS, and it's prefix is correctly set to "/". This BES will handle all data requests directed at the OLFS and will expose it's top level directory/collection/catalog in the URI space of the OLFS here:

http://localhost:8080/opendap/

The THREDDS catalog.xml file for this should contain a <datasetScan> element for each of the top level directories | collections | catalogs that the BES exposes at the above URI.

Remember: There must be one (but only one) BES configured with the <prefix> set to "/" in your olf.xml file.

3 Multiple BES examples

Here is a BESManager <Handler> element that defines two BES's:

    <Handler className="opendap.bes.BESManager">

        <BES>
            <prefix>/</prefix>
            <host>localhost</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/sst</prefix>
            <host>comet.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>

    </Handler>

The first one is running on the same system as the OLFS, the second on comet. test.org. The second BES is mapped to the prefix /sst. So the URL:

http://localhost:8080/opendap/

Will return the directory view at the top level of the first BES, running on the same system ads the OLFS. The URL:

http://localhost:8080/opendap/sst

Will return the directory view at the top level of the second BES, running on comet.test.org.

You can repeat this parrtn to add more BES's to the configuration. This next example shows a configuration with 4 BES's: The root BES, and 3 others:

    <BESConfig>

        <BES>
            <prefix>/</prefix>
            <host>server0.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/sst</prefix>
            <host>server1.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>

        <BES>
            <prefix>/chl-a</prefix>
            <host>server2.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>

        <BES>
            <prefix>/salinity</prefix>
            <host>server3.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>

    </BESConfig>

Note that in this example:

  1. The root BES is not necessarily running on the same host as the OLFS.
  2. Every BES has a different prefix.
  3. The OLFS would direct requests so that requests to:

4 Mount points

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

Consider, if you have this configuration:

    <BESConfig>

        <BES>
            <prefix>/</prefix>
            <host>server0.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
    </BESConfig>

And the top level directory for the root BES looks like this:

Top Level Directory

If you add another BES, like this:

    <BESConfig>

        <BES>
            <prefix>/</prefix>
            <host>server0.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/sst</prefix>
            <host>server5.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
    </BESConfig>

It will not appear in the top level directory unless you create a mount point. This simply means that on the file sytem served by the root BES you would need to create a directory called "sst" in the top of the directory tree that the root BES is exposing. In other words, simply create a directory called "sst" in the same directory that contains the "Test" and "data" directories on server0.test.org. After you did that your top level directory would look like this:

Top Level Directory

This holds true for any arrangement of BESs that you make. The location of the mount point will depend on your configuration, and how you organize things. Here is a more complex example.

Consider this configuration:

    <BESConfig>

        <BES>
            <prefix>/</prefix>
            <host>server0.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature </prefix>
            <host>server1.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica</prefix>
            <host>server2.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica/Canada </prefix>
            <host>server3.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica/USA </prefix>
            <host>server4.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/Europe/France </prefix>
            <host>server4.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
    </BESConfig>
  • The mount point "GlobalTemperature" must be in the top of the directory tree that the root BES on server0.test.org is exposing.
  • The mount point "NorthAmerica" must be in the top of the directory tree that the BES on server1.test.org is exposing.
  • The mount point "Canada" must be in the top of the directory tree that the BES on server2.test.org is exposing.
  • The mount point "USA" must be in the top of the directory tree that the BES on server2.test.org is exposing.
  • The mount point "France" must be located at "GlobalTemperature/Europe/France" relative to the top of the directory tree that the BES on server0.test.org is exposing.

5 Complete olfs.xml with multiple BES installations example

<OLFSConfig>
    <BESConfig>

        <BES>
            <prefix>/</prefix>
            <host>server0.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature </prefix>
            <host>server1.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica</prefix>
            <host>server2.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica/Canada </prefix>
            <host>server3.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica/USA </prefix>
            <host>server4.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/Europe/France </prefix>
            <host>server4.test.org</host>
            <port>10002</port>
            <ClientPool maximum="10" />
        </BES>
        
    </BESConfig>

      <!-- Used to indicate which type of directory view clients see. This DOES NOT
           affect the THREDDS catalogs! Only the HTML views of them. A value
           of "THREDDS" will provide the THREDDS directory view and a value
           of "OPeNDAP" will produce the OPeNDAP directory view.-->

      <DirectoryView>THREDDS</DirectoryView>

      <!-- AllowDirectDataSourceAccess
         - If this element is opresent then the server will allow users to request
         - the data source (file) directly. For example a user could just get the
         - underlying NetCDF files located on the server without using the OPeNDAP
         - request interface.
         -
         - THINK TWICE before allowing this, as data sources can be quite large
         - and allowing their transmission with out subsetting can put heavy loads
         - on the network and the server.
         -->
      <!-- <AllowDirectDataSourceAccess /> -->

</OLFSConfig>