• At its heart, the IDV is configured by one or more properties files and a set of other resource files. By default the IDV looks in 3 different places:
  • System resource path - in the java jar files.
  • Site path - defined at the command line or through user preferences.
  • User path - e.g., /home/idv/.unidata/idv/DefaultIdv
• The property files define:
  • The application name.
  • What remote data servers are available.
  • What data catalogs to use.
  • Where to find the resource description files.
  • Etc.
• The workshop is using an idv.properties file that contains:

idv.title = Unidata Workshop IDV

##Semicolon delimited list of urls pointing to thredds catalogs
idv.cataloglist= /ucar/unidata/apps/workshop/workshopCatalog.xml;https://www.unidata.ucar.edu/georesources/idvcatalog.xml

## default projection
idv.projection.default=World

• We are configuring the list of ADDE servers and their image and radar descriptors, and the workshopCatalog file for the gridded data chooser.
• The default start up process is as follows:
  • Process the default system property file.
  • Process any command line properties files.
  • Look in the properties loaded so far to get and process a list of other property files. These are:
    • <Site path>/idv.properties
    • <User path>/idv.properties
  • Look for the idv.resourcefiles property. This defines where to find the resource description files. e.g.:

    %USERPATH%/idv.rbi;%SITEPATH%/idv.rbi;%IDVPATH%/idv.rbi

  • Load in plugins (more on this later).
• Now we'll look at how the IDV finds the resources using the rbi files.

Unidata IDV Workshop for version 6.0 > Advanced Topics > Configuring IDV Sites