On 12/10/2010 11:37 AM, John Relph wrote:
On 12/10/2010 10:31 AM, Roland Schweitzer wrote:Hi John, Details below... On 12/10/2010 07:19 AM, John Relph wrote:On 12/09/2010 12:24 PM, Roland Schweitzer wrote:On 12/09/2010 10:43 AM, John Relph wrote:$TOMCAT_HOME/webapps/las/WEB-INF/classes/resources/ferret/FerretBackendConfig.xmlRoland Schweitzer wrote:Where is the name of that directory recorded in the configuration? That is, in which configuration files would I find the name of that directoryJohn, The test that is failing is access to the F-TDS version of the dataURL for the data sets installed with LAS. When LAS starts is createsa small journal file in the directory you chose in the configurationstep which sets up access to that data set via F-TDS. When I click on the LAS OPeNDAP link (http://data.nodc.noaa.gov/thredds/dodsC/las/) Isee the default data sets instead of those that are configured into your LAS.so that I can verify that the configuration is correct?There are actually three directories that are used for LAS and F-TDS to communicate and they are attributes on the <invoker> element:<invoker base_dir="resources/ferret"executable="/home/porter/tmap/ferret/x86_64-linux/bin/ferret"time_limit="3600" template_dir="templates"output_dir="/home/porter/rhs/tomcat/webapps/las/output" http_base_url = "http://porter.pmel.noaa.gov:8920/las/output"iosp_script_dir="resources/iosp/scripts" *iosp_temp_dir="/home/porter/rhs/tomcat/content/las/conf/server/temp"iosp_data_dir="/home/porter/rhs/tomcat/content/las/conf/server/data/dynamic" las_tfds_data_dir="/home/porter/rhs/tomcat/content/las/conf/server/data"*iosp_base_dir="resources/iosp"opendap_base_url = "http://porter.pmel.noaa.gov:8920/thredds/dodsC/output"/>Roland,I did find an error in the TDS catalog.xml which I have correct, so that the "Data from LAS" entry is now pointing to the correct directory. However, F-TDS still does not work.So, more questions.First, I'm looking at the value for "http_base_url". When I visit that URL at our site (http_base_url = "http://data.nodc.noaa.gov/las/output") I get an error. Is that URL used as a base for a longer URL? How can I test it?Yes, it's the base of all the product URLs. You are not likely to have permission to view http://data.nodc.noaa.gov/las/output. You will have to look at an individual image in that directory. Seems to work. I did a plot and it loaded the image. http://data.nodc.noaa.gov/las/output/96C61F1A6F5E8B6210888FEDA657A831_plot_image.gifSimilarly, the "opendap_base_url" is defined but when I attempt to access it using my browser, I get an error. How can I test if it's working correctly?This is a little tricky. The /output is a vestige we don't use any more. The URL you want can be found in the banner of the LAS page under the OPeNDAP link (http://data.nodc.noaa.gov/thredds/dodsC/las/).This all appears to be working just fine until I try to click on an actual F-TDS dataset:http://data.nodc.noaa.gov/thredds/dodsC/las/id-fd80f65d91/catalog.htmlhttp://data.nodc.noaa.gov/thredds/dodsC/las/id-fd80f65d91/catalog.html?dataset=las/id-fd80f65d91/data_data.nodc.noaa.gov_thredds_dodsC_pathfinder_testdata_crw_oa_data_aggregations_yearly_aggregate_2005.ncml.jnl http://data.nodc.noaa.gov/thredds/dodsC/las/id-fd80f65d91/data_data.nodc.noaa.gov_thredds_dodsC_pathfinder_testdata_crw_oa_data_aggregations_yearly_aggregate_2005.ncml.jnl.htmlThen I get an IO Exception from the Ferret IOSP code: Error { code = 500;message = "java.lang.Exception: Ferret config file resources/iosp/FerretConfig.xml not found.";};This tells me that the Java classes are deployed in the right place in the TDS and that the IOSP is plugged into the threddsConfig.xml correctly, but apparently some or all of the resources are missing.There is an 'deploy-iosp' target that just deploys the IOSP code and resources. You can refer to that in order to see what files go where.Alright, I found the target and used that to re-install the IOSP code and resources. The links you list above worked (but then I nuked them all).
Glad to hear it worked. Those links are required for LAS to do analysis and will get recreated when LAS starts. However, you can hide them from display in you TDS catalog by referencing them as a catalogRoot in threddsConfig.xml instead of a data set in catalog.xml.
For example make a catalog called las_catalog.xml in your content/thredds directory that looks something like this:
<catalog name="LAS Data Catalog"xmlns="http://www.unidata.ucar.edu/namespaces/thredds/InvCatalog/v1.0"
xmlns:xlink="http://www.w3.org/1999/xlink"> <service name="all" base="" serviceType="compound"> <service name="odap" serviceType="OpenDAP" base="/thredds/dodsC/" /> <service name="http" serviceType="HTTPServer" base="/thredds/fileServer/" /> </service><datasetScan name="Data From LAS" path="las" location="/home/porter/rhs/tomcat/content/las/conf/server/data" serviceName="all">
<filter> <include wildcard="*.nc"/> <include wildcard="*.fds"/> <include wildcard="*.jnl"/> </filter> </datasetScan> </catalog> and then reference it from threddsConfig.xml like this: <?xml version="1.0" encoding="UTF-8"?> <threddsConfig> [...] <catalogRoot>las.xml</catalogRoot> [...]
Question: does LAS make outgoing HTTP queries in order to complete its processing?
Any data set you have configured into your LAS that is being served by an OPeNDAP server that is not on your network will require and outgoing HTTP request to fetch the data. Other than that, no.
Roland
-- JohnRoland-- JohnI'm not sure why those files are not being written at start up, butperhaps there is a permission problem with the directory vis a vis theprocess that is running tomcat. F-TDS and LAS need to write in that directory to do their work. You can remove the default data setdirectories now that you have your own data configured, but you shouldsee new directories created when LAS starts.I don't see those directories at all. Of course, since I'm not sure where I'm looking, I don't know exactly what I'm looking for either.In my case, you see the directory is called: */home/porter/rhs/tomcat/content/las/conf/server/data*which looks like:[rhs@porter ferret]$ ls /home/porter/rhs/tomcat/content/las/conf/server/datacoads_climatology_cdf NOAA_NCEP_EMC_CMB_Ocean_Analysis_ml dynamic ocean_atlas_subset levitus_climatology_cdf NOAA_NCEP_EMC_CMB_Ocean_Analysis$TOMCAT_HOME/webapps/las/WEB-INF/classes/resources/ferret/FerretBackendConfig.xmlAnother possibility is that the FerretBackendConfig.xml file and theFerretConfig.xml file in F-TDS that are being used are pointing to thewrong directory for deployment on the public server.In which directories are those two configuration files expected to be found on a correctly configured system?(as mentioned above) and$TOMCAT_HOME/webapps/thredds/WEB-INF/classes/resources/iosp/FerretConfig.xmlIn most cases these files will be identical. Roland-- JohnRoland On 12/09/2010 09:32 AM, John Relph wrote:Folks, I'm having a problem with LAS 7.2 Beta 2 and F-TDS. LAS gives the following error when using the functions under "Apply analysis": ------- A component needed for your request is down or was not installed.If you are the site adminstrator, verify that your F-TDS installation isworking correctly, then restart your servlet container (Tomcat) or reinit your server from the admin page. -------The problem can be reproduced by following these steps, using the NODCLAS athttp://data.nodc.noaa.gov/las/ :1) Choose the World Ocean Atlas 09> 1 degree> nitrate> monthly>Nitrate dataset 2) Click on "Apply analysis" link at the bottom.3) Choose the "Average" Analysis type and the "Area" Analysis regiontype (though other choices result in the same error) 4) Click on "Update Plot". The error shows up in the graph area. Ferret is installed as part of LAS and TDS, as perhttp://ferret.pmel.noaa.gov/LAS/documentation/installer-documentation/installation/installing-and-integrating-tds-with-las/Have I missed something? -- John