Upgrading To TDS 4.2java.util.prefs warnings in the catalina.out logServer information can now be provided in the threddsConfig.xml
file (more details here):
<serverInformation>
<name>Initial TDS Installation</name>
<logoUrl>threddsIcon.gif</logoUrl>
<logoAltText>Initial TDS Installation</logoAltText>
<abstract>Scientific Data</abstract>
<keywords>meteorology, atmosphere, climate, ocean, earth science</keywords>
<contact>
<name>Support</name>
<organization>My Group</organization>
<email>support@my.group</email>
<!--phone></phone-->
</contact>
<hostInstitution>
<name>My Group</name>
<webSite>http://www.my.site/</webSite>
<logoUrl>myGroup.gif</logoUrl>
<logoAltText>My Group</logoAltText>
</hostInstitution>
</serverInformation>
This includes some basic descriptive information about the server; a name, logo, and web site URL for the hosting institution; and contact information.
NOTE: Some of this information was
previously (TDS 4.0 and 4.1) provided in the htmlSetup section. Use of the htmlSetup
section for that information is now deprecated (though still supported, for now).
The TDS distribution now includes the ncISO package from NOAA/NGDC (many thanks to Dave Neufeld and Ted Habermann).
For details on enabling the ncISO services and applying them to datasets, see the TDS ncISO page.
The OGCMeta.xml file has been replaced by some of the informatino in the serverInfo
element in the threddsConfig.xml file.
The following shows all the configuration options available in the WMS section of the
threddsConfig.xml file with the default values shown (more details
here):
<WMS> <allow>false</allow> <allowRemote>false</allowRemote> <paletteLocationDir>/WEB-INF/palettes</paletteLocationDir> <maxImageWidth>2048</maxImageWidth> <maxImageHeight>2048</maxImageHeight> </WMS>
We recommend that you include in the threddsConfig.xml
file only the options you want to change. As a first pass, we recommend the following:
<WMS> <allow>false</allow> </WMS>
The WMS service now uses a new configuration file for a number of more detailed
WMS configuration options, mainly focused on the styling of WMS images. Similar
to the threddsConfig.xml file, the WMS configuration file
(wmsConfig.xml) is found in the
${TOMCAT_HOME}/content/thredds directory. A detailed description
of the wmsConfig.xml file can be found at the MyOcean
"Detailed WMS Configuration" page.
If you are installing a new TDS, you should find a default wmsConfig.xml file (along
with other configuration files) in your content/thredds directory after you first
deploy the TDS. If you are upgrading from a TDS version before version 4.2.20100615.*,
you will have to copy the default file from
TOMCAT_HOME/webapps/thredds/WEB-INF/altContent/startup/wmsConfig.xml.
The number of CRS listed in the WMS GetCapabilities documents has been reduced between TDS 4.1 and 4.2. More information is available at this FAQ entry.
The datasetFmrc element has been deprecated in favor of the new
featureCollection element. Details on using the
featureCollection element and converting datasetFmrc
elements to featureCollection elements can be found
here.
java.util.prefs warnings in the catalina.out logThis is only an issue if you have enabled WMS and those services are being accessed.
You can avoid getting java.util.prefs warning in your catalina.out log file by
following the configuration steps given in the TDS FAQ on this issue.
This document is maintained by Unidata and was
last updated May, 2010. Send comments to THREDDS
support.