This document describes the basic installation process required to run PMS as a web application.
Before proceeding with this document, you need to have done the following:
The first task is to deploy PMS within your Servlet container. The deployment method varies with the Servlet container. For Tomcat you have two options:
build/pms
) to the webapps
directory in your Tomcat installation. This will
deploy the map server under the URL /pms
, relative
to the server root..
server.xml
configuration
file in the conf
directory in your Tomcat
installation:
<Context path="/pms"
docBase="path/to/build/pms"
crossContext="true"
debug="1"
reloadable="true"
trusted="false" >
</Context>
The path
attribute specifies the URL to the map
server, relative to PMS. The docBase
attribute
specifies the file system path to the web application, in this
case the directory where PMS was built. See the Tomcat documentation
for more details.
The next task is to edit the web application deployment descriptor
for PMS. This is an XML document named web.xml
, located
in the WEB-INF
directory of the web application.
The deployment descriptor contains three parameters for configuring access to Oracle via JDBC. Edit these parameters to match your Oracle configuration.
PMS uses Log4J to
log requests, errors and diagnostic messages to a rolling log file.
The log system is configured with a properties file named
log4j.properties
in the WEB-INF
directory of
the web application.
Edit the File
property to the desired path of the log
file. The application will roll the logs on a daily basis,
accumulating files from previous days in the same directory.