The Top Level
| File | Content |
|---|---|
| bin | Some utilities for LAS administration tasks, like adding data sets, testing the server and more. |
| build.xml.in | The input template for the ant build file. |
| compiler.jar | We use this utility to compress some of our JavaScript into smaller obfuscated code. |
| compile_V7UI.sh | A convenience script for compiling the JavaScript. |
| conf | This directory contains the example configuration files. |
| configure | The shell script used to configure LAS. It just finds Perl and starts the perl configure script. |
| configure.pl | The Perl configure script where all the hard work is done. |
| data | Example in-situ data. |
| GWT-compile | A convenience script for compiling our GWT code into JavaScript. |
| JavaSource | The Java source code for LAS. |
| Makefile | A make file.
|
| overview.html | JavaDoc overview. |
| refresh.sh | Copy static Web content to the running server. Edit it for your site. |
| WebContent | The static web content, servlet configuration and output templates |
The conf/ Directory
| File or directory | What it contains |
|---|---|
| example/ | This contains the raw materials for the configuration of the LAS. The files in this directory get processed and copied to the server/ directory. |
| $TOMCAT_HOME/content/las/conf/server | After the files in conf/exmaple are processed the results are placed in $TOMCAT_HOME/content/las/conf/server. You will add your data sets and other configuration information for your server into this directory for your running LAS. |
The JavaSource Directory
| File or directory | What it contains |
|---|---|
| JavaSource/resources/ferret | The resources used by the Ferret backend. If you interesting in writing your own Ferret operation scripts or modifying the existing scripts this is where you'll need to look. JavaSource/resources/ferret/FerretBackendConfig.xml contains an XML description of the Ferret environment that is used by Ferret as it runs. It also configures the size of the cache. The contents is mostly a sequence of FER environment variables and their values. This file gets created by the configure.pl script and gets its initial values from the environment of the parent shell that is running the configure.pl. If you edit this file and run configure again, it will the configure process will ask you if you want to keep it. make clean removes this file. The JavaScript/resources/ferret/script directory contains Ferret product scripts and any supporting scripts used by the product scripts. This directory gets referenced in the FerretBackendConfig.xml file in which the entire environment under which Ferret runs is defined. Ferret is then responsible for resolving the actual script names since this is just another directory in the FER_GO environment. The scripts used by Ferret in the LAS can actually appear anywhere in the FER_GO search path, but this is a particular directory reserved for scripts associated with LAS. |
| JavaSource/resources/database | The resources used by the database backend. This is where you find the files you need to configure for accessing in-situ data stored in an RDMS. |
| JavaSource/resources/log4j.xml | This is the file that is used to configure the logging levels in LAS. If you are having trouble change the level value="INFO" to value="DEBUG" and then you send the output to the mailing list for help:
<logger name="gov.noaa.pmel.tmap" additivity="false"> |
The WebContent directory
| File or directory | What it contains |
|---|---|
| WebContents/WEB-INF/struts-config.xml | The struts configuration file which points to other configuration files used by LAS.
The WebContent/WEB-INF/struts-config.xml is the top level configuration file for LAS. Inside this file you reference the four files that control the LAS Product Server: the las.xml file, the ui.xml file, the operationsV7.xml file and the productserver.xml file. Typically these three files are in the conf/server directory as described above. The las.xml is what it's always been (datasets, variables, grids, axes and categories). The operationsV7.xml file contains the new operations definitions for the Java product server. The productserver.xml file defines the names and URLs of the backend services available to this LAS. These services are associated with operations using the <service> element in the operations definition. |