On 12/09/2010 12:34 PM, John Relph wrote:
Roland Schweitzer wrote:On 12/09/2010 10:43 AM, John Relph wrote:Roland Schweitzer wrote:John, The test that is failing is access to the F-TDS version of the data URL for the data sets installed with LAS. When LAS starts is creates a small journal file in the directory you chose in the configuration step 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/) I see the default data sets instead of those that are configured into your LAS.Where is the name of that directory recorded in the configuration? That is, in which configuration files would I find the name of that directory so that I can verify that the configuration is correct?$TOMCAT_HOME/webapps/las/WEB-INF/classes/resources/ferret/FerretBackendConfig.xml There are actually three directories that are used for LAS and F-TDS to communicate and they are attributes on the<invoker> element:Roland, Thank you for your help. I'm assuming that there are configuration values used during the configuration of LAS that correspond to these values below. Are those configuration values in "config7.results" in the LAS source directory? Where do those configuration values end up in the LAS webapp directory? Are they only found in the FerretBackendConfig.xml and FerretConfig.xml files? I guess I'm answering my own question: it appears that those directories must also appear in content/thredds/catalog.xml, content/las/conf/server/productserver.xml, etc., which are automatically generated by the ./configure process. But the values for those configuration items, that is, the names of the directories, are never specified by the user during the ./configure process. Is it possible to specify different directories? Perhaps by a command-line option to ./configure?
We used to ask in the configure process where to place those directories. When we started working toward building a war file that could be relocated to any server, it seemed to make sense to just put them in the $TOMCAT_HOME/content directory. We may have to rethink that based on the fact that folks might want point to some large scratch area that's not backed up for example.
You can, as you have discovered, find all the references and change them by hand or you could pull an old configure7.pl out of an old tar file resurrect that logic. If it's critical to you I'll send you one that will ask where to place those directories.
How large can the contents of those directories become?
The contents could potentially get large. On the other hand you can clean out the directory with complete impunity. Or pretty close to complete impunity. If the system is looking for a file there and doesn't find it, it will recreate it.
Roland
-- John<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"/>I'm not sure why those files are not being written at start up, but perhaps there is a permission problem with the directory vis a vis the process that is running tomcat. F-TDS and LAS need to write in that directory to do their work. You can remove the default data set directories now that you have your own data configured, but you should see 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/data coads_climatology_cdf NOAA_NCEP_EMC_CMB_Ocean_Analysis_ml dynamic ocean_atlas_subset levitus_climatology_cdf NOAA_NCEP_EMC_CMB_Ocean_AnalysisAnother possibility is that the FerretBackendConfig.xml file and the FerretConfig.xml file in F-TDS that are being used are pointing to the wrong directory for deployment on the public server.In which directories are those two configuration files expected to be found on a correctly configured system?$TOMCAT_HOME/webapps/las/WEB-INF/classes/resources/ferret/FerretBackendConfig.xml (as mentioned above) and $TOMCAT_HOME/webapps/thredds/WEB-INF/classes/resources/iosp/FerretConfig.xml In 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 is working 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 NODC LAS at http://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 region type (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 per http://ferret.pmel.noaa.gov/LAS/documentation/installer-documentation/installation/installing-and-integrating-tds-with-las/ Have I missed something? -- John