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

From OPeNDAP Documentation
(Single BES Example)
 
(24 intermediate revisions by one other user not shown)
Line 2: Line 2:
  
  
=Top Level BES=
+
=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).
+
Every installation of Hyrax requires a top level (or ''root'' level) BES.** This BES has a ''prefix'' of "/" (the forward slash character). The prefix is a URL token between the server address/port and catalog root used to designate a particular BES instance in the case that multiple Back-End-Servers are available to a single OLFS. The default (for a single BES) is no additional tag, designated by "/". The prefix is used to provide a mapping for each BES connected to the OLFS to URI space serviced by the OLFS.
  
 
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.
 
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.
Line 11: Line 11:
 
<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.
 
<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=
+
=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:
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. ''Eh? What's that you said?'' Allow me to explain by example.
 
 
 
==Single BES Example (Default)==
 
Here is the <''BESConfig''> section of an '''olfs.xml''' file that configures the OLFS to use a single BES, the default configuration arrangement for Hyrax:
 
 
<pre>
 
<pre>
     <BESConfig>
+
     <Handler className="opendap.bes.BESManager">
 
         <BES>
 
         <BES>
 
             <prefix>/</prefix>
 
             <prefix>/</prefix>
 
             <host>localhost</host>
 
             <host>localhost</host>
             <port>10002</port>
+
             <port>10022</port>
 
             <ClientPool maximum="10" />
 
             <ClientPool maximum="10" />
 
         </BES>
 
         </BES>
     </BESConfig>
+
     </Handler>
 
</pre>
 
</pre>
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 direct at the OLFS and will expose it's top level directory/collection/catalog in the URI space of the OLFS here:
+
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/
 
  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.
+
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 (and only one) BES configured like this (with the <''prefix''> set to "/") in your '''olf.xml''' file.
+
'''''Remember''''': There '''must''' be one (but only one) BES configured with the <''prefix''> set to "/" in your '''olf.xml''' file.
  
==2 BES example==
+
=Multiple BES examples=
 +
Here is a BESManager <''Handler''> element that defines two BES's:
 +
<pre>
 +
    <Handler className="opendap.bes.BESManager">
  
Here is the <''BESConfig''> section of an '''olfs.xml''' file that defines two BES's:
 
<pre>
 
    <BESConfig>
 
 
         <BES>
 
         <BES>
 
             <prefix>/</prefix>
 
             <prefix>/</prefix>
 
             <host>localhost</host>
 
             <host>localhost</host>
             <port>10002</port>
+
             <port>10022</port>
 
             <ClientPool maximum="10" />
 
             <ClientPool maximum="10" />
 
         </BES>
 
         </BES>
Line 48: Line 44:
 
             <prefix>/sst</prefix>
 
             <prefix>/sst</prefix>
 
             <host>comet.test.org</host>
 
             <host>comet.test.org</host>
             <port>10002</port>
+
             <port>10022</port>
 
             <ClientPool maximum="10" />
 
             <ClientPool maximum="10" />
 
         </BES>
 
         </BES>
     </BESConfig>
+
 
 +
     </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 as the OLFS. The URL:
 
  http://localhost:8080/opendap/sst
 
  http://localhost:8080/opendap/sst
 
Will return the directory view at the top level of the second BES, running on ''comet.test.org''.
 
Will return the directory view at the top level of the second BES, running on ''comet.test.org''.
  
=olfs.xml for multiple BES installations=
+
You can repeat this pattern to add more BES's to the configuration. This next example shows a configuration with 4 BES's: The ''root'' BES, and 3 others:
 +
<pre>
 +
    <Handler className="opendap.bes.BESManager">
  
=Examples=
+
        <BES>
 +
            <prefix>/</prefix>
 +
            <host>server0.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
        <BES>
 +
            <prefix>/sst</prefix>
 +
            <host>server1.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
  
==Simple==
+
        <BES>
 +
            <prefix>/chl-a</prefix>
 +
            <host>server2.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
  
==Complex==
+
        <BES>
 +
            <prefix>/salinity</prefix>
 +
            <host>server3.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
 
 +
    </Handler>
 +
</pre>
 +
 
 +
Note that in this example:
 +
# The ''root'' BES is not necessarily running on the same host as the OLFS.
 +
# Every BES has a different prefix.
 +
# The OLFS would direct requests so that requests to:
 +
#* http://localhost:8080/opendap/sst/* are handled by the BES at server1.test.org
 +
#* http://localhost:8080/opendap/chl-a/* are handled by the BES at server2.test.org
 +
#* http://localhost:8080/opendap/salinity/* are handled by the BES at server3.test.org
 +
