| 1 |
3032
|
perry
|
<h2>Installing for J2EE</h2>
|
| 2 |
|
|
|
| 3 |
|
|
<p>
|
| 4 |
|
|
You should first have your J2EE servlet container installed.
|
| 5 |
|
|
The <a href="http://jakarta.apache.org/tomcat/index.html">Tomcat</a>
|
| 6 |
|
|
servlet container is known to work well for Mapbuilder, as well as
|
| 7 |
|
|
other related applications such as GeoServer.
|
| 8 |
|
|
</p>
|
| 9 |
|
|
|
| 10 |
|
|
<p>
|
| 11 |
|
|
Download the -war.zip archive and extract mapbuilder.war file to
|
| 12 |
|
|
the tomcat webapps directory.
|
| 13 |
|
|
Depending on your Tomcat setup, you may or may not have to restart Tomcat.
|
| 14 |
|
|
The default tomcat installation will expand the .war file automatically.
|
| 15 |
|
|
Installation details for other servlet containers may vary.
|
| 16 |
|
|
</p>
|
| 17 |
|
|
|
| 18 |
|
|
<p>
|
| 19 |
|
|
The required server side scripts are automatically available as servlets,
|
| 20 |
|
|
and configured in /mapbuilder/WEB-INF/web.xml.
|
| 21 |
|
|
By default, these are: /mapbuilder/proxy for the proxyUrl and
|
| 22 |
|
|
/mapbuilder/writeXml for the serializeUrl config property.
|
| 23 |
|
|
If you install Mpabuilder using a different context name, it will be
|
| 24 |
|
|
automatically detected.
|
| 25 |
|
|
</p>
|
| 26 |
|
|
|
| 27 |
|
|
<p>
|
| 28 |
|
|
Other aspects of the Tomcat setup (where $catalina_home refers to you base
|
| 29 |
|
|
directory for the servlet container):
|
| 30 |
|
|
</p>
|
| 31 |
|
|
|
| 32 |
|
|
<dl class="med">
|
| 33 |
|
|
<dt class="title">Logging:</dt>
|
| 34 |
|
|
<dd>
|
| 35 |
|
|
The server scripts use the Log4J logging package which is configured by
|
| 36 |
|
|
the file $catalina_home/webapps/mapbuilder/WEB-INF/classes/log4j.properties.
|
| 37 |
|
|
By default, logging level is set to INFO and by default there will be
|
| 38 |
|
|
a log file at $catalina_home/logs/mapbuilder-log4j.log.
|
| 39 |
|
|
Please refer to <a href="http://logging.apache.org/log4j/docs/">Log4J
|
| 40 |
|
|
documentation</a> for more details on how to configure
|
| 41 |
|
|
the logging facility.
|
| 42 |
|
|
<dd>
|
| 43 |
|
|
<dt class="title">File save directory:</dt>
|
| 44 |
|
|
<dd>
|
| 45 |
|
|
The file save directory is where files are written to disk by the serialize
|
| 46 |
|
|
script.
|
| 47 |
|
|
This directory has to be writable by the web user and it is up to the
|
| 48 |
|
|
application to purge it.
|
| 49 |
|
|
The location of the directory is configured in the Mapbuilder context
|
| 50 |
|
|
deployment decriptor at $catalina_home/webapps/mapbuilder/WEB-INF/web.xml
|
| 51 |
|
|
and defaults to $catalina_home/webapps/mapbuilder/temp.
|
| 52 |
|
|
</dd>
|
| 53 |
|
|
</dl>
|
| 54 |
|
|
|
| 55 |
|
|
<p>
|
| 56 |
|
|
more ?
|
| 57 |
|
|
</p>
|