Installing Practical Map Server


Introduction

This document describes the basic installation process required to run PMS as a web application.

Prerequisites

Before proceeding with this document, you need to have done the following:

  1. Installed and configured a Servlet container such as Apache Tomcat.
  2. Installed and configured Oracle 8.1.6 or higher (note that this is not a hard requirement to use PMS, but is currently necessary to run a standard build without modification).
  3. Built PMS from the source distribution.

Deploying the web application

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:

  1. copy or create a symbolic link from the PMS build (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..
  2. Add an entry to the 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.

Configuring the web application

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.

Configuring the log system

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.


Last modified: $Id: configure.html,v 1.1 2001/06/24 21:11:58 karl Exp $