#* The BES at server0.test.org would handle everything else.
  
  Example:
+
=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:
 +
 
 +
<pre>
 +
    <Handler className="opendap.bes.BESManager">
 +
 
 +
        <BES>
 +
            <prefix>/</prefix>
 +
            <host>server0.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
    </Handler>
 +
</pre>
 +
 
 +
And the top level directory for the ''root'' BES looks like this:
 +
 
 +
[[Image:topDir.png|Top Level Directory]]
 +
 
 +
If you add another BES, like this:
 +
<pre>
 +
    <Handler className="opendap.bes.BESManager">
 +
 
 +
        <BES>
 +
            <prefix>/</prefix>
 +
            <host>server0.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
        <BES>
 +
            <prefix>/sst</prefix>
 +
            <host>server5.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
    </Handler>
 +
</pre>
 +
'''It will not appear in the top level directory unless you create a ''mount point''.''' This simply means that on the file system 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:
 +
 
 +
[[Image:topDir2.png|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:
 +
<pre>
 +
    <Handler className="opendap.bes.BESManager">
 +
 
 +
        <BES>
 +
            <prefix>/</prefix>
 +
            <host>server0.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
        <BES>
 +
            <prefix>/GlobalTemperature </prefix>
 +
            <host>server1.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
        <BES>
 +
            <prefix>/GlobalTemperature/NorthAmerica</prefix>
 +
            <host>server2.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
        <BES>
 +
            <prefix>/GlobalTemperature/NorthAmerica/Canada </prefix>
 +
            <host>server3.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
        <BES>
 +
            <prefix>/GlobalTemperature/NorthAmerica/USA </prefix>
 +
            <host>server4.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
        <BES>
 +
            <prefix>/GlobalTemperature/Europe/France </prefix>
 +
            <host>server4.test.org</host>
 +
            <port>10022</port>
 +
            <ClientPool maximum="10" />
 +
        </BES>
 +
       
 +
    </Handler>
 +
</pre>
 +
 
 +
*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.
 +
 
 +
=Complete olfs.xml with multiple BES installations example=
 +
 
 +
 
 +
<pre>
 +
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
 +
&lt;OLFSConfig&gt;
 +
 
 +
    &lt;DispatchHandlers&gt;
 +
 
 +
        &lt;HttpGetHandlers&gt;
 +
 
 +
            &lt;Handler className="opendap.bes.BESManager"&gt;
 +
 
 +
                &lt;BES&gt;
 +
                    &lt;prefix&gt;/&lt;/prefix&gt;
 +
                    &lt;host&gt;server0.test.org&lt;/host&gt;
 +
                    &lt;port&gt;10022&lt;/port&gt;
 +
                    &lt;ClientPool maximum="10" /&gt;
 +
                &lt;/BES&gt;
 +
               
 +
                &lt;BES&gt;
 +
                    &lt;prefix&gt;/GlobalTemperature &lt;/prefix&gt;
 +
                    &lt;host&gt;server1.test.org&lt;/host&gt;
 +
                    &lt;port&gt;10022&lt;/port&gt;
 +
                    &lt;ClientPool maximum="10" /&gt;
 +
                &lt;/BES&gt;
 +
               
 +
                &lt;BES&gt;
 +
                    &lt;prefix&gt;/GlobalTemperature/NorthAmerica&lt;/prefix&gt;
 +
                    &lt;host&gt;server2.test.org&lt;/host&gt;
 +
                    &lt;port&gt;10022&lt;/port&gt;
 +
                    &lt;ClientPool maximum="10" /&gt;
 +
                &lt;/BES&gt;
 +
               
 +
                &lt;BES&gt;
 +
                    &lt;prefix&gt;/GlobalTemperature/NorthAmerica/Canada &lt;/prefix&gt;
 +
                    &lt;host&gt;server3.test.org&lt;/host&gt;
 +
                    &lt;port&gt;10022&lt;/port&gt;
 +
                    &lt;ClientPool maximum="10" /&gt;
 +
                &lt;/BES&gt;
 +
               
 +
                &lt;BES&gt;
 +
                    &lt;prefix&gt;/GlobalTemperature/NorthAmerica/USA &lt;/prefix&gt;
 +
                    &lt;host&gt;server4.test.org&lt;/host&gt;
 +
                    &lt;port&gt;10022&lt;/port&gt;
 +
                    &lt;ClientPool maximum="10" /&gt;
 +
                &lt;/BES&gt;
 +
               
 +
                &lt;BES&gt;
 +
                    &lt;prefix&gt;/GlobalTemperature/Europe/France &lt;/prefix&gt;
 +
                    &lt;host&gt;server4.test.org&lt;/host&gt;
 +
                    &lt;port&gt;10022&lt;/port&gt;
 +
                    &lt;ClientPool maximum="10" /&gt;
 +
                &lt;/BES&gt;
 +
 
 +
            &lt;/Handler&gt;
 +
 
 +
            &lt;Handler className="opendap.coreServlet.SpecialRequestDispatchHandler" /&gt;
 +
           
 +
            &lt;Handler className="opendap.bes.VersionDispatchHandler" /&gt;
 +
 
 +
            &lt;Handler className="opendap.bes.DirectoryDispatchHandler"&gt;
 +
                &lt;DefaultDirectoryView&gt;OPeNDAP&lt;/DefaultDirectoryView&gt;
 +
            &lt;/Handler&gt;
 +
 
 +
            &lt;Handler className="opendap.bes.DapDispatchHandler" /&gt;
 +
 
 +
            &lt;Handler className="opendap.bes.FileDispatchHandler" &gt;
 +
                &lt;!-- &lt;AllowDirectDataSourceAccess /&gt; --&gt;
 +
            &lt;/Handler&gt;
 +
 
 +
            &lt;Handler className="opendap.bes.ThreddsDispatchHandler" /&gt;
 +
 
 +
        &lt;/HttpGetHandlers&gt;
 +
 
 +
        &lt;HttpPostHandlers&gt;
 +
            &lt;Handler className="opendap.coreServlet.SOAPRequestDispatcher" &gt;
 +
                &lt;OpendapSoapDispatchHandler&gt;opendap.bes.SoapDispatchHandler&lt;/OpendapSoapDispatchHandler&gt;
 +
            &lt;/Handler&gt;
 +
        &lt;/HttpPostHandlers&gt;
 +
 
 +
    &lt;/DispatchHandlers&gt;
 +
 
 +
&lt;/OLFSConfig&gt;
 +
 
 +
</pre>

Latest revision as of 20:45, 19 December 2013

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). The prefix is a URL token between the server address/port and catalog root used to designate a particular BES instance in the case that multiple Back-End-Servers are available to a single OLFS. The default (for a single BES) is no additional tag, designated by "/". The prefix is used to provide a mapping for each BES connected to the OLFS to URI space serviced by the OLFS.

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>10022</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>10022</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/sst</prefix>
            <host>comet.test.org</host>
            <port>10022</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 as 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 pattern to add more BES's to the configuration. This next example shows a configuration with 4 BES's: The root BES, and 3 others:

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

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

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

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

    </Handler>

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:

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

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

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

Top Level Directory

If you add another BES, like this:

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

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

It will not appear in the top level directory unless you create a mount point. This simply means that on the file system 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:

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

        <BES>
            <prefix>/</prefix>
            <host>server0.test.org</host>
            <port>10022</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature </prefix>
            <host>server1.test.org</host>
            <port>10022</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica</prefix>
            <host>server2.test.org</host>
            <port>10022</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica/Canada </prefix>
            <host>server3.test.org</host>
            <port>10022</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/NorthAmerica/USA </prefix>
            <host>server4.test.org</host>
            <port>10022</port>
            <ClientPool maximum="10" />
        </BES>
        
        <BES>
            <prefix>/GlobalTemperature/Europe/France </prefix>
            <host>server4.test.org</host>
            <port>10022</port>
            <ClientPool maximum="10" />
        </BES>
        
    </Handler>
  • 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

<?xml version="1.0" encoding="UTF-8"?>
<OLFSConfig>

    <DispatchHandlers>

        <HttpGetHandlers>

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

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

            </Handler>

            <Handler className="opendap.coreServlet.SpecialRequestDispatchHandler" />
            
            <Handler className="opendap.bes.VersionDispatchHandler" />

            <Handler className="opendap.bes.DirectoryDispatchHandler">
                <DefaultDirectoryView>OPeNDAP</DefaultDirectoryView>
            </Handler>

            <Handler className="opendap.bes.DapDispatchHandler" />

            <Handler className="opendap.bes.FileDispatchHandler" >
                <!-- <AllowDirectDataSourceAccess /> -->
            </Handler>

            <Handler className="opendap.bes.ThreddsDispatchHandler" />

        </HttpGetHandlers>

        <HttpPostHandlers>
            <Handler className="opendap.coreServlet.SOAPRequestDispatcher" >
                <OpendapSoapDispatchHandler>opendap.bes.SoapDispatchHandler</OpendapSoapDispatchHandler>
            </Handler>
        </HttpPostHandlers>

    </DispatchHandlers>

</OLFSConfig>