Revision 2182
Added by Matt Jones over 20 years ago
docs/user/metacatinstall.html | ||
---|---|---|
93 | 93 |
<td class="tablehead" colspan="2"><p>Aditional Software Setup</p></td> |
94 | 94 |
<tr> |
95 | 95 |
<td> |
96 |
<p class="header">Oracle 8i</p> |
|
97 |
<p> |
|
96 |
<p class="header">Java</p> |
|
97 |
<p>You'll need a recent Java SDK, preferably j2sdk1.4.2 or later. 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> |
|
98 | 104 |
The Oracle RDBMS must be installed and running as a daemon on the system. |
99 | 105 |
In addition the JDBC listener must be enabled. You can enable it by |
100 | 106 |
logging in as your Oracle user and typing the following: |
... | ... | |
107 | 113 |
rejected by Metacat it is probably because the user permissions are not |
108 | 114 |
correctly set. |
109 | 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></li> |
|
128 |
<li>Edit the "data/postgres.conf" file and uncomment and edit the line |
|
129 |
starting with "tcpip_socket" so that it reads |
|
130 |
<code>tcpip_socket = true</code></li> |
|
131 |
<li>Run <code>createdb metacat</code> to create a new database</li> |
|
132 |
<li>Run <code>psql metacat</code> to log in using the postgres account and create a new "metacat" user account |
|
133 |
<ul> |
|
134 |
<li>In postgres, run <code>CREATE USER metacat WITH UNENCRYPTED PASSWORD 'apasswordyoulike';</code></li> |
|
135 |
<li>This creates a new account called metacat on the database named metacat</li> |
|
136 |
<li>Note: there are many ways to do this, so others such as using |
|
137 |
ENCRYPTED passwords will work fine.</li> |
|
138 |
</ul> |
|
139 |
</li> |
|
140 |
<li>Exit the postgres account back to root and restart the postgres |
|
141 |
database with <code>/etc/init.d/postgresql restart</code></li> |
|
142 |
<li>Test logging into the postgres db using the metacat account with |
|
143 |
the following command: |
|
144 |
<code>psql -U metacat -W -h localhost metacat</code></li> |
|
145 |
</ul> |
|
146 |
</p> |
|
110 | 147 |
<p class="header">Ant</p> |
111 | 148 |
<p> |
112 | 149 |
Ant is a Java based build application similar to Make on UNIX systems. |
... | ... | |
114 | 151 |
directory named "build.xml". The Metacat CVS module contains a default |
115 | 152 |
build.xml file that may require some modification upon installation. Ant |
116 | 153 |
should be installed on the system and the "ant" executable shell script |
117 |
should be available in the users path. |
|
154 |
should be available in the users path. We note that the current build is |
|
155 |
not working with Ant 1.6.x, so you'll need to use an earler version. We have |
|
156 |
successfully used Ant 1.5.1, 1.5.2, and some earlier versions. |
|
118 | 157 |
</p> |
119 | 158 |
<p class="header">Tomcat</p> |
120 | 159 |
<p> |
... | ... | |
307 | 346 |
either do this using the ant build system, or by manually running the |
308 | 347 |
scripts using a sql utility. |
309 | 348 |
</p> |
310 |
<p>To run the scripts using ant, type "ant installdb". |
|
349 |
<p><b>WARNING: Do NOT run this on an existing metacat installation as it |
|
350 |
will delete all of your data. If you have an existing metacat installation, |
|
351 |
see the instructions for "Upgrading" below.</b></p> |
|
352 |
|
|
353 |
<p>To run the scripts using ant, type <code>ant installdb</code>. This does |
|
354 |
not work for postgres, so you'll need to run the xmltables-postgres.sql script |
|
355 |
manually (see next paragraph). |
|
311 | 356 |
</p> |
312 | 357 |
<p>To run the scripts manually, change to the |
313 | 358 |
metacat/src directory. Then run you RDBMS's SQL utility. In Oracle it is |
314 | 359 |
SQLPlus. This tutorial assumes an Oracle database so this example is for |
315 | 360 |
SQLPlus. Login as the oracle user that was set up for use with Metacat. |
316 | 361 |
At the SQLPlus prompt type the following: <pre><b>@xmltables.sql;</b></pre> |
362 |
For postgres, use a command like: |
|
363 |
<code>psql -U metacat -W -h localhost -f build/src/xmltables-postgres.sql metacat</code> |
|
317 | 364 |
</p> |
318 | 365 |
<p>Either way, |
319 | 366 |
you should see a bunch of output showing the creation of the Metacat table |
... | ... | |
357 | 404 |
<ul> |
358 | 405 |
<li>upgrade-db-to-1.2.sql</li> |
359 | 406 |
<li>upgrade-db-to-1.3.sql</li> |
407 |
<li>upgrade-db-to-1.4.sql</li> |
|
360 | 408 |
</ul> |
361 | 409 |
<p> |
362 | 410 |
So, if you had an existing metacat 1.0 installation and you were upgrading |
... | ... | |
377 | 425 |
<p> |
378 | 426 |
Ant allows compilation and installation to be done in one step. |
379 | 427 |
Change into the metacat directory and type: |
380 |
<pre><b>ant install</b></pre> |
|
428 |
<pre><b>ant geteml install</b></pre> |
|
429 |
or, if you are upgrading an existing installation, type: |
|
430 |
<pre><b>ant geteml upgrade</b></pre> |
|
381 | 431 |
<p> |
382 | 432 |
You should see a bunch of messages telling you the progress of compilation |
383 | 433 |
and installation. When it is done you should see the message |
Also available in: Unified diff
New instructions, particularly regarding some of the problems I had on
postgres remembering how to set up the user access control and tcp connections.