Project

General

Profile

metacat / docs / user / metacatinstall.html @ 2455

1
<!-- 
2
  *   '$RCSfile$'
3
  *     Purpose: web page describing the installation of Metacat
4
  *   Copyright: 2000 Regents of the University of California and the
5
  *               National Center for Ecological Analysis and Synthesis
6
  *     Authors: Chad Berkley
7
  *
8
  *    '$Author: jones $'
9
  *      '$Date: 2005-04-05 16:46:25 -0700 (Tue, 05 Apr 2005) $'
10
  *  '$Revision: 2455 $'
11
  *
12
  *
13
  -->
14
  
15
<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.0//EN">
16
<html>
17

    
18
<head>
19
  <title>Metacat Installation Instructions</title>
20
  <link rel="stylesheet" type="text/css" href="@docrooturl@default.css">
21
</head>
22

    
23
<body>
24

    
25
<table class="tabledefault" width="100%">
26
<tr><td rowspan="2"><img src="@docrooturl@images/KNBLogo.gif"></td>
27
<td colspan="7">
28
<div class="title">Metacat UNIX Installation Instructions</div>
29
</td>
30
</tr>
31
<tr>
32
  <td><a href="@server@/" class="toollink"> KNB Home </a></td>
33
  <td><a href="@server@/data.html" class="toollink"> Data </a></td>
34
  <td><a href="@server@/people.html" class="toollink"> People </a></td>
35
  <td><a href="@server@/informatics" class="toollink"> Informatics </a></td>
36
  <td><a href="@server@/biodiversity" class="toollink"> Biocomplexity </a></td>
37
  <td><a href="@server@/education" class="toollink"> Education </a></td>
38
  <td><a href="@server@/software" class="toollink"> Software </a></td>
39
</tr>
40
</table>
41
<hr>
42

    
43
<table class="tabledefault" width="100%">
44
<td class="tablehead" colspan="2"><p class="emphasis">***Disclaimer***</p></td>
45
<tr>
46
<td>
47
  <p class="emphasis">
48
   These installation instructions are meant for a systems administrator/DBA
49
   or someone who is an advanced computer user.  They are NOT meant for
50
   the average computer user.  Please realize that by executing these
51
   instructions, you may have to trouble shoot many advanced issues yourself.
52
</td>
53
</tr>
54
</table>
55

    
56
<table class="tabledefault" width="100%">
57
<td class="tablehead" colspan="2"><p>Pre-Installation</p></td>
58
<tr>
59
<td>
60
  <p class="header">Minimum Requirements</p> 
61
  <p>
62
   Installing Metacat requires a server running an SQL92 compliant database
63
   (Oracle 8i recommended) with at least 128MB RAM, and a Pentium III class
64
   processor or higher.  The amount of disk space required depends on the
