Metacat

   installation).  These instructions assume a Linux environment but may

  <p>You'll need a recent Java SDK; J2SE 1.4.2 or later is required.  The latest metacat release

  has been tested most extensively with <a href="http://java.sun.com/j2se/1.5.0/">J2SE 5.0</a>

  and this is the recommended version.

    We recommend that you install Tomcat version 5.5.  More details about 

    Tomcat installation are available <a href=" http://jakarta.apache.org/tomcat/index.html">here</a>.

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

  <p>

  The properties that you will likely need to change will include:

  <ul>

  <li><code>tomcat</code></li>

  <li><code>deploy.dir</code></li>

  <li><code>metacat.context</code></li> 

  <li><code>config.hostname</code></li>

  <li><code>config.port</code></li>

  <li><code>config.port.https</code></li>

  <li><code>ldapUrl</code></li>

  <li><code>database</code></li>

  <li><code>jdbc-connect</code></li>

  <li><code>jdbc-base</code></li>

  <li><code>user</code></li>

  <li><code>password</code></li>

  <li><code>datafilepath</code></li>

  <li><code>inlinedatafilepath</code></li>

  <li><code>default-style</code></li>

  <li><code>administrators</code></li>

  <li><code>authority.context</code></li>

  <li><code>config.lsidauthority</code></li>

  </ul>

  Each is described in detail in the following table:

          <code>C:/Tomcat-5.5</code></td>

      <td>deploy.dir</td>

      <td>The deploy.dir property is the location in which your tomcat servlet 

          contexts are deployed. This is typically "${tomcat}/webapps",

          where ${tomcat} is the same value that you entered for the 'tomcat'

          <code>C:/Tomcat-5.5/webapps</code>

      <td>metacat.context</td>

      <td>The metacat.context property is the name of the servlet context in which you 

      <td>config.hostname</td>

      <td>The config.hostname property is the hostname of the server on which Metacat is 

          property).

         <code>somehost.university.edu</code>

      <td>config.port</td>

      <td>The config.port property is the HTTP plain port number that is used to connect to Metacat.

          If Tomcat is running stand-alone, the value will typically be 8080.</td>

          <code>80</code>

          <code>8080</code>

      <td>config.port.https</td>

      <td>The config.port.https property is the HTTP secure port number that is used to connect to Metacat.

          If Tomcat is running stand-alone, the value will typically be 8443.</td>

      <td>Default:&nbsp;&nbsp;

          <code>80</code>

      <br><br>Example:&nbsp;&nbsp;

          <code>8443</code>

      </td>

    </tr>

    <tr>

          <code>sqlserver</code>. <em>Note that sqlserver support is minimal and

          possibly including code changes.  We have not recently tested on 

          sqlserver.</em>

          <code>postgresql</code>

          <code>oracle</code>&nbsp;&nbsp;

          <code>jdbc-connect=jdbc:postgresql://localhost/metacat</code>

      <br><br>Example:&nbsp;&nbsp;

          <code>jdbc:oracle:thin:@somehost.university.edu:1521:metacat</code>

      <td>The base directory for locating JDBC jar files. When using the postgresql database, the default setting of './lib' can be used,

          while oracle and sqlserver databases will require a different setting since these jar files are not included in the Metacat

          distribution.</td>

          <code>./lib</code>

          <code>/usr/oracle/jdbc/lib</code><br>

      <td>The database user name that you set up to use Metacat.</td>

          <code>metacat</code>

          <code>metacatuser</code>

          <code>C:/Tomcat-5.5/data/metacat/data</code>

          <code>C:/Tomcat-5.5/data/metacat/inlinedata</code>

          during a query. It is set to "default", which is one of the styles that 

          <code>default</code>

      <br><br>Examples:<code>esa kepler knb knb2 knp lter ltss nceas nrs obfs pisco specnet</code>

          documents. The list can contain more than one account separated

          <code>http://${httpserver}/cgi-bin</code>

      <td>cvsroot</td>

      <td>CVS access to retrieve latest EML. Only used by

          developers in building the release.</td>

      <td>Default:&nbsp;&nbsp;

          <code><pre>:ext:${env.USER}@cvs.ecoinformatics.org:/cvs</pre></code>

          Example:  

          <code><pre>:ext:myaccount@cvs.ecoinformatics.org:/cvs</pre></code>

      </td>

    </tr>

    <tr>

      <td>timedreplication</td>

      <td>Determines whether timed replication to other metacat servers is being used.</td>

      <td>Default:&nbsp;&nbsp;

          <code>false</code>

      <br><br>Other possible values:&nbsp;&nbsp;

          <code>true</code>

      </td>

    </tr>

    <tr>

      <td>firsttimedreplication</td>

      <td>The time for starting first timed replication if timedreplication is true.

          (See comments in build.properties file for additional details.)</td>

      <td>Default:&nbsp;&nbsp;

          <code>10:00 PM</code>

          <code>&nbsp;</code>

      </td>

    </tr>

    <tr>

      <td>timedreplicationinterval</td>

      <td>The interval to next timed replication if timedreplication is true.

          The value is in milliseconds and default value is 48 hours.</td>

      <td>Default:&nbsp;&nbsp;

          <code>172800000</code>

          <code>&nbsp;</code>

      </td>

    </tr>

    <tr>

  <code>lib/metacat.properties</code>. Under most circumstances,

      <li>build/src/upgrade-db-to-1.6.sql</li>

      <li>build/src/upgrade-db-to-1.7.sql</li>

    For example, if you had an existing metacat 1.4 installation and you were upgrading 

    to metacat 1.7, you would need to run three scripts in sequence:

    upgrade-db-to-1.5.sql, upgrade-db-to-1.6.sql, and upgrade-db-to-1.7.sql. 

    However, if you were starting from a Metacat 1.6

    installation, you would only need to run the upgrade-db-to-1.7.sql script.

    <em>Be sure to use the version of the scripts from the 'build/src' directory: they

    are customized for your installation in that directory.</em>

  catalina.sh file in tomcat bin directory. The reason is that GeoServer uses X11 windows to draw graphics.