For performance and space reasons, you may want some TDS directories on larger and higher performance disks than the directory where Tomcat is installed. For instance:
The easiest way to change the location of non-data directories is with symbolic links. For
instance, if Tomcat is installed on a smaller and/or lower performance disk (say
/data is a larger and higher performance disk, your
directory might look something like this:
-rw-r--r-- 1 tomcat tomcat 37950 Jul 19 07:01 LICENSE -rw-r--r-- 1 tomcat tomcat 557 Jul 19 07:01 NOTICE -rw-r--r-- 1 tomcat tomcat 8669 Jul 19 06:59 RELEASE-NOTES -rw-r--r-- 1 tomcat tomcat 6670 Jul 19 07:01 RUNNING.txt drwxr-xr-x 3 tomcat tomcat 1024 Oct 24 06:42 bin/ drwxr-xr-x 4 tomcat tomcat 512 Nov 1 18:14 conf/ lrwxrwxrwx 1 tomcat tomcat 30 Aug 17 18:15 content -> /data/tds/tdsA/content/ drwxr-xr-x 2 tomcat tomcat 512 Aug 9 15:02 lib/ lrwxrwxrwx 1 tomcat tomcat 27 Aug 17 18:16 logs -> /data/tds/tdsA/logs/ drwxr-xr-x 2 tomcat tomcat 512 Oct 22 12:04 temp/ drwxr-xr-x 7 tomcat tomcat 512 Nov 1 18:33 webapps/ drwxr-xr-x 3 tomcat tomcat 512 Aug 9 19:38 work/
the TDS will use or create (if they don't already exist) the configuration files in:
The location of your data directories is configured in your
configuration catalog(s). So, if your data is located in
/data/pub, you simply use the appropriate
/data/pub locations in your
various dataset configurations (
The various cache directories (
can be configured with the
dir child element of the various caching elements in the
threddsConfig.xml file. However, we recommend using a symbolic link to move
content/thredds instead (more detail here).
The TDS configuration directory is created and populated with default files the first time the TDS is deployed. It is persistent even when a TDS installation is upgraded or re-deployed. All modifications and additions to the TDS configuration should be made in this directory. Do not place files containing passwords or anything else with security issues in this directory. Typically you will only be adding and modifying catalogs and configuration files.
When there are many catalogs, you may want to keep them in seperate subdirectories of the TDS configuration directory. This is recommended practice. However, do not use a subdirectory content/thredds/catalog, as catalog is a reserved word in this context.
When the TDS is first deployed, the TDS configuration directory looks like:
catalog.xml- the main TDS configuration catalog (root catalog for TDS configuration)
enhancedCatalog.xml- an example catalog [Note: It is referenced from
threddsConfig.xml- configuration file for allowing non-default services, configuring caching, etc (more detailed information).
catalogInit.log- log file for messages generated while reading TDS configuration catalogs during TDS initialization and reinitialization.
threddsServlet.log- TDS error log file.
cache/- various cache directories