65
   size of your RDBMS tablespace (which should be at least 10 MB, 
66
   however Metacat itself requires only about 1 MB of free space after 
67
   installation.  These instructions assume a Linux environment but may
68
   work on other UNIX type environments, however this has not been tested.
69
  </p>
70
  <p class = "header">Additional Required Software</p>
71
  <p>
72
   The server on which you wish to install Metacat must have the following
73
   software installed and running correctly before attempting to install
74
   Metacat.
75
   <ul>
76
     <li><a href="http://www.oracle.com">Oracle 8i</a> (or another SQL92
77
         compliant RDBMS like Postgres)</li>
78
     <li><a href="http://jakarta.apache.org/ant/index.html">Apache Jakarta-Ant</a>
79
     </li>
80
     <li><a href="http://jakarta.apache.org/tomcat/index.html">Apache Jakarta-Tomcat</a>
81
       <p class="emphasis">Note: For a more robust web serving environment, 
82
       Apache web server should
83
       be installed along with Tomcat and the two should be integrated
84
       as described on the Apache web site.</p>
85
     </li>
86
   </ul>
87
  </p>
88
</td>
89
</tr>
90
</table>
91

    
92
<table class="tabledefault" width="100%">
93
<td class="tablehead" colspan="2"><p>Aditional Software Setup</p></td>
94
<tr>
95
<td>
96
  <p class="header">Java</p>
97
  <p>You'll need a recent Java SDK; j2sdk1.4.2 or later is required.  We haven't 
98
  tested with any of the 1.5.x versions yet, so probably best to stay with 1.4.x.
99
  Make sure that JAVA_HOME environment variable is properly set and that both
100
  java and javac are on your PATH.
101
  </p>
102
  <p class="header">Oracle 8i or Postgres</p>
103
  <p><i>Oracle:</i><br>
104
   The Oracle RDBMS must be installed and running as a daemon on the system.
105
   In addition the JDBC listener must be enabled.  You can enable it by
106
   logging in as your Oracle user and typing the following:
107
   <pre>lsnrctl start</pre>
108
   Your instance should have a table space of at least 5 MB (10 MB or higher 
109
   recommended).  You should also have a username specific to Metacat
110
   created and enabled.  This user must have most normal permissions 
111
   including CREATE SESSION, CREATE TABLE, CREATE INDEX, CREATE TRIGGER, 
112
   EXECUTE PROCEDURE, EXECUTE TYPE, etc.  If an action is unexplainably 
113
   rejected by Metacat it is probably because the user permissions are not
114
   correctly set.
115
  </p>
116
  <p><i>Postgres:</i><br>
117
  Postgres can be easily installed on most linux distributions and on
118
  Windows (using cygwin) and Mac OS X.  Using Fedora Core or RedHat Linux,
119
  you can install the rpms for postgres and then run 
120
  <code>/etc/init.d/postgresql start</code> in order to start the database.
121
  This initializes the data files.  You need to do a bit of configuration
122
  to create a database and set up a user account and allow internet access
123
  via jdbc.  See the postgres documentation for this, but here is a quick 
124
  start:
125
  <ul>
126
     <li>Switch to the "postgres" user account and edit "data/pg_hba.conf", adding the following line to the file:<br>
127
     <code>host   metacat  metacat      127.0.0.1         255.255.255.255   password</code><br>
128
     If your host uses IPv6 addresses, you made need this line instead:
129
     <code>host   metacat  metacat      ::1               ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff password</code></li>
130
     <li>Edit the "data/postgres.conf" file and uncomment and edit the line
131
     starting with "tcpip_socket" so that it reads 
132
     <code>tcpip_socket = true</code></li>
133
     <li>Run <code>createdb metacat</code> to create a new database</li>
134
     <li>Run <code>psql metacat</code> to log in using the postgres account and create a new "metacat" user account
135
     <ul>
136
        <li>In postgres, run <code>CREATE USER metacat WITH UNENCRYPTED PASSWORD 'apasswordyoulike';</code></li>
137
        <li>This creates a new account called metacat on the database named metacat</li>
138
        <li>Note: there are many ways to do this, so others such as using 
139
        ENCRYPTED passwords will work fine.</li>
140
     </ul>
141
     </li>
142
     <li>Exit the postgres account back to root and restart the postgres 
143
     database with <code>/etc/init.d/postgresql restart</code></li>
144
     <li>Test logging into the postgres db using the metacat account with 
145
     the following command: 
146
     <code>psql -U metacat -W -h localhost metacat</code></li>
147
  </ul>
148
  </p>
149
  <p class="header">Ant</p>
150
  <p>
151
   Ant is a Java based build application similar to Make on UNIX systems.  
152
   It takes in installation parameters from a file in the root installation
153
   directory named "build.xml".  The Metacat CVS module contains a default
154
   build.xml file that may require some modification upon installation.  Ant
155
   should be installed on the system and the "ant" executable shell script 
156
   should be available in the users path. We note that the current build is 
157
   not working with Ant 1.6.x, so you'll need to use an earler version.  We have 
158
   successfully used Ant 1.5.1, 1.5.2, and some earlier versions.
159
  </p>
160
  <p class="header">Tomcat</p>
161
  <p>
162
    Install Tomcat into the directory of your choice. The directory in which 
163
    you install Tomcat itself will be referred to as the "$CATALINA_HOME".
164
    We recommend that you install Tomcat version 4.0.  More details about 
165
    Tomcat installation is available <a href=" http://jakarta.apache.org/tomcat/index.html">here</a>.
166
  </p>
167
 </td>
168
</tr>
169
</table>
170

    
171
<table class="tabledefault" width="100%">
172
<td class="tablehead" colspan="2"></td>
173
<tr>
174
<td>
175
  <p>
176
   Once all of the prerequisite software is installed as described above, 
177
   the installation of Metacat can begin.  First you must have a current
178
   version of the source distribution of Metacat.  You can get it two ways.
179
   Authorized users can check it out of the NCEAS 
180
   <a href="http://www.nceas.ucsb.edu/cgi-bin/cvsweb.cgi/xmltodb/">CVS</a>
181
   system. You'll need both the "metacat" module and the "utilities" module to
182
   be checked out in sibling directories. The command is as follows: 
183
   <pre>mkdir knb-software</pre>
184
   <pre>cd knb-software</pre>
185
   <pre>cvs checkout -P metacat</pre>
186
   <pre>cvs checkout -P utilities</pre>  
187
   Or you can 
188
   <a href="@server@/software/download.html">download</a> a gzipped tar file
189
   from this site.
190
  </p>
191
  <p><h2>Edit <code>build.properties</code> File</h2></p>
192
  <p>
193
   Once you have either checked out or unzipped and untarred the source
194
   distribution, you can begin the installation process.  Change into the 
195
   metacat directory and edit the file called "<code>build.properties</code>".  You will need 
196
   to change a number of configuration properties to match the setup on
197
   your system.
198
  </p>
199
  <p>
200
  The properties that you will likely need to change will include 
201
  <code>tomcat</code>, <code>tomcatversion</code>, <code>webapps</code>, 
202
  <code>context</code>, <code>server</code>, <code>httpserver</code>, 
203
  <code>database</code>, <code>jdbc-connect</code>, <code>jdbc-base</code>, 
204
  <code>user</code>, <code>password</code>, <code>datafilepath</code>, 
205
  <code>inlinedatafilepath</code>, <code>cvsroot</code>, 
206
  <code>cvsroot-alternate</code>, <code>default-style</code>, and
207
  <code>administrators</code>. 
208
  Each is described in detail in the table below.
209
  </p>
210
  Properties you will likely need to change:
211
  <br><br>
212
  <table border="1">
213
    <tr>
214
      <td><b>Property</b></td>
215
      <td><b>Description</b></td>
216
      <td><b>Default value and examples of other values</b></td>
217
    </tr>
218
    <tr>
219
      <td>tomcat</td>
220
      <td>The tomcat property is the location in which tomcat is installed.</td>
221
      <td>Default:&nbsp;&nbsp;
222
          <code>/usr/local/devtools/jakarta-tomcat</code>
223
      <br><br>Example:&nbsp;&nbsp;
224
          <code>C:/Tomcat4</code></td>
225
    </tr>
226
    <tr>
227
      <td>tomcatversion</td>
228
      <td>The tomcatversion property is the version of your Tomcat. You should 
229
          put tomcat3, tomcat4, or tomcat5 here. We have most extensively 
230
          tested Tomcat 4.x, but Tomcat 5.x seems to work fine as well.
231
      </td>
232
      <td>Default:&nbsp;&nbsp;
233
          <code>tomcat4</code>
234
      <br><br>Example:&nbsp;&nbsp;
235
          <code>tomcat3</code>
236
      </td>
237
    </tr>
238
    <tr>
239
      <td>webapps</td>
240
      <td>The webapps property is the location in which your tomcat servlet 
241
          contexts are installed. This is typically "TOMCAT_HOME/webapps",
242
          where TOMCAT_HOME is the same value that you entered for the 'tomcat'
243
          property above.
244
      </td>
245
      <td>Default:&nbsp;&nbsp;
246
          <code>/var/www/org.ecoinformatics.knb</code>
247
      <br><br>Example:&nbsp;&nbsp;
248
          <code>C:/Tomcat4/webapps</code>
249
      </td>
250
    </tr>
251
    <tr>
252
      <td>context</td>
253
      <td>The context property is the name of the servlet context in which you 
254
          want Metacat to be installed. This will determine the installation 
255
          directory for the servlet and many of the URLs that are used to access
256
          the installed Metacat server.</td>
257
      <td>Default:&nbsp;&nbsp;
258
          <code>knb</code>
259
      <br><br>Example:&nbsp;&nbsp;
260
          <code>mycontext</code>
261
      </td>
262
    </tr>
263
    <tr>
264
      <td>server</td>
265
      <td>The server property is hostname of for the server on which Metacat is 
266
          running (note that you should not include the 'http://' in the server 
267
          property). The server setting should include the port number 
268
          appended to the end if Tomcat is running stand-alone (see example).
269
      </td>
270
      <td>Default:&nbsp;&nbsp;
271
         <code>knb.ecoinformatics.org</code>
272
      <br><br>Example:&nbsp;&nbsp;
273
         <code>somehost.university.edu:8080</code>
274
      </td>
275
    </tr>
276
    <tr>
277
      <td>httpserver</td>
278
      <td>httpserver is the plain HTTP address on which Metacat is running 
279
          (note that you should not include the 'http://' in the httpserver 
280
          property).
281
          The httpserver setting should include the HTTP plain port number 
282
          appended to the end if Tomcat is running stand-alone (see example).</td>
283
      <td>Default:&nbsp;&nbsp;
284
          <code>knb.ecoinformatics.org</code>
285
      <br><br>Example:&nbsp;&nbsp;
286
          <code>somehost.university.edu:8080</code>
287
      </td>
288
    </tr>
289
    <tr>
290
      <td>ldapUrl</td>
291
      <td>URL to the LDAP server. The LDAP server is used in the default
292
          authentication module to authenticate and identify users of the
293
          system.  To participate in the KNB network, you should leave this at
294
          the default.  But it can be changed if you want to use a 
295
          different directory of users.
296
      </td>
297
      <td>Default:&nbsp;&nbsp;
298
          <code>ldap://ldap.ecoinformatics.org/dc=ecoinformatics,dc=org</code>
299
      </td>
300
    </tr>
301
    <tr>
302
      <td>database</td>
303
      <td>Select the database to use for metadata storage.
304
          Valid values are <code>oracle</code>, <code>postgresql</code>, or
305
          <code>sqlserver</code>. Note that sqlserver support is minimal and
306
          probably will not work without substantial changes on your part,
307
          possibly including code changes.  We have not revcently tested on 
308
          sqlserver.
309
      </td>
310
      <td>Default:&nbsp;&nbsp;
311
          <code>oracle</code>
312
      <br><br>Other possible values:&nbsp;&nbsp;
313
          <code>postgresql</code>&nbsp;&nbsp;
314
          <code>sqlserver</code>
315
      </td>
316
    </tr>
317
    <tr>
318
      <td>jdbc-connect</td>
319
      <td>The JDBC connection string used to connect to the database.</td>
320
      <td>Default:&nbsp;&nbsp;
321
          <code>jdbc:oracle:thin:@metacat.nceas.ucsb.edu:1521:knb</code>
322
      </td>
323
    <tr>
324
      <td>jdbc-base</td>
325
      <td>The base directory for locating JDBC jar files (not needed for postgresql).</td>
326
      <td>Default:&nbsp;&nbsp;
327
          <code>/usr/oracle/jdbc/lib</code>
328
      <br><br>Example:&nbsp;&nbsp;
329
          <code>C:/jdev10g/jdbc/lib</code><br>
330
      </td>
331
    </tr>
332
    <tr>
333
      <td>user</td>
334
      <td>The database user name that you set up to use Metacat. For example, 
335
          an Oracle username.</td>
336
      <td>Default:&nbsp;&nbsp;
337
          <code>knb</code>
338
      <br><br>Example:&nbsp;&nbsp;
339
          <code>metacatdb</code>
340
      </td>
341
    </tr>
342
    <tr>
343
      <td>password</td>
344
      <td>The database password that you set up to use Metacat.</td>
345
      <td>Default:&nbsp;&nbsp;
346
          <code>yourPasswordHere</code>
347
      <br><br>Example:&nbsp;&nbsp;
348
          <code>metacat123</code>
349
      </td>
350
    </tr>
351
    <tr>
352
      <td>datafilepath</td>
353
      <td>The datafilepath is the directory to store data files.</td>
354
      <td>Default:&nbsp;&nbsp;
355
          <code>/var/metacat/data</code>
356
      <br><br>Example:&nbsp;&nbsp;
357
          <code>C:/Tomcat4/data/knb/data</code>
358
      </td>
359
    </tr>
360
    <tr>
361
      <td>inlinedatafilepath</td>
362
      <td>The inlinedatafilepath is the directory to store inline data that
363
          has been extracted from EML documents.</td>
364
      <td>Default:&nbsp;&nbsp;
365
          <code>/var/metacat/inline-data</code>
366
      <br><br>Example:&nbsp;&nbsp;
367
          <code>C:/Tomcat4/data/knb/inlinedata</code>
368
      </td>
369
    </tr>
370
    <tr>
371
      <td>default-style</td>
372
      <td>The default-style parameter defines the "style-set" that is to be used
373
          by default when the qformat parameter is missing or set to "html"
374
          during a query. It is set to "knb", which is one of the styles that 
375
          ships with the default metacat distribution. Other possible settings
376
          are shown in the examples to the right.</td>
377
      <td>Default:&nbsp;&nbsp;
378
          <code>knb</code>
379
      <br><br>Examples:&nbsp;&nbsp;
380
          <pre><code>default   esa   knb2   nceas   nrs   obfs   specnet</code></pre>
381
      </td>
382
    </tr>
383
    <tr>
384
      <td>administrators</td>
385
      <td>The administrators parameter lists the accounts that are allowed to
386
          perform administrative actions such as rebuilding indices for 
387
          documents. The list can can contain more than one account separated
388
          by colons.</td>
389
      <td>Default:&nbsp;&nbsp;
390
          <code>uid=jones,o=NCEAS,dc=ecoinformatics,dc=org</code>
391
      <br><br>Examples:&nbsp;&nbsp;
392
          <code>uid=localadmin,o=ucnrs.org</code>
393
      </td>
394
    </tr>
395
  </table>
396
  <br>
397
  <p>
398
   Note that the build file is preconfigured to install Metacat either using 
399
   Oracle, PostgreSQL, or Microsoft SQL Server as a backend database.  
400
   To change the database system, simply change the value of the 'database' 
401
   property to be the name of the database target that you wish to use 
402
   (either 'oracle', 'postgresql', or 'sqlserver').
403
  </p>
404
  Other properties in <code>build.properties</code> that you can (but generally need not) change:<br />
405
  <br>
406
  <table border="1">
407
    <tr>
408
      <td><b>Property</b></td>
409
      <td><b>Description</b></td>
410
      <td><b>Default value and examples of other values</b></td>
411
    </tr>
412
    <tr>
413
      <td>inst.cgi.dir</td>
414
      <td>Installation directory for registry CGI scripts</td>
415
      <td>Default:&nbsp;&nbsp;
416
          <code>/var/www/cgi-knb</code>
417
      </td>
418
    </tr>
419
    <tr>
420
      <td>cgi-prefix</td>
421
      <td>&nbsp;</td>
422
      <td>Default:&nbsp;&nbsp;
423
          <code>http://knb.ecoinformatics.org/cgi-bin</code>
424
      </td>
425
    </tr>
426
    <tr>
427
      <td>knb-site-url</td>
428
      <td>This is the URL to the web context root for the knb site. 
429
          It is used for the qformat=knb skin only.</td>
430
      <td>Default:&nbsp;&nbsp;
431
          <code>http://knb.ecoinformatics.org</code>
432
      </td>
433
    </tr>
434
    <tr>
435
      <td>forcereplicationwaitingtime</td>
436
      <td>The waiting time before replication is forced to begin after
437
          uploading a package. The default value should usually suffice.</td>
438
      <td>Default:&nbsp;&nbsp;
439
          <code>30000</code>
440
          <code>&nbsp;</code>
441
      </td>
442
    </tr>
443
    <tr>
444
      <td>cvsroot</td>
445
      <td>CVS access to retrieve latest EML. Only used by
446
          developers in building the release.</td>
447
      <td>Default:&nbsp;&nbsp;
448
          <code><pre>:ext:${env.USER}@cvs.ecoinformatics.org:/cvs</pre></code>
449
          Example:&nbsp;&nbsp;
450
          <code><pre>:ext:myaccount@cvs.ecoinformatics.org:/cvs</pre></code>
451
      </td>
452
    </tr>
453
    <tr>
454
      <td>cvsroot-alternate</td>
455
      <td>CVS access to retrieve latest conversion styles. Only used by
456
          developers in building the release.</td>
457
      <td>Default:&nbsp;&nbsp;
458
          <code><pre>:ext:${env.USER}@cvs.nceas.ucsb.edu:/cvs/pbi</pre></code>
459
          Example:&nbsp;&nbsp;
460
          <code><pre>:ext:myaccount@cvs.nceas.ucsb.edu:/cvs/pbi</pre></code>
461
      </td>
462
    </tr>
463
  </table>
464
  <p>
465
  Metacat has a number of additional settable properties in file
466
  <code>metacat/lib/metacat.properties</code>. Under most circumstances,
467
  you will not need to modify this file because the properties of interest
468
  to you can be controlled by editing <code>build.properties</code> as
469
  described above. To learn more about Metacat's additional properties,
470
  see <a href="./properties.html">Metacat Properties File</a>.
471
  </p>
472
  <p class="emphasis">
473
   Note: When setting properties, DO NOT add a trailing slash [/] to the end of any paths that are specified.
474
   Metacat will not function correctly if you do so.
475
  </p>
476

    
477
</td>
478
</tr>
479
</table>
480

    
481
<table class="tabledefault" width="100%">
482
<td class="tablehead" colspan="2"><p><h2>Compilation and Installation</h2></p></td>
483
<tr>
484
<td>
485
  <a name="protocol"></a>
486
  <p>
487
   Ant allows compilation and installation to be done in one step.
488
   Change into the metacat directory and type: 
489
   <pre><b>ant install</b></pre>
490
   or, if you are upgrading an existing installation, type:
491
   <pre><b>ant clean upgrade</b></pre>
492
   <p>
493
   You should see a bunch of messages telling you the progress of compilation
494
   and installation.  When it is done you should see the message 
495
   BUILD SUCCESSFUL
496
   and you should be returned to a UNIX command prompt.  If you do not see
497
   the message BUILD SUCCESSFUL then there was an error that you need to 
498
   resolve.
499
   This may come up if you are logged in as a user that does not have write
500
   access to one or more of the directories that are listed in the build.xml
501
   file, or if any of the paths to files are not configured correctly in the
502
   "config" target.
503
  </p>
504
  <p>
505
  Note: The 'data' directories that are indicated in the 'datafilepath' and
506
  'inlinedatafilepath' build properties must be writeable
507
  by user account under which Tomcat runs or you will not be able to upload 
508
  data files to the system.
509
  </p>
510

    
511
  <p class="header"><h2>SQL Scripts</h2></p>
512
  <p>
513
   You now need to set up the table structure in your database.  You can do
514
   either do this using the ant build system, or by manually running the
515
   scripts using a sql utility.
516
  </p>
517
  <p><b>WARNING: Do NOT run this on an existing metacat installation as it
518
  will delete all of your data.  If you have an existing metacat installation,
519
  see the instructions for "Upgrading" below.</b></p>
520

    
521
  <p>To run the scripts using ant, type <code>ant installdb</code>.  This does 
522
  not work for postgres, so you'll need to run the xmltables-postgres.sql script 
523
  manually (see next paragraph).
524
  </p>
525
  <p>To run the scripts manually, change to the
526
   metacat/build/src directory.  Then run you RDBMS's SQL utility.  In Oracle it is
527
   SQLPlus.  This tutorial assumes an Oracle database so this example is for
528
   SQLPlus.  Login as the oracle user that was set up for use with Metacat.
529
   At the SQLPlus prompt type the following: <pre><b>@xmltables.sql;</b></pre>
530
   For postgres, use a command like: 
531
   <code>psql -U metacat -W -h localhost -f build/src/xmltables-postgres.sql metacat</code>
532
  </p>
533
  <p>Either way, 
534
   you should see a bunch of output showing the creation of the Metacat table
535
   space. The first time you run this script you will get several errors at the 
536
   beginning saying that you cannot drop a table/index/trigger because it 
537
   does not exist.  This is normal.  Any other errors besides this need to be
538
   resolved before continuing. The script file name for PostgreSQL is 
539
   xmltables-postgres.sql and for Microsoft SQL server is 
540
   xmltables-sqlserver.sql.
541
  </p>
542
  <p>
543
   If the script has run correctly you should be able to type 
544
   <pre>describe xml_documents</pre> and it should show:
545
   <pre>
546
    Name            Null?         Type
547
    --------------  ------------  ---------------- 
548
     DOCID          NOT NULL      VARCHAR2(250)
549
     ROOTNODEID                   NUMBER(20)
550
     DOCNAME                      VARCHAR2(100)
551
     DOCTYPE                      VARCHAR2(100)
552
     DOCTITLE                     VARCHAR2(1000)
553
     USER_OWNER                   VARCHAR2(100)
554
     USER_UPDATED                 VARCHAR2(100)
555
     SERVER_LOCATION              NUMBER(20)
556
     REV                          NUMBER(10)
557
     DATE_CREATED                 DATE
558
     DATE_UPDATED                 DATE
559
     PUBLIC_ACCESS                NUMBER(1)
560
     UPDATED                      NUMBER(1)
561
   </pre>
562
  </p>
563
  <p class="header"><h2>Registering schemas and DTDs</h2></p>
564
  <p>Once the tables have been created, you should also register the Ecological
565
  Metadata Language (EML) DTDs and schemas. <b>However, note that you should 
566
  NOT do this if you are upgrading an existing installation -- the upgrade
567
  scripts take care of it for you (see the next section).</b>  If you are
568
  installing new, you can register the schema documents by running:</p>
569
  <pre><b>ant register-schemas</b></pre> 
570
  <p>This command registers the EML DTDs' and schemas' location in the 
571
  metacat server.  Your database username and password have to be set correctly
572
  for this to work.  Also, if for some reason running this script from ant
573
  does not work, you could instead try running "build/src/loaddtdschema.sql"
574
  from your sql utility (but be sure to use the version in the 'build' directory
575
  that has been customized for your installation).
576
  </p>
577
  <p class="header"><h2>Upgrading SQL Scripts</h2></p>
578
  <p>
579
    If you have an existing metacat installation, you should not run the install
580
    script because it will replace all of the older tables with new, empty 
581
    copies of the tables.  Thus you would lose your data!  Instead, you can 
582
    run some upgrade scripts that will change the table structure as needed for
583
    the new version.  If you are skipping versions, run each upgrade script
584
    for the intermediate versions as well.  Currently the upgrade scripts are:
585
   </p>
586
    <ul>
587
      <li>build/src/upgrade-db-to-1.2.sql</li>
588
      <li>build/src/upgrade-db-to-1.3.sql</li>
589
      <li>build/src/upgrade-db-to-1.4.sql</li>
590
    </ul>
591
   <p>
592
    So, if you had an existing metacat 1.0 installation and you were upgrading 
593
    to 1.4, you would need to run all three scripts in sequence:
594
    upgrade-db-to-1.2.sql, upgrade-db-to-1.3.sql, and upgrade-db-to-1.4.sql. 
595
    However, if you were starting from a Metacat 1.3.x
596
    installation, you would only need to run the upgrade-db-to-1.4.sql script.
597
    Be sure to use the version of the scripts from the 'build' directory they
598
    are customized for your installation in that directory.
599
   </p>
600
  </p>
601
  <h2>Restart Tomcat</h2>
602
  <p>
603
   Once you have successfully installed Metacat, there is one more step.  Tomcat
604
   (and Apache if you have Tomcat integrated with it) must be restarted.  To do
605
   this, login as the user that runs your tomcat server (often "tomcat"),
606
   go to $CATALINA_HOME/bin and type:
607
   <pre>
608
   ./shutdown.sh 
609
   ./startup.sh 
610
   </pre>
611
   In the Tomcat startup messages you should see something in log file like:
612
   <pre>
613
    MetacatServlet Initialize
614
    Context log path="/metadata" :Metacat: init
615
    MetacatServlet Initialize
616
   </pre>
617
   If you see that message Tomcat is successfully loading the Metacat servlet.
618
   Next, try to run your new servlet.  Go to a web browser and type:
619
   <pre>http://yourserver.yourdomain.com/yourcontext/</pre>
620
   You should substitute your context name for "yourcontext" in the url above.
621
   If everything is working correctly, you should see a query page followed
622
   by an empty result set.  Note that if you do not have Tomcat integrated with
623
   Apache you will probably have to type
624
   <pre>http://yourserver.yourdomain.com:8080/yourcontext/</pre>
625
  </p>
626
</td>
627
</tr>
628
</table>
629

    
630
</body>
631
</html>