Revision 988
Added by Jing Tao over 22 years ago
| metacatinstall.html | ||
|---|---|---|
| 209 | 209 |
</p> |
| 210 | 210 |
<p> |
| 211 | 211 |
The properties that you need to change will include jdbc-connect, |
| 212 |
dbDriver, dbAdapter, oracle_home, jdbc, tomcat, webapps, context, |
|
| 213 |
user, password, server, web-base-url, and default-style. |
|
| 214 |
Each is described in detail below. You should also verify that the |
|
| 215 |
jar file properties mentioned in the remainder of the config target are |
|
| 216 |
accessible at the paths listed -- the defaults will usually work. |
|
| 212 |
dbDriver, dbAdapter, oracle_home, |
|
| 213 |
jdbc, tomcat, webapps, contex, user, server, systemidserver, |
|
| 214 |
web-base-url, and default-style. Each is described in detail below. |
|
| 215 |
You should also verify that the jar file properties mentioned in the |
|
| 216 |
remainder of the config target are accessible at the paths listed -- the |
|
| 217 |
defaults will usually work. |
|
| 217 | 218 |
</p> |
| 218 | 219 |
Properties you will likely need to change:<br /> |
| 219 | 220 |
<ul> |
| ... | ... | |
| 260 | 261 |
<li> |
| 261 | 262 |
The server is the http address on which Metacat is running. |
| 262 | 263 |
</li> |
| 264 |
</li> |
|
| 263 | 265 |
<li> |
| 266 |
The systemidserver is the protocol (http or https) and server location to get |
|
| 267 |
DTD file. |
|
| 268 |
</li> |
|
| 269 |
<li> |
|
| 264 | 270 |
The user and password parmaters are the database user name that you set up |
| 265 | 271 |
to use Metacat, for example an Oracle username and password. |
| 266 | 272 |
</li> |
| ... | ... | |
| 289 | 295 |
<li> |
| 290 | 296 |
The servlet path is the relative path to your servlet as viewed by the |
| 291 | 297 |
Tomcat or Apache web server. Under Tomcat, the form is usually |
| 292 |
<pre>/<servlet-context-name>/servlet/<servlet-name></pre> |
|
| 293 |
In the example above "metadata" is the name of the servlet context and |
|
| 294 |
"metacat" is the name of the servlet. |
|
| 298 |
<pre>/<servlet-context-name>/servlet/metacat</pre> |
|
| 295 | 299 |
</li> |
| 296 | 300 |
<li> |
| 297 | 301 |
The html-path is usually the first directory of the servlet-path. The only |
| ... | ... | |
| 370 | 374 |
<td> |
| 371 | 375 |
<a name="protocol"></a> |
| 372 | 376 |
<p> |
| 373 |
Now we are ready to finish setting up Tomcat by creating the protocol.jar |
|
| 374 |
file. To do this, change into the xmltodb directory and type |
|
| 375 |
<pre>ant protocol</pre> |
|
| 376 |
When it is done and says "BUILD SUCCESSFUL", change into the 'build' |
|
| 377 |
directory. There will be a file there called 'protocol.jar'. Now, copy |
|
| 378 |
that file to $TOMCAT_HOME/lib/protocol.jar. In our case: |
|
| 379 |
<pre>cp protocol.jar /usr/local/devtools/jakarta-tomcat/lib/.</pre> |
|
| 380 |
<div class="emphasis">Note that once you have installed the protocol handlers |
|
| 381 |
you do not need to install them again. You can recompile Metacat and install |
|
| 382 |
it without having to go through this process again.</div> |
|
| 377 |
Now we are ready to finish setting up Tomcat by getting DTD file from CVS. |
|
| 378 |
To do this, change into the xmltodb directory and type |
|
| 379 |
<pre>ant getdtd</pre> |
|
| 380 |
When it is done and says "BUILD SUCCESSFUL", the DTD files in CVS server will |
|
| 381 |
copy to xmltodb/lib/dtd directory. |
|
| 383 | 382 |
</p> |
| 384 | 383 |
<p> |
| 385 |
Once the protocol.jar file is compiled and copied, you are ready to compile
|
|
| 384 |
Once the DTD files are copied, you are ready to compile
|
|
| 386 | 385 |
and install |
| 387 | 386 |
Metacat. Ant allows compilation and installation to be done in one step. |
| 388 | 387 |
Change into the xmltodb directory and type: |
Also available in: Unified diff
Update the install instruction.