TDS Configuration Directory

Most TDS configuration information is stored in the TDS configuration directory. The default location for the TDS configuration directory is

${tomcat_home}/content/thredds

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.

Content of Configuration Directory

When the TDS is first deployed, the TDS configuration directory looks like:

• ${tomcat_home}/content/thredds/
  • catalog.xml - the main TDS configuration catalog (root catalog for TDS configuration)
  • enhancedCatalog.xml - an example catalog [Note: It is referenced from catalog.xml.]
  • threddsConfig.xml - configuration file for allowing non-default services, configuring caching, etc (more detailed information).
  • logs/
    • 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
    • agg/
    • cdm/
    • collection/
    • ehcache/
    • ncss/
    • wcs/

Changing the Location of the Configuration Directory

There are two ways to change the location of the TDS Configuration Directory:

• The easiest way to change the location of the TDS configuration directory is by creating ${tomcat_home}/content as a symbolic link to the desired location.

• If you can't use a symbolic link, the other option is to set the "tds.content.root.path" Java system property. For instance, by adding the following to JAVA_OPTS in your startup script:

  -Dtds.content.root.path=/some/absolute/path

  the TDS will use or create (if they don't already exist) the configuration files in:

  /some/absolute/path/thredds

Note: If you are planning on running more than one TDS on a single Tomcat instance, please be sure to read the "Running Multiple TDS in one Tomcat Container" page and especially the section on " Web Application Containers and Java System Properties". Rather than setting the "tds.content.root.path" property with a "-D..." Java option as discussed above, you will need to edit the TDS default properties file:

${tomcat_home}/webapps/thredds2/WEB-INF/classes/thredds/server/tds.properties

and change the value of "tds.content.root.path" there.

This document is maintained by Unidata and was last updated July 2011. Send comments to THREDDS support.