Metacat

  <p> 

  <a name="buildProperties" />

  <h2>Edit <code>build.properties</code> File</h2>

  </p>

   your system. The property values that you will likely need to change are described in 

   detail in the following table:

  <br/>

      <td>The tomcatversion property is the version of Tomcat in which you 

          jar files coming with Tomcat. 

          <p>

            <em>Note: Tomcat 3 and 4 are no longer tested or supported by Metacat.

                Users are highly encouraged to upgrade to Tomcat 5.5.

            </em>

          </p>

          <p>

            <em>Also note: a property value of 'tomcat5' can be set when using

                either Tomcat 5.0 or Tomcat 5.5.

            </em>

          </p>

      </td>

      <br><br>Other possible values (deprecated):&nbsp;&nbsp;

          <code>tomcat3 tomcat4</code>

      </td>

          <p>

          The build file is preconfigured to install Metacat either using 

          Oracle, PostgreSQL, or Microsoft SQL Server as a backend database.  

          To change the database system, simply change the value of the 'database' 

          property to be the name of the database target that you wish to use.

          </p>

          <p>

          </p>

          <code>jdbc:postgresql://localhost/metacat</code>

      <td>Default: <code>authority</code></td>

      <td><p>Default: <code>ecoinformatics.org</code></p>

        <p>Examples: <code>esa.org</code> or <code>sulphur.ecoinformatics.org</code></p></td>

    <tr>

      <td>install.ecogrid</td>

      <td>Enables EarthGrid web services. EarthGrid web services are disabled by default. 

          To enable EarthGrid web services (including query, put, authentication and 

          identifier interface), set this value to <code>true</code>, and also set the value

          of the <em>metacat.dir</em> property as detailed below.</td>

      <td>

          Default:&nbsp;&nbsp;<code>false</code>

      </td>

    </tr>

    <tr>

      <td>metacat.dir</td>

      <td>If the <em>install.ecogrid</em> property (see above) is set to <code>true</code>, this

          property should be set to the absolute path of the top-level metacat directory.

          If <em>install.ecogrid</em> is set to <code>false</code> (the default setting), 

          the value of <em>metacat.dir</em> is ignored.          

      </td>

      <td>Default:&nbsp;&nbsp;<code>/home/tao/project/metacat</code></td>

    </tr>

  Other properties in <code>build.properties</code> that you can (but generally need not) change:

      <td>Default:&nbsp;&nbsp;<code>${config.hostname}:${config.port.https}</code></td>

      <td>http.protocol</td>

      <td>http.protocol is the string used in the leading part of a URL to indicate use of the HTTP protocol.</td>

      <td>Default:&nbsp;&nbsp;<code>http</code>

      </td>

    </tr>

    <tr>

      <td>config.metacatserver</td>

      <td>The URL to the metacat server, composed in part from three other properties (http.protocol, httpserver, and metacat.context).</td>

      <td>Default:&nbsp;&nbsp;<code>${http.protocol}://${httpserver}/${metacat.context}/metacat</code>

      </td>

    </tr>

    <tr>

      <td>The URL used for executing CGI scripts</td>

    <tr>

      <td>log.dir</td>

      <td>The directory where replication log files are to be written by Metacat.</td>

      <td>Default:&nbsp;&nbsp;<code>${tomcat}/logs</code></td>

    </tr>

    <tr>

      <td>moderators</td>

      <td>Moderator accounts, in a colon-separated list. Specifies a list of special users who can review a general user's submission. 

             Moderators can approve, revise and reject the submission after reviewing. This property is only used in the ESA skin.</td>

      <td>Default:&nbsp;&nbsp;<code>cn=knb-prod,o=NCEAS,dc=ecoinformatics,dc=org</code></td>

    </tr>

    <tr>

      <td>allowedSubmitters</td>

      <td>Specifies the list of users who should be allowed to submit documents. 

          If no value is specified (the default setting), all users will be allowed to submit documents.

      </td>

      <td>Default:&nbsp;&nbsp;(no value)</td>

    </tr>

    <tr>

      <td>deniedSubmitters</td>

      <td>Specify the list of users who should not be allowed to submit documents. 

          If no value is specified (the default setting), all users will be allowed to submit documents.</td>

      <td>Default:&nbsp;&nbsp;(no value)</td>

    </tr>

    <tr>

      <td>config.metadataLabelLsid</td>

      <td> </td>

      <td>Default:&nbsp;&nbsp;<code>${config.lsidauthority}</code></td>

    </tr>

    <tr>

      <td>build.dir</td>

      <td>The name of the subdirectory that is created when metacat is built by the 'ant' tool.</td>

      <td>Default:&nbsp;&nbsp;<code>build</code></td>

    </tr>

    <tr>

      <td>lsid.build.dir</td>

      <td>The name of the subdirectory for building the LSID component of metacat.</td>

      <td>Default:&nbsp;&nbsp;<code>${build.dir}/lsid</code></td>

    </tr>

    <tr>

      <td>lib.dir</td>

      <td>The name of the subdirectory where library (.jar) files and a number of other important files are located.</td>

      <td>Default:&nbsp;&nbsp;<code>lib</code></td>

    </tr>

    <tr>

      <td>lsid.lib.dir</td>

      <td>The name of the subdirectory where LSID library (.jar) files are located.</td>

      <td>Default:&nbsp;&nbsp;<code>${lib.dir}/lsid_lib</code></td>

    </tr>

    <tr>

      <td>lsid.classes.dir</td>

      <td>The relative path to the location of Java classes that support LSID.</td>

      <td>Default:&nbsp;&nbsp;<code>edu/ucsb/nceas/metacat/lsid</code></td>

    </tr>

    <tr>

      <td>conf.dir</td>

      <td>The name of the directory where LSID configuration files are located.</td>

      <td>Default:&nbsp;&nbsp;<code>lib/lsid_conf</code></td>

    </tr>

    <tr>

      <td>services.dir</td>

      <td>The name of the directory where LSID services configuration files are located.</td>

      <td>Default:&nbsp;&nbsp;<code>${conf.dir}/services</code></td>

    </tr>

    <tr>

      <td>webinf.dir</td>

      <td>The name of the directory where additional LSID web services files are located.</td>

      <td>Default:&nbsp;&nbsp;<code>${conf.dir}/WEB-INF</code></td>

    </tr>

    <tr>

      <td>compile.debug</td>

      <td>Indicates whether Java source should be compiled with debug information.</td>

      <td>Default:&nbsp;&nbsp;<code>true</code></td>

    </tr>

    <tr>

      <td>compile.deprecation</td>

      <td>Indicates whether Java source should be compiled with deprecation information.</td>

      <td>Default:&nbsp;&nbsp;<code>false</code></td>

    </tr>

    <tr>

      <td>compile.optimize</td>

      <td>Indicates whether Java source should be compiled with optimization.</td>

      <td>Default:&nbsp;&nbsp;<code>true</code></td>

    </tr>

    <tr>

      <td>indexPaths</td>

      <td>The <em>indexPaths</em> property specifies a comma-separated (potentially long) list 

          of indexed paths that can be utilized to improve the

          performance of metacat queries. Each component of the <em>indexPaths</em> property

          should specify an absolute or relative path (using an XPath-like syntax) to an XML element or 

          attribute present in the XML documents being queried. Metacat stores XML 

          element and attribute values for indexed paths in a special database table 

          that optimizes search performance.

          <p>Metacat queries allow you to specify (using the &lt;pathexpr&gt; tag in search query) 

          an exact path to which you want

          to restrict the search. When the <pathexpr> path that is specified in the query

          is a member of the <em>indexPaths</em> list, search results are returned faster 

          because metacat can conduct its search using the optimized database table.

          <p>

          The default value for the <em>indexPaths</em> property contains numerous paths to EML

          elements and attributes that are commonly queried by metacat search tools. 

          For example, <em>keyword</em> is a

          member of this list because it is common for search tools to query

          the <em>keyword</em> field in EML documents. For most purposes, the default value will

          optimize various types of searches on EML documents and need not be changed.

          <p>

          For more information about metacat queries, 

          see <a href="./metacatquery.html">Queries and Results</a>.

      </td>

      <td>Default:&nbsp;&nbsp;<code>organizationName,originator/individualName/surName,...</code></td>

    </tr>