Revision 989
Added by berkley over 22 years ago
metacatinstall.html | ||
---|---|---|
147 | 147 |
servlet context will depend on where you install the tomcat webapps |
148 | 148 |
directory.</div> |
149 | 149 |
</p> |
150 |
<p> |
|
151 |
After setting up Tomcat, you must make a slight modification to the startup |
|
152 |
script. Tomcat needs to know about special protocol handlers that Metacat |
|
153 |
uses for its URLs. Find the line in the tomcat.sh file that says |
|
154 |
<pre> |
|
155 |
if [ "$TOMCAT_OPTS" = "" ] ; then |
|
156 |
TOMCAT_OPTS="" |
|
157 |
fi |
|
158 |
</pre> |
|
159 |
It should be on about line 65. You need to comment out the TOMCAT_OPTS |
|
160 |
entry that is there and add the following: |
|
161 |
<pre> |
|
162 |
TOMCAT_OPTS="-Djava.protocol.handler.pkgs=edu.ucsb.nceas.protocols" |
|
163 |
</pre> |
|
164 |
When you are done the if statement should look like: |
|
165 |
<pre> |
|
166 |
if [ "$TOMCAT_OPTS" = "" ] ; then |
|
167 |
#TOMCAT_OPTS="" |
|
168 |
TOMCAT_OPTS="-Djava.protocol.handler.pkgs=edu.ucsb.nceas.protocols" |
|
169 |
fi |
|
170 |
</pre> |
|
171 |
You must also complete the <a href="#protocol">protocol.jar</a> step below |
|
172 |
for this to be completely |
|
173 |
setup. Also, make sure that this startup script is always used to start |
|
174 |
tomcat or the parameter will not be set correctly and some features of |
|
175 |
Metacat will not work. |
|
176 |
</p> |
|
177 |
<p> |
|
178 |
Your servlet context should now be setup. The next step is giving Tomcat |
|
179 |
something to run in that context (i.e. Metacat). |
|
180 |
</p> |
|
181 | 150 |
</td> |
182 | 151 |
</tr> |
183 | 152 |
</table> |
... | ... | |
204 | 173 |
to change a number of configuration properties to match the setup on |
205 | 174 |
your system. If you are using oracle, you'll need to customize the |
206 | 175 |
properties in the "oracle" target. If you are using Postgres, you'll |
207 |
need to customize the properties inthe "postgres" target. All users |
|
176 |
need to customize the properties in the "postgres" target. All users
|
|
208 | 177 |
will need to customize the properties in the "config" target. |
209 | 178 |
</p> |
210 | 179 |
<p> |
211 | 180 |
The properties that you need to change will include jdbc-connect, |
212 | 181 |
dbDriver, dbAdapter, oracle_home, |
213 |
jdbc, tomcat, webapps, contex, user, server, systemidserver, |
|
182 |
jdbc, tomcat, webapps, context, user, server, systemidserver,
|
|
214 | 183 |
web-base-url, and default-style. Each is described in detail below. |
215 | 184 |
You should also verify that the jar file properties mentioned in the |
216 | 185 |
remainder of the config target are accessible at the paths listed -- the |
217 | 186 |
defaults will usually work. |
218 | 187 |
</p> |
188 |
<p> |
|
189 |
Note that the build file is preconfigured to install Metacat either using |
|
190 |
Oracle or PostgreSQL as a backend database. To change the database |
|
191 |
system, simply change the 'depends' attribute of the 'config' target to be |
|
192 |
the name of the database target that you wish to use (either 'oracle' or |
|
193 |
'postgresql'). If you wish to use a different database system, add a new |
|
194 |
target for your database with the needed parameters and actions then add it |
|
195 |
to the 'depends' attribute. |
|
196 |
</p> |
|
219 | 197 |
Properties you will likely need to change:<br /> |
220 | 198 |
<ul> |
221 | 199 |
<li> |
... | ... | |
224 | 202 |
</li> |
225 | 203 |
<li> |
226 | 204 |
The dbDriver parameter is the name of the JDBC driver class to use for |
227 |
connections to your database. If you are not using Oracle, you will also |
|
228 |
need to change the name of the database adapter class in the dbAdapter |
|
229 |
property in the <a href="./properties.html"?>metacat.properties</a> file. |
|
205 |
connections to your database. |
|
230 | 206 |
</li> |
231 | 207 |
<li> |
232 | 208 |
The dbAdapter parameter is the name of the Metacat adapter class to be used |
233 | 209 |
to communicate with a particular database. |
234 |
If you are not using Oracle, you will need to change this. There are |
|
235 |
currently adapters for Oracle, Postgres, and MS SQL Server. |
|
236 | 210 |
</li> |
237 | 211 |
<li> |
238 | 212 |
The oracle_home parameter is the location that oracle is installed on |
... | ... | |
259 | 233 |
or supplementary images. |
260 | 234 |
</li> |
261 | 235 |
<li> |
262 |
The server is the http address on which Metacat is running. |
|
236 |
Server is the http address on which Metacat is running (note that you should |
|
237 |
not include the 'http://' in the server property. |
|
263 | 238 |
</li> |
264 | 239 |
</li> |
265 | 240 |
<li> |
266 | 241 |
The systemidserver is the protocol (http or https) and server location to get |
267 |
DTD file.
|
|
242 |
any DTDs.
|
|
268 | 243 |
</li> |
269 | 244 |
<li> |
270 |
The user and password parmaters are the database user name that you set up
|
|
245 |
The user and password parameters are the database user name that you set up
|
|
271 | 246 |
to use Metacat, for example an Oracle username and password. |
272 | 247 |
</li> |
273 | 248 |
<li> |
... | ... | |
285 | 260 |
<ul> |
286 | 261 |
<li> |
287 | 262 |
The installdir |
288 |
parameter is the directory that you want Ant to install the servlet to.
|
|
263 |
parameter is the directory in which Ant should install the servlet.
|
|
289 | 264 |
It is your "servlet context path" that was defined above. |
290 | 265 |
</li> |
291 | 266 |
<li> |
292 | 267 |
Replication path is the relative path to the replication servlet. This |
293 |
should be the name of your servlet followed by "/servlet/replication". |
|
268 |
should be the name of your servlet followed by "/servlet/replication". For |
|
269 |
example 'metacat/servlet/replication'. |
|
294 | 270 |
</li> |
295 | 271 |
<li> |
296 | 272 |
The servlet path is the relative path to your servlet as viewed by the |
Also available in: Unified diff
updated for 1.1.0