[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A few questions about THREDDS Data Server architecture

On 3/14/2010 5:36 PM, Seung Kim wrote:
Dear Mr. Caron,

I work for NOAA NESDIS CLASS Project.  We are planning to deploy THREDDS
Data Server initially at NCDC CLASS.
I was reading the PowerPoint document posted at

I have a few questions that you can answer right away..

In Slide 2 ("TDS is a data server), I see "catalog.xml" sent to remote user
and "configCatalog.xml" read by THREDDS Server. Is the "catalog.xml" file
one of THREDDS Dataset Inventory Catalogs? Would you please let me know
what "configCatalog.xml" is for? Could it have since been renamed

no, thats a different file. configCatalog.xml just means "server side configuration catalog files".

BTW, you should be looking at the 4.0 docs:


What entities shown in Slide 2 are parts of the TDS? Could they be all
shown in the white rectangle (i.e., HTTP Tomcat Server and the elements
inside this box, configCatalog.xml, and Datasets)? Or could they be just
"THREDDS Server plus catalog.xml and associated web services (i.e., HTTP
Server, OPeNDAP, WCS/WMS, NetcdfSubset, and RadarServer)?

on that slide, everything except for RemoteAccess aand IDD Data is part of the TDS.
I would like to ask your permission to copy and modify the figure (Slide 2)
and to use it in one of my documents.

yes, you are welcome to use anything on our site.

Thank you very much.

Seung T. Kim
Sr. Systems Engineer

7855 Walker Drive, Suite 200, Greenbelt, MD 20770
Civil Division|Phone: 240-542-1121|Fax: 301-474-4074|address@hidden|

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.