Revision 4571
Added by daigle about 16 years ago
| metacatinstall.html | ||
|---|---|---|
| 62 | 62 |
<div class="toc2"><a href="#MinRequirements">Minimum Requirements</a></div> |
| 63 | 63 |
<div class="toc2"><a href="#AdditionalRequiredSoftware">Additional Required Software</a></div> |
| 64 | 64 |
<div class="toc1"><a href="#AdditionalSoftwareSetup">Additional Software Setup</a></div> |
| 65 |
<div class="toc2"><a href="#AdditionalSoftwareJava">Java</a></div> |
|
| 66 |
<div class="toc2"><a href="#AdditionalSoftwareOracle">Oracle</a></div> |
|
| 67 |
<div class="toc2"><a href="#AdditionalSoftwarePostgres">PostgreSQL</a></div> |
|
| 68 |
<div class="toc2"><a href="#AdditionalSoftwareAnt">Ant</a></div> |
|
| 69 |
<div class="toc2"><a href="#AdditionalSoftwareTomcat">Tomcat</a></div> |
|
| 65 | 70 |
<div class="toc1"><a href="#InstallingMetacat">Installing Metacat</a></div> |
| 71 |
<div class="toc2"><a href="#InstallDownloadMetacat">Download Metacat Application</a></div> |
|
| 72 |
<div class="toc2"><a href="#InstallMetacatWar">Install Metacat War</a></div> |
|
| 73 |
<div class="toc2"><a href="#InstallRestartTomcat">Restart Tomcat</a></div> |
|
| 74 |
<div class="toc2"><a href="#InstallTroubleshooting">Troubleshooting</a></div> |
|
| 75 |
<div class="toc2"><a href="#InstallConfigureMetacat">Configure Metacat</a></div> |
|
| 66 | 76 |
<div class="toc1"><a href="#UpgradingMetacat">Upgrading Existing Metacat</a></div> |
| 67 |
<div class="toc1"><a href="#Registry">Registry</a></div> |
|
| 77 |
<div class="toc2"><a href="#UpgradeStopMetacat">Stop the Running Metacat</a></div> |
|
| 78 |
<div class="toc2"><a href="#UpgradeDownloadMetacat">Download Latest Metacat Application</a></div> |
|
| 79 |
<div class="toc2"><a href="#UpgradeMetacatWar">Upgrade Metacat War</a></div> |
|
| 80 |
<div class="toc2"><a href="#UpgradeRestartTomcat">Restart Tomcat</a></div> |
|
| 81 |
<div class="toc2"><a href="#UpgradeTroubleshooting">Troubleshooting</a></div> |
|
| 82 |
<div class="toc2"><a href="#UpgradeConfigureMetacat">Configure Metacat</a></div> |
|
| 83 |
<div class="toc1"><a href="#Registry">Web Based Registry</a></div> |
|
| 68 | 84 |
</div> |
| 69 | 85 |
|
| 70 | 86 |
<a name="QuickInstructions"></a><div class="header1">Quick Instructions</div> |
| ... | ... | |
| 117 | 133 |
<p>Set up and enable knb (Metacat) site configurations by typing:</p> |
| 118 | 134 |
<div class="code">sudo cp <metacat_package_dir>/knb /etc/apache2/sites-available</div> |
| 119 | 135 |
<div class="code">sudo a2ensite knb</div> |
| 136 |
<p>If you are going to make use of an LSID server, set up and enable the authority service site |
|
| 137 |
configurations by typing:</p> |
|
| 138 |
<div class="code">sudo cp <metacat_package_dir>/authority /etc/apache2/sites-available</div> |
|
| 139 |
<div class="code">sudo a2ensite authority</div> |
|
| 120 | 140 |
<p>Restart apache to bring in changes by typing:</p> |
| 121 | 141 |
<div class="code">sudo /etc/init.d/apache2 force-reload</div> |
| 122 | 142 |
</div> |
| ... | ... | |
| 257 | 277 |
</ul> |
| 258 | 278 |
</p> |
| 259 | 279 |
|
| 260 |
<table class="tabledefault" width="100%"> |
|
| 261 |
<td class="tablehead" colspan="2"><p><a name="Additional Software Setup"><h2>Aditional Software Setup</h2></p></td> |
|
| 262 |
<tr> |
|
| 263 |
<td> |
|
| 264 |
<p class="header">Java</p> |
|
| 280 |
<a name="AdditionalSoftwareSetup"></a><div class="header1">Additional Software Setup</div> |
|
| 281 |
<a name="AdditionalSoftwareJava"></a><div class="header2">Java</div> |
|
| 265 | 282 |
<p>You'll need a recent Java SDK; J2SE 1.4.2 or later is required. The latest metacat release |
| 266 | 283 |
has been tested most extensively with <a href="http://java.sun.com/j2se/1.5.0/">J2SE 5.0</a> |
| 267 | 284 |
and this is the recommended version. |
| 268 | 285 |
Make sure that JAVA_HOME environment variable is properly set and that both |
| 269 | 286 |
java and javac are on your PATH. |
| 270 | 287 |
</p> |
| 271 |
<p class="header">Oracle 8i or Postgres</p> |
|
| 272 |
<p><i>Oracle:</i><br> |
|
| 273 |
The Oracle RDBMS must be installed and running as a daemon on the system. |
|
| 288 |
<a name="AdditionalSoftwareOracle"></a><div class="header2">Oracle 8i</div> |
|
| 289 |
<p>The Oracle RDBMS must be installed and running as a daemon on the system. |
|
| 274 | 290 |
In addition the JDBC listener must be enabled. You can enable it by |
| 275 |
logging in as your Oracle user and typing the following: |
|
| 276 |
<pre>lsnrctl start</pre> |
|
| 277 |
Your instance should have a table space of at least 5 MB (10 MB or higher |
|
| 291 |
logging in as your Oracle user and typing the following:</p> |
|
| 292 |
|
|
| 293 |
<div class="code">lsnrctl start</div> |
|
| 294 |
|
|
| 295 |
<p>Your instance should have a table space of at least 5 MB (10 MB or higher |
|
| 278 | 296 |
recommended). You should also have a username specific to Metacat |
| 279 | 297 |
created and enabled. This user must have most normal permissions |
| 280 | 298 |
including CREATE SESSION, CREATE TABLE, CREATE INDEX, CREATE TRIGGER, |
| 281 | 299 |
EXECUTE PROCEDURE, EXECUTE TYPE, etc. If an action is unexplainably |
| 282 | 300 |
rejected by Metacat it is probably because the user permissions are not |
| 283 |
correctly set. |
|
| 284 |
</p> |
|
| 285 |
<p><i>Postgres:</i><br>
|
|
| 286 |
Postgres can be easily installed on most linux distributions and on
|
|
| 301 |
correctly set.</p>
|
|
| 302 |
|
|
| 303 |
<a name="AdditionalSoftwarePostgreSQL"></a><div class="header2">PostgreSQL</div>
|
|
| 304 |
<p>PostgreSQL can be easily installed on most linux distributions and on
|
|
| 287 | 305 |
Windows (using cygwin) and Mac OS X. Using Fedora Core or RedHat Linux, |
| 288 |
you can install the rpms for postgres and then run |
|
| 289 |
<code>/etc/init.d/postgresql start</code> in order to start the database. |
|
| 306 |
you can install the rpms for postgres and then run </p> |
|
| 307 |
|
|
| 308 |
<div class="code">/etc/init.d/postgresql start</div> |
|
| 309 |
|
|
| 310 |
<p>in order to start the database. |
|
| 290 | 311 |
On Ubuntu and other Debian-based Linux distributions, you can use the apt-get command |
| 291 | 312 |
to install postgres: <code>sudo apt-get install postgresql-8.0</code> and |
| 292 | 313 |
then run <code>/etc/init.d/postgresql-8.0 start</code> to start. |
| ... | ... | |
| 319 | 340 |
<code>psql -U metacat -W -h localhost metacat</code></li> |
| 320 | 341 |
</ul> |
| 321 | 342 |
</p> |
| 322 |
<p class="header">Ant</p> |
|
| 343 |
|
|
| 344 |
<a name="AdditionalSoftwareAnt"></a><div class="header2">Ant</div> |
|
| 323 | 345 |
<p> |
| 324 | 346 |
Ant is a Java based build application similar to Make on UNIX systems. |
| 325 | 347 |
It takes in installation parameters from a file in the root installation |
| ... | ... | |
| 331 | 353 |
not working with Ant 1.6.x, so you'll need to use an earler version. We have |
| 332 | 354 |
successfully used Ant 1.5.1, 1.5.2, and some earlier versions. --> |
| 333 | 355 |
</p> |
| 334 |
<p class="header">Tomcat</p> |
|
| 356 |
|
|
| 357 |
<a name="AdditionalSoftwareTomcat"></a><div class="header2">Tomcat</div> |
|
| 335 | 358 |
<p> |
| 336 | 359 |
Install Tomcat into the directory of your choice. The directory in which |
| 337 | 360 |
you install Tomcat itself will be referred to as the "$CATALINA_HOME". |
| 338 | 361 |
We recommend that you install Tomcat version 5.5. More details about |
| 339 | 362 |
Tomcat installation are available <a href=" http://jakarta.apache.org/tomcat/index.html">here</a>. |
| 340 | 363 |
</p> |
| 341 |
</td> |
|
| 342 |
</tr> |
|
| 343 |
</table> |
|
| 344 | 364 |
|
| 345 |
<table class="tabledefault" width="100%"> |
|
| 346 |
<td class="tablehead" colspan="2"><p><a name="Installing Metacat"><h2>Installing Metacat</h2></p></td> |
|
| 347 |
<tr> |
|
| 348 |
<td> |
|
| 365 |
<a name="InstallingMetacat"></a><div class="header1">Installing Metacat</div> |
|
| 349 | 366 |
<a name="protocol"></a> |
| 350 | 367 |
<p>This section is only for a fresh installation. If you are upgrading an existing Metacat, please skip |
| 351 |
this section and go to the next one - <a HREF="metacatinstall.html#Upgrade">Upgrading Existing Metacat</a>
|
|
| 368 |
this section and go to the next one - <a href="metacatinstall.html#Upgrade">Upgrading Existing Metacat</a>
|
|
| 352 | 369 |
|
| 353 |
<h3>Download Metacat application</h3> |
|
| 370 |
<a name="InstallDownloadMetacat"></a><div class="header2">Download Metacat Application</div> |
|
| 371 |
<p>Browse to the |
|
| 372 |
<a href="http://knb.ecoinformatics.org/software/download.html">KNB Software Download Page</a>. |
|
| 373 |
In the Metacat section, select the link that looks like:</p> |
|
| 374 |
<div class="code">metacat-bin-X.X.X.tar.gz</div> |
|
| 375 |
<p>where X.X.X is the latest version of Metacat. Choose to save the file locally.</p> |
|
| 376 |
<p>Extract the Metacat package files by typing:</p> |
|
| 377 |
<div class="code">tar -xvzf metacat-bin-X.X.X.tar.gz</div> |
|
| 378 |
<p>You should see a war file and several supporting files. The location where these files |
|
| 379 |
were extracted will be refered to as the the <metacat_package_dir> for the remainder |
|
| 380 |
of this documentation. |
|
| 381 |
|
|
| 382 |
<a name="InstallMetacatWar"></a><div class="header2">Install Metacat War</div> |
|
| 383 |
<p>Copy the war file to Tomcat:</p> |
|
| 384 |
<div class="code">sudo cp knb.war /usr/share/tomcat5.5/webapps</div> |
|
| 385 |
<p>Restart Tomcat:</p> |
|
| 386 |
<div class="code">sudo /etc/init.d/tomcat5.5 restart</div> |
|
| 354 | 387 |
|
| 355 |
<p>First <a href="/software/download.html">download metacat-1.9.0.tar.gz</a> from this site.</p><br> |
|
| 388 |
<a name="InstallRestartTomcat"></a><div class="header2">Restart Tomcat</div> |
|
| 389 |
<p>Once you have successfully installed Metacat, there is one more step. Tomcat |
|
| 390 |
(and Apache if you have Tomcat integrated with it) must be restarted. To do |
|
| 391 |
this, login as the user that runs your tomcat server (often "tomcat"), |
|
| 392 |
go to $CATALINA_HOME/bin and type: </p> |
|
| 393 |
|
|
| 394 |
<div class="code">./shutdown.sh</div> |
|
| 395 |
<div class="code">./startup.sh</div> |
|
| 396 |
|
|
| 397 |
<p>In the Tomcat startup messages you should see something in the log file like:</p> |
|
| 398 |
|
|
| 399 |
<div class="code">Metacat: [WARN]: Metacat (1.9.0) initialized. [edu.ucsb.nceas.metacat.MetaCatServlet]</div> |
|
| 356 | 400 |
|
| 357 |
<p>Extract the contents of the tar file in Linux/Mac by typing: </p> |
|
| 358 |
<pre> |
|
| 359 |
<b> |
|
| 360 |
tar-xvzf metacat-1.9.0.tar.gz |
|
| 361 |
</b> |
|
| 362 |
</pre> |
|
| 363 |
|
|
| 364 |
<h3>Copy war file to Tomcat application directory</h3> |
|
| 401 |
<p>If you see that message Tomcat has successfully loaded the Metacat servlet. |
|
| 402 |
Next, try to run your new servlet. Go to a web browser and type:</p> |
|
| 403 |
|
|
| 404 |
<div class="code">http://yourserver.yourdomain.com/yourcontext/</div> |
|
| 405 |
|
|
| 406 |
<p>You should substitute your context name for "yourcontext" in the url above. |
|
| 407 |
If everything is working correctly, you should see a Metacat configuration screen. Note that if you do not have Tomcat integrated with |
|
| 408 |
Apache you will probably have to type:</p> |
|
| 409 |
|
|
| 410 |
<div class="code">http://yourserver.yourdomain.com:8080/yourcontext/</div> |
|
| 365 | 411 |
|
| 366 |
<p>Copy knb.war to $CATALINA_HOME/webapps</p> |
|
| 367 |
<p>If desired, you can rename the war file to <yourcontext>.war</p> |
|
| 368 |
|
|
| 369 |
<h3>Create Metacat directory</h3> |
|
| 412 |
<a name="InstallTroubleshooting"></a><div class="header2">Troubleshooting</div> |
|
| 413 |
<p>If you see something like:</p> |
|
| 370 | 414 |
|
| 371 |
<p>Create the Metacat storage directory:</p> |
|
| 372 |
<pre> |
|
| 373 |
<b> |
|
| 374 |
mkdir /var/metacat |
|
| 375 |
</b> |
|
| 376 |
</pre> |
|
| 415 |
<div class="code">java.lang.InternalError: Can't connect to X11 window server using 'yourservanme:0.0' as the value of the DISPLAY variable.</div> |
|
| 377 | 416 |
|
| 378 |
<p>Change the ownership of the Metacat storage directory to be the user that runs Tomcat: |
|
| 379 |
<pre> |
|
| 380 |
<b> |
|
| 381 |
chown tomcat:tomcat /var/metacat |
|
| 382 |
</b> |
|
| 383 |
</pre></p> |
|
| 384 |
|
|
| 385 |
<h3>Restart Tomcat</h3> |
|
| 386 |
<p> |
|
| 387 |
Once you have successfully installed Metacat, there is one more step. Tomcat |
|
| 388 |
(and Apache if you have Tomcat integrated with it) must be restarted. To do |
|
| 389 |
this, login as the user that runs your tomcat server (often "tomcat"), |
|
| 390 |
go to $CATALINA_HOME/bin and type: |
|
| 391 |
<pre> |
|
| 392 |
<b> |
|
| 393 |
./shutdown.sh |
|
| 394 |
./startup.sh |
|
| 395 |
</b> |
|
| 396 |
</pre> |
|
| 397 |
In the Tomcat startup messages you should see something in the log file like: |
|
| 398 |
<pre> |
|
| 399 |
Metacat: [WARN]: Metacat (1.8.1) initialized. [edu.ucsb.nceas.metacat.MetaCatServlet] |
|
| 400 |
</pre> |
|
| 401 |
If you see that message Tomcat is successfully loading the Metacat servlet. |
|
| 402 |
Next, try to run your new servlet. Go to a web browser and type: |
|
| 403 |
<pre> |
|
| 404 |
http://yourserver.yourdomain.com/yourcontext/ |
|
| 405 |
</pre> |
|
| 406 |
You should substitute your context name for "yourcontext" in the url above. |
|
| 407 |
If everything is working correctly, you should see a Metacat configuration screen. Note that if you do not have Tomcat integrated with |
|
| 408 |
Apache you will probably have to type |
|
| 409 |
<pre> |
|
| 410 |
http://yourserver.yourdomain.com:8080/yourcontext/ |
|
| 411 |
</pre> |
|
| 412 |
</p> |
|
| 413 |
<p><b>Troubleshooting</b>: If you see something like java.lang.InternalError: |
|
| 414 |
Can't connect to X11 window server using 'yourservanme:0.0' as the value of the DISPLAY variable. |
|
| 415 |
<p>You should add this line: |
|
| 416 |
<b>JAVA_OPTS="-Djava.awt.headless=true $JAVA_OPTS"</b> at the first line of |
|
| 417 |
catalina.sh file in tomcat bin directory. The reason is that GeoServer uses X11 windows to draw graphics. |
|
| 418 |
</p> |
|
| 417 |
<p>You should add this line: </p> |
|
| 419 | 418 |
|
| 420 |
<h3>Configure Metacat</h3> |
|
| 421 |
<p> |
|
| 422 |
Once you see the Metacat configuration screen, you can follow the instructions in the |
|
| 419 |
<div class="code">JAVA_OPTS="-Djava.awt.headless=true $JAVA_OPTS"</div> |
|
| 420 |
|
|
| 421 |
<p>at the first line of the catalina.sh file in tomcat bin directory. The reason is that |
|
| 422 |
GeoServer uses X11 windows to draw graphics.</p> |
|
| 423 |
|
|
| 424 |
<a name="InstallConfigureMetacat"></a><div class="header2">Configure Metacat</div> |
|
| 425 |
<p>Once you see the Metacat configuration screen, you can follow the instructions in the |
|
| 423 | 426 |
<a href="./metacatconfigure.html"> Configuring Metacat Section</a> |
| 424 |
to complete the internal configuration of Metacat. |
|
| 425 |
</p> |
|
| 426 |
|
|
| 427 |
<h3>Deploy wsdl file (Only for EarthGrid-enabled Metacat installation) </h3> |
|
| 428 |
<p> |
|
| 429 |
Once Tomcat is running successfully, there is another step for EarthGrid-enabled Metacat installation. |
|
| 430 |
In metacat directory, type: |
|
| 431 |
<pre><b>ant deploy-ecogrid</b></pre> |
|
| 432 |
It will generate wsdl files for EarthGrid services. |
|
| 433 |
</p> |
|
| 427 |
to complete the internal configuration of Metacat.</p> |
|
| 434 | 428 |
|
| 435 |
</td> |
|
| 436 |
</tr> |
|
| 437 |
</table> |
|
| 438 |
|
|
| 439 |
<table class="tabledefault" width="100%"> |
|
| 440 |
<td class="tablehead" colspan="2"><p><a name="Upgrade"><h2>Compilation and Upgrading Existing Metacat</h2></p></td> |
|
| 441 |
<tr> |
|
| 442 |
<td> |
|
| 429 |
<a name="UpgradingMetacat"></a><div class="header1">Upgrading Existing Metacat</div> |
|
| 443 | 430 |
<a name="protocol"></a> |
| 444 | 431 |
<p>The following instructions are for upgrading an existing Metacat. |
| 445 |
<p><h3>Stop the running Metacat</h3> |
|
| 446 |
<P>To do this, login as the user that runs your tomcat server (often "tomcat"), |
|
| 447 |
go to $CATALINA_HOME/bin and type: |
|
| 448 |
<pre><b>./shutdown.sh</b> </pre> |
|
| 449 |
<p> |
|
| 450 |
<h3>Run Ant Build</h3> |
|
| 451 |
<p> |
|
| 452 |
Ant allows compilation and upgrading to be done in one step. |
|
| 453 |
Change into the metacat directory and type: |
|
| 454 |
<pre><b>ant clean upgrade</b></pre> |
|
| 455 |
<p> |
|
| 456 |
You should see a bunch of messages telling you the progress of compilation |
|
| 457 |
and installation. When it is done you should see the message |
|
| 458 |
BUILD SUCCESSFUL |
|
| 459 |
and you should be returned to a UNIX command prompt. If you do not see |
|
| 460 |
the message BUILD SUCCESSFUL then there was an error that you need to |
|
| 461 |
resolve. |
|
| 462 |
This may come up if you are logged in as a user that does not have write |
|
| 463 |
access to one or more of the directories that are listed in the build.xml |
|
| 464 |
file, or if any of the paths to files are not configured correctly in the |
|
| 465 |
"config" target. |
|
| 466 |
</p> |
|
| 467 |
<p> |
|
| 468 |
Note: The 'data' directories that are indicated in the 'datafilepath' and |
|
| 469 |
'inlinedatafilepath' build properties must be writable |
|
| 470 |
by user account under which Tomcat runs or you will not be able to upload |
|
| 471 |
data files to the system. |
|
| 472 |
</p> |
|
| 473 |
|
|
| 474 |
<p class="header">To install metacat LSID support, adjust the LSID-related |
|
| 475 |
properties in the build.properties files and type: |
|
| 476 |
<p class="header"><b>ant deploy-lsid</b> |
|
| 432 |
|
|
| 433 |
<a name="UpgradeStopMetacat"></a><div class="header2">Stop the Running Metacat</div> |
|
| 434 |
<p>To do this, login as the user that runs your tomcat server (often "tomcat"), |
|
| 435 |
go to $CATALINA_HOME/bin and type:</p> |
|
| 436 |
|
|
| 437 |
<div class="code">./shutdown.sh</div> |
|
| 438 |
|
|
| 439 |
<a name="UpgradeDownloadMetacat"></a><div class="header2">Download Latest Metacat Application</div> |
|
| 440 |
<p>Browse to the |
|
| 441 |
<a href="http://knb.ecoinformatics.org/software/download.html">KNB Software Download Page</a>. |
|
| 442 |
In the Metacat section, select the link that looks like:</p> |
|
| 443 |
<div class="code">metacat-bin-X.X.X.tar.gz</div> |
|
| 444 |
<p>where X.X.X is the latest version of Metacat. Choose to save the file locally.</p> |
|
| 445 |
<p>Extract the Metacat package files by typing:</p> |
|
| 446 |
<div class="code">tar -xvzf metacat-bin-X.X.X.tar.gz</div> |
|
| 447 |
<p>You should see a war file and several supporting files. The location where these files |
|
| 448 |
were extracted will be refered to as the the <metacat_package_dir> for the remainder |
|
| 449 |
of this documentation.</p> |
|
| 477 | 450 |
|
| 478 |
<p><h3>Upgrade SQL Scripts</h3></p> |
|
| 479 |
<P>Note: there is no SQL script that needs to be run when user upgrades the Metacat |
|
| 480 |
from 1.8.0 to 1.8.1 release.</p> |
|
| 481 |
<p> |
|
| 482 |
If you have an existing metacat installation, you should not run the install |
|
| 483 |
script because it will replace all of the older tables with new, empty |
|
| 484 |
copies of the tables. Thus you would lose your data! Instead, you can |
|
| 485 |
run some upgrade scripts that will change the table structure as needed for |
|
| 486 |
the new version. If you are skipping versions, run each upgrade script |
|
| 487 |
for the intermediate versions as well. Currently the upgrade scripts are: |
|
| 488 |
</p> |
|
| 489 |
<ul> |
|
| 490 |
<li>build/src/upgrade-db-to-1.2.sql</li> |
|
| 491 |
<li>build/src/upgrade-db-to-1.3.sql</li> |
|
| 492 |
<li>build/src/upgrade-db-to-1.4.sql</li> |
|
| 493 |
<li>build/src/upgrade-db-to-1.5.sql</li> |
|
| 494 |
<li>build/src/upgrade-db-to-1.6.sql</li> |
|
| 495 |
<li>build/src/upgrade-db-to-1.7.sql</li> |
|
| 496 |
<li>build/src/upgrade-db-to-1.8.sql</li> |
|
| 497 |
</ul> |
|
| 498 |
<p> |
|
| 499 |
For example, if you had an existing metacat 1.5 installation and you were upgrading |
|
| 500 |
to metacat 1.8, you would need to run three scripts in sequence: |
|
| 501 |
upgrade-db-to-1.6.sql, upgrade-db-to-1.7.sql, and upgrade-db-to-1.8.sql. |
|
| 502 |
However, if you were starting from a Metacat 1.7 |
|
| 503 |
installation, you would only need to run the upgrade-db-to-1.8.sql script. |
|
| 504 |
<em>Be sure to use the version of the scripts from the 'build/src' directory: they |
|
| 505 |
are customized for your installation in that directory.</em> |
|
| 506 |
</p> |
|
| 507 |
<p> |
|
| 508 |
Ant targets exist to do the upgrades, so you can also do the above described upgrade by running:<br /> |
|
| 509 |
</p> |
|
| 510 |
<p> |
|
| 511 |
<strong>ant upgrade16</strong><br /> |
|
| 512 |
<strong>ant upgrade17</strong><br /> |
|
| 513 |
<strong>ant upgrade18</strong><br /> |
|
| 514 |
</p> |
|
| 451 |
<a name="UpgradeMetacatWar"></a><div class="header2">Upgrade Metacat War</div> |
|
| 452 |
<p>Copy the war file to Tomcat:</p> |
|
| 453 |
<div class="code">sudo cp knb.war /usr/share/tomcat5.5/webapps</div> |
|
| 454 |
<p>Remove (or rename) the existing application directory:</p> |
|
| 455 |
<div class="code">sudo rm -rf /usr/share/tomcat5.5/webapps/knb</div> |
|
| 456 |
<p> or </p> |
|
| 457 |
<div class="code">sudo mv /usr/share/tomcat5.5/webapps/knb /usr/share/tomcat5.5/webapps/knb.bak</div> |
|
| 458 |
<p>Restart Tomcat:</p> |
|
| 459 |
<div class="code">sudo /etc/init.d/tomcat5.5 restart</div> |
|
| 460 |
|
|
| 461 |
<a name="UpgradeRestartTomcat"></a><div class="header2">Restart Tomcat</div> |
|
| 462 |
<p>Once you have successfully installed Metacat, there is one more step. Tomcat |
|
| 463 |
(and Apache if you have Tomcat integrated with it) must be restarted. To do |
|
| 464 |
this, login as the user that runs your tomcat server (often "tomcat"), |
|
| 465 |
go to $CATALINA_HOME/bin and type: </p> |
|
| 466 |
|
|
| 467 |
<div class="code">./startup.sh</div> |
|
| 468 |
|
|
| 469 |
<p>In the Tomcat startup messages you should see something in the log file like:</p> |
|
| 470 |
|
|
| 471 |
<div class="code">Metacat: [WARN]: Metacat (1.8.0) initialized. [edu.ucsb.nceas.metacat.MetaCatServlet]</div> |
|
| 472 |
|
|
| 473 |
If you see that message Tomcat has successfully loaded the Metacat servlet. |
|
| 474 |
Next, try to run your new servlet. Go to a web browser and type:</p> |
|
| 475 |
|
|
| 476 |
<div class="code">http://yourserver.yourdomain.com/yourcontext/</div> |
|
| 477 |
|
|
| 478 |
<p>You should substitute your context name for "yourcontext" in the url above. |
|
| 479 |
If everything is working correctly, you should see a query page followed |
|
| 480 |
by an empty result set. Note that if you do not have Tomcat integrated with |
|
| 481 |
Apache you will probably have to type</p> |
|
| 482 |
|
|
| 483 |
<div class="code">http://yourserver.yourdomain.com:8080/yourcontext/</div> |
|
| 515 | 484 |
|
| 516 |
</p> |
|
| 517 |
<h3>Restart Tomcat</h3> |
|
| 518 |
<p> |
|
| 519 |
Once you have successfully installed Metacat, there is one more step. Tomcat |
|
| 520 |
(and Apache if you have Tomcat integrated with it) must be restarted. To do |
|
| 521 |
this, login as the user that runs your tomcat server (often "tomcat"), |
|
| 522 |
go to $CATALINA_HOME/bin and type: |
|
| 523 |
<pre> |
|
| 524 |
<b> |
|
| 525 |
./startup.sh |
|
| 526 |
</b> |
|
| 527 |
</pre> |
|
| 528 |
In the Tomcat startup messages you should see something in the log file like: |
|
| 529 |
<pre> |
|
| 530 |
Metacat: [WARN]: Metacat (1.8.0) initialized. [edu.ucsb.nceas.metacat.MetaCatServlet] |
|
| 531 |
</pre> |
|
| 532 |
If you see that message Tomcat is successfully loading the Metacat servlet. |
|
| 533 |
Next, try to run your new servlet. Go to a web browser and type: |
|
| 534 |
<pre>http://yourserver.yourdomain.com/yourcontext/</pre> |
|
| 535 |
You should substitute your context name for "yourcontext" in the url above. |
|
| 536 |
If everything is working correctly, you should see a query page followed |
|
| 537 |
by an empty result set. Note that if you do not have Tomcat integrated with |
|
| 538 |
Apache you will probably have to type |
|
| 539 |
<pre>http://yourserver.yourdomain.com:8080/yourcontext/</pre> |
|
| 540 |
</p> |
|
| 541 |
<p><b>Troubleshooting</b>: If you see something like java.lang.InternalError: |
|
| 542 |
Can't connect to X11 window server using 'yourservanme:0.0' as the value of the DISPLAY variable. |
|
| 543 |
<p>You should add this line: |
|
| 544 |
<b>JAVA_OPTS="-Djava.awt.headless=true $JAVA_OPTS"</b> at the first line of |
|
| 545 |
catalina.sh file in tomcat bin directory. The reason is that GeoServer uses X11 windows to draw graphics. |
|
| 546 |
</p> |
|
| 485 |
<a name="UpgradeTroubleshooting"></a><div class="header2">Troubleshooting</div> |
|
| 486 |
<p>If you see something like: |
|
| 547 | 487 |
|
| 548 |
<h3>Deploy wsdl file (Only for EarthGrid-enabled Metacat installation) </h3> |
|
| 549 |
<p> |
|
| 550 |
Once Tomcat is running successfully, there is another step for EarthGrid-enabled Metacat installation. |
|
| 551 |
In metacat directory, type: |
|
| 552 |
<pre><b>ant deploy-ecogrid</b></pre> |
|
| 553 |
It will generate wsdl files for EarthGrid services. |
|
| 554 |
</p> |
|
| 488 |
<div class="code">java.lang.InternalError: Can't connect to X11 window server using 'yourservanme:0.0' as the value of the DISPLAY variable.</div> |
|
| 489 |
|
|
| 490 |
<p>You should add this line: </p> |
|
| 491 |
|
|
| 492 |
<div class="code">JAVA_OPTS="-Djava.awt.headless=true $JAVA_OPTS"</div> |
|
| 493 |
<p>at the first line of the catalina.sh file in the tomcat bin directory. The reason is that |
|
| 494 |
GeoServer uses X11 windows to draw graphics.</p> |
|
| 495 |
|
|
| 496 |
<a name="UpgradeConfigureMetacat"></a><div class="header2">Configure Metacat</div> |
|
| 497 |
<p>Once you see the Metacat configuration screen, you can follow the instructions in the |
|
| 498 |
<a href="./metacatconfigure.html"> Configuring Metacat Section</a> |
|
| 499 |
to complete the internal configuration of Metacat.</p> |
|
| 555 | 500 |
|
| 556 |
</td> |
|
| 557 |
</tr> |
|
| 558 |
</table> |
|
| 559 |
|
|
| 560 |
<table class="tabledefault" width="100%"> |
|
| 561 |
<td class="tablehead" colspan="2"><a name="Registry"><h2>Web-based Registry for Metacat</h2></td> |
|
| 562 |
<tr> |
|
| 563 |
<td> |
|
| 564 |
<p>The registry allows users to upload simple metadata documents directly from the web. See the separate |
|
| 565 |
<a href="registry_installation.html">Registry Installation Guide</a>.</p><br /><br /> |
|
| 566 |
</td> |
|
| 501 |
<a name="Registry"></a><div class="header1">Web Based Registry</div> |
|
| 502 |
<p>The registry allows users to upload simple metadata documents directly from the web. See the separate |
|
| 503 |
<a href="registry_installation.html">Registry Installation Guide</a>.</p><br/><br/> |
|
| 567 | 504 |
</body> |
| 568 | 505 |
</html> |
Also available in: Unified diff
Updated existing installation instructions to be more inline with binary install instructions.