DCMMS Administration Guide

A "\" at the end of the line in program listings means that the line continues in the next line.

This document uses Unified Modeling Language (UML) diagrams to illustrate various aspects of the DCMMS application.

For those not familiar with the UML symbology, Figure 1.1, “UML Legend” provides a basic UML legend.

Figure 1.1. UML Legend

The DCMMS application can be installed in a stand-alone setup or in a client-server environment.

Figure 1.2. Stand-Alone Deployment

Figure 1.3. Client-Server Deployment

Caution

The DCMMS application is meant to run in an intranet environment. If you want to use the application over the internet you should protect it by a proper firewall and/or VPN setup. To run the application directly on an internet server would require a complete security audit of the application code. Regardless of the type of installation, it is important that the administrator stays up-to-date with the latest Apache, PostgreSQL, Windows and PHP releases to avoid security leaks.

Figure 1.4. Internet Deployment

In addition to the outlined approach it might be possible to run a DCMMS on server on the internet if it is hardened with SSL and additional access control on the Apache side (E.g. client-side certificates).

A PC with at least 256 MB RAM and at least 1 GHz CPU speed.

The actual hardware requirements might be higher depending on the size and nature of the map data as well as the number of concurrent users.

To print the workorders, a printer with at least 300dpi resolution is required.

	Tip
	Call-center grade headphones are strongly recommended in order to receive customer complaint calls.

	Tip
	An optical mouse is recommended for all DCMMS clients.

The following software packages are required to run the DCMMS application:

Section 2.1, “Installation”covers the installation of all required software packages.

If it is intended to use the Arabic interface of the DCMMS application, the PostArabic software package is required in addition.

1.3.2.1. Operating System

	Caution
	While it might be possible to install the DCMMS server on other Windows flavors, only Windows 2003 Server and Windows XP are recommended. The filesystem of c: must be NTFS and not FAT.

Windows XP,2000 installations have been tested and should work. Windows NT, 95, 98 are ME not recommended.

Installation of DCMMS on other operating systems such as Linux may require minor changes to the source code. Please contact the DCMMS developers if you are having problems. The initial DCMMS version was created on Linux.

On Windows, the following folders contain files that belong to the standard DCMMS installation:

+ c:
| 
+--+ ms4w	
|  |
|  +--+ Apache
|  |  |
|  |  +--- conf
|  |  |
|  |  +--- logs
|  |
|  +--+ apps
|  |  |
|  |  +--+ dmms
|  |     |
|  |     +--- conf
|  |     |
|  |     +--- data
|  |     |
|  |     +--- htdocs
|  |     |
|  |     +--- include
|  |     |
|  |     +--- plugin
|  |
|  +--+ httpd.d
|  |
|  +--+ tmp 
|     |
|     +--- ms_tmp
|  
+--+ Program Files
|   |
|   +--+ PostgreSQL
|      |
|      +--+ 8.3
|         |
|         +--- data
|
+--+ windows
   |
   +--- fonts

	Note
	Note that your actual folder structure might be different, e.g. when you use a Non-English version of Windows XP. Use the structure above as a reference when you're not sure where to install things.

	Tip
	If you are installing manually, you should install the software to the above mentioned folders.

The PostgreSQL folder holds the PostgreSQL installation, the Apache2 folder the Apache webserver and the php folder the PHP installation. The tmp folder holds temporary files (e.g. PHP session information) and the ms_tmp folder contains temporary map files created by mapserver.

For most of the software packages these folders are the default on a system with an English version of the Windows operating system. The folders will be created during the installation process described below.

c:\ms4w\apps\dcmms\config contains all configuration files with the exception of c:\ms4w\apps\dcmms\include\dcmconfig.php.

c:\ms4w\apps\dcmms\doc contains the documentation in various formats: CHM, DocBook XML, HTML, PDF.

c:\ms4w\apps\dcmms\data contains GIS data (shape files) used by the application. However this location is not fixed and may be overridden in the map file.

c:\ms4w\apps\dcmms\plugin contains application plug-ins (extensions that extend the functionality).

Basic computer knowledge together with this guide should be sufficient to administer a stand-alone installation.

Any administrator will benefit from knowledge in SQL, PostgreSQL, the Windows command line interface (cmd.exe), Windows user administration, Windows services, GIS (e.g. ArcView), mailing lists - however such knowledge is not a requirement.

Various support possibilities are available to support new administrators (See Section 2.8.2, “Support Tracker”, Section 2.8.1, “DCMMS Info Mailing List”).

This section introduces Windows services.

Apache and PostgreSQL run as Windows services.

To open the Services Panel, open the Control Panel from the Start Menu as shown in Figure 1.6, “Control Panel”.

Figure 1.6. Control Panel

In the Control Panel, click on the following icon:

Open the Services Panel by clicking on the this shortcut:

The Services Panel is displayed in Figure 1.7, “Services Panel”.

Figure 1.7. Services Panel

The Status column shows the services that are currently running. In Figure 1.7, “Services Panel” is running ("Started") while the Removable Storage is not running (empty Status column).

To start a service, click on the button.

To stop a service, click on the button.

In both cases, verify the success in the Status column of the service list.

For additional information on Windows services, consult your Windows documentation.

Important information on Windows user accounts.

Figure 1.8. Windows Users

For additional information on Windows user accounts, consult your Windows documentation.

	Note
	While the Windows user accounts "system" and "postgres", you don't have to know their passwords.

	Note
	The name of the Windows user account to run the PostgreSQL database service (default: postgres) can be changed during the PostgreSQL installation.

Introduction to PostgreSQL user management.

Figure 1.9. PostgreSQL Users

The PostgreSQL documentation which you can access e.g. through the Start Menu (after PostgreSQL installation) or on the PostgreSQL website contains additional information on PostgreSQL user management.

Caution

Don't get confused by the two "postgres" accounts: Even though they have the same name, they are different things, one lives inside PostgreSQL and one inside Windows. You don't have to know the password of the Windows account "postgres" (The PostgreSQL intaller is creating a long, random password for it), but you have to know the password of the PostgreSQL account "postgres". Please follow the PostgreSQL installation instructions carefully (Section 2.1.2.3, “PostgreSQL”).

If you are going to use DCMMS in more than one language and would like to use the DCMMS translation system for your data, you should read this section.

DCMMS is actually using two translation systems: GNU gettext for text that occurs in the PHP sources and the dcmmstranslation() for text stored inside the PostgreSQL database.

	Note
	The dcmmstranslation() is not yet used for all text stored inside the PostgreSQL database (especially coded values). This will change gradually in the future. For the time being administrators and developers have to understand both translation systems.

Both gettext and dcmmstranslation() will fall back to the two letter ISO language code in case no translation is found for the five letter code (E.g. the "ar" translation is returned if "ar_JO" was requested and no translation was found).

dcmmstranslation('en', name)

$_SESSION["strMapFile"] = "conf/sample_%s.map";

Mailing lists are automated distribution systems for emails.

The majority of the software products mentioned in this document offer a multitude of mailing lists to keep users and administrators updates about the latest releases as well as potential security issues.

	Tip
	If you are not familiar with mailing lists yet, take the time to familiarize with the techniques to subscribe and to post to them.

How to install DCMMS on Windows XP Professional or Windows 2003 Server.

How to install DCMMS on Windows XP Professional or Windows 2003 Server.

Please contact the DCMMS developers if you are looking for a DCMMS CD release.

All installers mentioned below area available in the setup folder of the CD.

2.1.1.1. MS4W base installation

This section describes how to install MS4W for Windows.

The MS4W installer is available from the setup folder of the DCMMS CD or from http://www.maptools.org/dl/ms4w/.

There is two types of MS4W installers

 

			  Zip file based MS4W installer, if this type is selected, the file
			  should be extracted to c:\MS4W.
			  

			  Binary EXE excutable MS4W installer, this installer will install 
			  the MS4W package with all it's contents to  C:\MS4W.
			 
 
			

	Note
	Using the ms4w-2.3.1-setup.exe require to have an internet connection to download the package components.

	Important
	It is recommended to use the Zip based MS4W installer.

Extract the zip file to C:\MS4W

After extraction, the Apache service should be installed by double click on the Apache-install.bat

	Unblock the Apache service
	For security reasons, the Apache service should be unblocked in order to be used

Figure 2.1. Unblock Apache service

2.1.1.2. PostgreSQL

This section describes how to install PostgreSQL for Windows.

The PostgreSQL installer (postgresql-8.3.6-1-windows.exe) is available from the setup folder of the DCMMS CD or from http://www.enterprisedb.com/products/pgdownload.do#windows/.

	Note
	If you are going to download the PostgreSQL from the internet, Please consider that there is two Windows packages, It is recommended to download the PostgreSQL Windows One-Click Installers

Figure 2.2. PostgreSQL Installers

Figure 2.3. PostgreSQL Windows One click Installers

	Note
	PostGIS extension can be installed using the PostgreSQL 8.3 Application stack builder. Important An Internet connection should be available. Important IF THIS STEP IS DONE, YOU CAN SKIP THE PostGIS 1.3.5 Installation STEP, AND GO TO DCMMS 2.0.0 MS4W base installation STEP.

Figure 2.4. PostgreSQL Setup

Click Next >.

Figure 2.5. Choose Installation Path

Figure 2.6. Choose Installation Path

Figure 2.7. Choose Data folder Installation Path

Figure 2.8. Enter the Password for the postgres super user

Figure 2.9. Choose Installation Path

Figure 2.10. Choose Database Port

	Note
	Do not change the locale, keep the default settings as the default is UTF8

Figure 2.11. Choose Database locale

Click on the next button to start the installation.

Figure 2.12. Installation ready

When the installation is finished, the installer will ask to run the Stack builder, The stack title can be used to install additional componenets on top of PostgreSQL.

	Important
	Running the Stack builder requires to have an internet connection, if you do not have it, uncheck the check box.

	Important
	If you run the Stack builder, and installed the PostGIS, You can skip the PostGIS installation

Figure 2.13. Installation Completed

2.1.1.3. PostGIS 1.3.5 Installation

The PostGIS installer (postgis-pg83-setup-1.3.5-1.exe) is available from the setup folder of the DCMMS CD or from http://postgis.refractions.net/.

Figure 2.14. PostGIS License

Click on I Agree if you agree to the PostGIS license in Figure 2.48, “PostGIS License”.

Figure 2.15. PostGIS Components

	Caution
	Uncheck the option Create Database as shown in Figure 2.49, “PostGIS Components” and click Next >. The dcmms database will be created by the DCMMS installer.

Figure 2.16. PostGIS Location

Accept the default settings as shown in Figure 2.50, “PostGIS Location” and click Next >.

	Note
	The destination folder is your PostgreSQL installation folder and might differ from the one shown in Figure 2.50, “PostGIS Location”

Figure 2.17. PostGIS Database Connection

Accept the default settings as shown in Figure 2.51, “PostGIS Database Connection” and enter the password you have chosen for the PostgreSQL superuser "postgres" (Section 2.1.2.3, “PostgreSQL”). Click Install.

Figure 2.18. Installation Complete

Click Close

2.1.1.4.  DCMMS 2.0.4 MS4W base installation

The following steps should be followed in order to setup DCMMS 2.0.4 MS4W based version

The lastest version of the MS4W backage should be downloaded, and extracted to C:\MS4W

Click on the DCMMS 2.0.4 setup in order to install the DCMMS.

The DCMMS installer will copy the needed file under the C:\MS4W folder

The files will be copied to c:\MS4W\apache\htdocs

The files will be copied to c:\MS4W\httpd.d

The files will be copied to c:\MS4W\apache\a

Start the DCMMS Setup, which is available from the setup folder of the DCMMS CD or from the internet: http://dcmms.sourceforge.net.

Figure 2.19. Installer language

Select the language, and Click on OK.

Figure 2.20. DCMMS License

Click on I Agree if you agree to the license shown in the license dialog (Figure 2.20, “DCMMS License”).

Figure 2.21. DCMMS Components

Select all DCMMS components except Update as shown in Figure 2.21, “DCMMS Components” and click Next >.

Figure 2.22. DCMMS Location

Accept the default installation path, c:\ms4w, as shown in Figure 2.22, “DCMMS Location” and click Next >.

Figure 2.23. DCMMS Database Connection

Enter the PostgreSQL superuser "postgres" password (As entered in Figure 2.8, “Enter the Password for the postgres super user”). Click Install.

You should now be able to start the DCMMS from the Start Menu or through the shortcut on the Desktop. Note that the full functionality will only be available once you've completed the data set, e.g. by loading the sample data.

	Note
	The installer will not overwrite existing DCMMS configuration files.

How to install DCMMS on Windows XP Professional or Windows 2003 Server.

How to install DCMMS on Windows XP Professional or Windows 2003 Server.

Please contact the DCMMS developers if you are looking for a DCMMS CD release.

All installers mentioned below area available in the setup folder of the CD.

2.1.2.1. Apache

	Tip
	If you are running Skype, you may want to shutdown Skype while you are installing Apache as Skype might otherwise prevent Apache from using port 80.

	Tip
	If the Apache installation is not fully successful because another program (e.g. IIS) is already using port 80, simply edit httpd.conf to use another port (e.g. "Listen 81" instead of "Listen 80" and run the Apache setup again. Choosing the repair option will complete the Apache installation.

Run the Apache installer. The Apache installer is available from the setup folder of the DCMMS CD or from the Apache website: http://httpd.apache.org.

Figure 2.24. Apache Wizard

In the Apache installer welcome page, click Next > (Figure 2.24, “Apache Wizard”).

Figure 2.25. Apache License

Select I accept the terms in the license agreement and click Next > (Figure 2.25, “Apache License”).

Figure 2.26. Apache Readme

Read through the information in Figure 2.26, “Apache Readme” and click on Next >.

Figure 2.27. Apache Information

Fill in the fields Network Domain (The domain of your Organization), Server Name (The name of your DCMMS server) and Administrator's Email Address (Your email address). Verify that the option for All Users, on Port 80, as a Service is selected and click Next > (Figure 2.27, “Apache Information”).

Figure 2.28. Apache Setup Type

Verify the selection in Figure 2.28, “Apache Setup Type” and click Next >.

Figure 2.29. Apache Location

Make sure that the Destination Folder is C:\Program Files\Apache Group and click Next >.

	Tip
	The DCMMS installer reads the Apache installation folder from the Windows registry. You can install Apache to different locations.

Figure 2.30. Apache Install

In the dialog shown in Figure 2.30, “Apache Install”, click Install.

	Tip
	If the Apache installation fails because another application is using port 80, you can use the following commands to find out which application is using port 80: netstat -aon tasklist Look for the process id (PID) of the process occupying port 80 and find the application of the process id.

2.1.2.2. PHP

Run the DCMMS Scripting installer. The installer is available from the setup folder of the CD or from the DCMMS website: http://dcmms.sourceforge.net.

Figure 2.31. PHP License

Click I Agree if you agree to the license (Figure 2.31, “PHP License”).

Figure 2.32. PHP Components

Click Next >.

	Tip
	PEAR modules can be easily installed and upgraded over the internet. See the PEAR documentation for details. However, the DCMMS scripting installer provides all necessary packages.

Figure 2.33. PHP Location

Accept the default installation directory, c:\windows\php, by clicking Install (Figure 2.33, “PHP Location”).

2.1.2.3. PostgreSQL

This section describes how to install PostgreSQL for Windows.

The PostgreSQL installer (postgresql-8.1.msi) is available from the setup folder of the DCMMS CD or from http://pgfoundry.org/projects/pginstaller/.

	Note
	Don't get confused by the two PostgreSQL installer files. They are both required and can only be installed together.

Run the PostgreSQL installer and select the English language.

Figure 2.34. PostgreSQL Language Selection

Click Start > to begin the Installation

Figure 2.35. PostgreSQL Setup

Click Next >.

Figure 2.36. Installation Notes

Press Next > after reading the installation instructions.

Figure 2.37. Choose Installation Options

Note that the PostgreSQL installation path is not important. Please accept the default installation path provided by the installer.

Accept the other settings as shown in Figure 2.37, “Choose Installation Options” and click Next >.

Figure 2.38. Service Configuration

Accept the default settings as shown in Figure 2.38, “Service Configuration” and click Next >. Instead of "Z1027" your installer will show the name of your computer.

Figure 2.39. Account Error

Select Yes.

Figure 2.40. Password

Accept the random password by clicking OK.

	Tip
	You don't have to remember the random password. It is only used internally to run the PostgreSQL service on Windows. See Section 1.4, “Concepts” for detailed information.

Figure 2.41. Successfully granted the 'Logon as a service' right

Click on OK.

Figure 2.42. Initialise Database Cluster

Accept the default settings as shown in Figure 2.42, “Initialise Database Cluster” and choose an appropriate password for the PostgreSQL superuser "postgres". Enter the password to the Password and Password (again) fields then click Next >.

	Caution
	You'll need this password (for the PostgreSQL superuser "postgres") later on during the installation process e.g. while running the DCMMS setup and for database maintenance purposes. Make sure that you remember it well.

Figure 2.43. Enable Procedural Languages

Accept the default settings as shown in Figure 2.43, “Enable Procedural Languages”. Make sure that "PL/pgsql" is selected. Click Next >.

Figure 2.44. Enable Contrib Modules

Accept the default selection as shown in Figure 2.44, “Enable Contrib Modules” and click Next >.

Figure 2.45. Enable PostGIS

As shown in Figure 2.45, “Enable PostGIS”, leave the option Enable PostGIS in template1 unchecked and click Next >.

PostGIS will be enabled for the dcmms database by the DCMMS installer.

Figure 2.46. Ready to Install

As shown in Figure 2.46, “Ready to Install”, PostgeSQL can be installed now. Click Next >.

Figure 2.47. Installation complete

Click Finish.

	Tip
	As mentioned in Figure 2.47, “Installation complete”, it is recommended to subscribe to the pgsql-announce mailing list to stay up-to-date with the latest PostgreSQL developments.

2.1.2.4. PostGIS

Once the PostgreSQL setup has finished, start the PostGIS setup which is available in the setup folder of the CD or on the internet: http://www.webbased.co.uk/mca/.

Figure 2.48. PostGIS License

Click on I Agree if you agree to the PostGIS license in Figure 2.48, “PostGIS License”.

Figure 2.49. PostGIS Components

	Caution
	Uncheck the option Create Database as shown in Figure 2.49, “PostGIS Components” and click Next >. The dcmms database will be created by the DCMMS installer.

Figure 2.50. PostGIS Location

Accept the default settings as shown in Figure 2.50, “PostGIS Location” and click Next >.

	Note
	The destination folder is your PostgreSQL installation folder and might differ from the one shown in Figure 2.50, “PostGIS Location”

Figure 2.51. PostGIS Database Connection

Accept the default settings as shown in Figure 2.51, “PostGIS Database Connection” and enter the password you have chosen for the PostgreSQL superuser "postgres" (Section 2.1.2.3, “PostgreSQL”). Click Install.

Figure 2.52. Installation Complete

Click Close

2.1.2.5. DCMMS

Start the DCMMS Setup, which is available from the setup folder of the DCMMS CD or from the internet: http://dcmms.sourceforge.net.

Figure 2.53. DCMMS License

Click on I Agree if you agree to the license shown in the license dialog (Figure 2.53, “DCMMS License”).

Figure 2.54. DCMMS Components

Select all DCMMS components except Update as shown in Figure 2.54, “DCMMS Components” and click Next >.

Figure 2.55. DCMMS Location

Accept the default installation path, c:\program files\dcmms, as shown in Figure 2.55, “DCMMS Location” and click Next >.

Figure 2.56. DCMMS Database Connection

Enter the PostgreSQL superuser "postgres" password (As entered in Figure 2.42, “Initialise Database Cluster”). Click Install.

You should now be able to start the DCMMS from the Start Menu or through the shortcut on the Desktop. Note that the full functionality will only be available once you've completed the data set, e.g. by loading the sample data.

	Note
	The installer will not overwrite existing DCMMS configuration files.

How to install DCMMS manually.

	Note
	This section might be useful only for installations on non-Windows platforms and for developers who are interested in the details of the DCMMS installation process.

	Tip
	The DCMMS installer sources (e.g. dcmms.nsi) may contain additional helpful information on the installation process.

	Caution
	The following expects that various PostgreSQL binaries, such as psql.exe or createlang.exe are in the PATH. If necessary, you have to change your PATH environment variable to include the bin folder of your PostgreSQL installation.

2.1.3.1. PostgreSQL

The PostgreSQL database is available from http://www.postgresql.org.

The PostgreSQL installation should support UNICODE.

	Warning
	You may run into problems if you use a binary PostgreSQL distribution under Linux or UNIX. In order to use PostGIS and specifically GEOS from PostgreSQL, the binaries have to be linked against libstc++. The PostGIS documentation contains details regarding this issue.

In order to enforce DCMMS logins with password authentication, the pg_hba.conf configuration file should be altered like in the following example:

# TYPE  DATABASE    USER      IP-ADDRESS  IP-MASK           METHOD
host    all         postgres  127.0.0.1   255.255.255.255   trust
host    dcmms       all       127.0.0.1   255.255.255.255   password

Note that this still allows the PostgreSQL superuser postgres to connect to PostgreSQL server without authentication. However the user postgres is not allowed to log on to DCMMS.

Note

The instructions below assume that the PostgreSQL administrator is named postgres and that the postmaster is running on the local machine (localhost). If this is not the case for you, you'll have to adjust the commands accordingly. The same applies to the connection method - if your postmaster is not configured to accept TCP/IP connections, you have to adjust the commands (and possibly the DCMMS configuration).

Create a new database named dcmms using UNICODE, load the PL/SQL language to the database:

createdb -U postgres -h localhost --encoding=UNICODE dcmms
createlang -U postgres -h localhost plpgsql dcmms 
           

If PL/SQL was created in template1, the second command will fail. Ignore the error message in this case.

psql -U postgres -h localhost -f postgis.sql dcmms 
psql -U postgres -h localhost -f spatial_ref_sys.sql dcmms

2.1.3.3. PostArabic

PostArabic is a small module that adds Arabic shaping functionality to PostgreSQL.

	Tip
	The PostArabic installation is only required in order to display Arabic map labels. If you are not interested in Arabic map labels, you can skip the PostArabic installation.

The PostArabic sources are available from the DCMMS download page.

Follow the installation instructions in the file README.arabic.

Change to the directory containing arabic.sql and load PostArabic to the dcmms database:

psql -U postgres -h localhost -f arabic.sql dcmms

make
make install
psql -U postgres -h localhost -f fuzzystrmatch.sql

Alias /dcmms "c:/program files/dcmms/"
<Directory "c:/program files/dcmms">
  Options Indexes Multiviews
</Directory>

Alias /ms_tmp/ "c:/tmp/ms_tmp/"

2.1.3.6. PHP

The PHP scripting language is available from www.php.net.

DCMMS is currently using PHP 4.*. Use of DCMMS with PHP 5.0 will require some small changes to the application and is not recommended yet. Please contact the DCMMS developers if PHP 5.0 is a requirement for your installation.

Follow the installation instructions in the PHP documentations.

	Note
	If you don't install PHP to c:\windows\php, some of the settings below have to be adjusted.

	Caution
	Because of previous PHP/Mapscript limitations, it is recommended to install PHP as a CGI command. The use of PHP as an Apache module is not very well tested with DCMMS and may lead to instabilities. If you are testing such a setup, please share your experiences with the DCMMS developers.

The installation can be completed with the following three lines in httpd.conf:

ScriptAlias /php/ "c:/windows/php/"
AddType application/x-httpd-php .php
Action application/x-httpd-php "/php/php.exe"

Again, make sure that the path names above match the ones on your system.

Add the following DCMMS-specific configuration settings to c:\windows\php.ini:

default_mimetype = "text/html"
default_charset = "utf-8"

include_path = ".;c:\windows\php\pear"

error_reporting  =  E_ALL & ~E_NOTICE

extension_dir = "c:/windows/php/extensions"
enable_dl = On

allow_call_time_pass_reference = On

file_uploads = On
upload_tmp_dir = c:\tmp
upload_max_filesize = 20M

extension=php_gd2.dll
extension=php_gettext.dll
extension=php_pgsql.dll
extension=php_zip.dll
extension=php_mapscript_46.dll

[Session]
session.save_path = c:/tmp
      

	Caution
	In order to use gettext in PHP on Linux, the PHP safe mode has to be enabled. The reason is that the putenv() function to set the locale will fail otherwise. In php.ini: safe_mode = On

2.1.3.7. Mapserver

On Windows, install the mapserver distribution with PHP/Mapscript, which is available from the internet under http://maptools.org.

On other operating systems, install PHP/Mapscript from the Mapserver distribution which is available from http://mapserver.gis.umn.edu/index.html.

Make sure that the PHP/Mapscript extension is loaded in php.ini.

	Note
	You'll need a PHP/Mapscript binary compiled with PostGIS support.

psql -U postgres -h localhost -f create_dcmms_ddl.sql dcmms
psql -U postgres -h localhost -f create_views.sql dcmms

set PGCLIENTENCODING=WINDOWS-1256
psql -d dcmms -U postgres -h localhost -f administrativearea.sql
psql -d dcmms -U postgres -h localhost -f village.sql
psql -d dcmms -U postgres -h localhost -f landmark.sql

Upon first installation, the DCMMS application will provide two default PostgreSQL (DCMMS) users:

As the name indicates, admin has administrator rights, whereas the user dcmms has not.

See Section 1.4.3, “PostgreSQL users” for detailed information on Windows and PostgreSQL users.

	Caution
	On production systems, you should change the default passwords as soon as possible for security reasons.

The following points should be checked before a DCMMS goes into production:

This section describes the installation of various optional tools that ease the DCMMS administration and configuration.

2.1.6.2. GIX

GIX is an ArcView 3.* extension that allows to export views to mapserver map files.

GIX is available from http://gix.sourceforge.net.

	Note
	You can only use fragments from the map files created by GIX as ArcView 3.* does not support PostGIS.

See Section 2.2.2, “Custom Map” for details regarding the DCMMS map files.

2.1.6.3. poEdit

To edit the dcmms.po files, poEdit is recommended. It is freely available from http://poedit.sourceforge.net.

	Tip
	Install poEdit version 1.3.1 or higher.

In order to extract the translation messages from the PHP sources, the following settings should be applied.

Start poEdit.

Select Preferences from the File menu.

Select the Parser tab and click on the New button.

Figure 2.57. poEdit PHP parser settings

Fill in the settings as shown in Figure 2.57, “poEdit PHP parser settings”

Close the dialogs.

Open a dcmms.po file.

Choose Options... from the Catalog menu.

In the Paths tab, add the path to the DCMMS source as shown in Figure 2.58, “Catalog Path”

Figure 2.58. Catalog Path

	Caution
	Make sure that you enter the actual path to the DCMMS sources on your system.

Once the settings above have been applied, it is possible to update the catalog by selecting Update from sources from the Catalog menu.

See also Section 1.4.4, “Translation System”.

The file include/dcmconfig.php contains the configuration of the DCMMS application.

A default configuration file is stored under include/dcmconfig.php.default. Copy this file to include/dcmconfig.php if necessary.

The configuration file can be edited using any text editor.

All other configuration files can be found in the conf folder: c:\ms4w\apps\dcmms\conf.

The PHP configuration file php.ini is installed by default under c:\windows.

The intSRID variable in dcmconfig.php is used to specify the spatial referencing system identifier for your spatial data. The PostGIS documentation contains detailed information about spatial reference systems. PostGIS stores SRIDs in the spatial_ref_sys table. A value of "-1" can be used in case no real SRID is available. However, the specification of an SRID is very important in order to expose the data through services like WMS.

How to use your own maps with DCMMS.

Create your own map file(s) and edit the following line in dcmconfig.php to point to this file:

$_SESSION["strMapFile"] = "conf/sample_%s.map";

	Warning
	When customizing the map files, make sure to use other names than sample_en.map. An update of the application would otherwise overwrite your customized map files. Adjust dcmconfig.php accordingly.

In the default configuration, you need one map file for every language (%s will be replaced with the two-letter ISO language code).

If you would like to use DCMMS in more than one language, please also read Section 1.4.4, “Translation System”.

	Note
	The "DESCRIPTION" metadata information must be provided for layers that return results for the identify tool. In addition, the "TEMPLATE" has to be set for the respective class.

The following layers are required and should be copied from the sample files:

	Tip
	The default map resolution in map.php can be configured in the map file. Look for a line like the following: SIZE 600 450 Currently the following configurations are possible without changes to the PHP source: SIZE 400 300 SIZE 600 450 SIZE 800 600

	Tip
	DCMMS comes with symbol and font definitions in the files etc\symbols.sym and etc\fonts.txt. It is recommended that you use different files for custom symbol and font definitions. A DCMMS update will overwrite these files.

	Tip
	Use shptree.exe from the mapserver distribution to index large shape files used by the application. Indexes created by shptree.exe will increase the performance when PHP/Mapscript is dealing with these files. Note that the shptree.exe index format differs e.g. from the one used by ArcView.

	Tip
	ArcView 3.* users may want to use the GIX extension to transfer symbology from ArcView to the mapserver map file. See Section 2.1.6.2, “GIX”.

The mapserver documentation available from http://mapserver.gis.umn.edu/ contains detailed information about the mapfile syntax.

2.2.2.1. Tiled Shapefiles

Tiled shapefiles allow mapserver to maximize performance for large shapefile datasets.

The ngwa.map map file provides an example of tiled shapefile usage.

Please refer to the mapserver documentation for details on tiled shapefiles.

	Tip
	Use the tileindex.exe from the mapserver distribution to create tile indexes.

	Caution
	Uniform shapefiles have to be used when they are tiled. They have to have exactly the same number of fields in the same order.

To re-order shapefile fields using ArcView 3.*, follow these steps:

• Open a View.

• Add the shapefile as a Theme to the View.

• Open the attribute table.

• Drag and drop the field headers until they are in the correct order.

• Go back to the View.

• Select Theme->Convert to Shapefile.

2.2.2.2. PostGIS Layers

The DCMMS application replaces the dummy user name and password in the mapfile with the information provided by the user when logging on. Example 2.1, “PostGIS Connection Example” shows an example PostGIS connection line from a mapfile.

Example 2.1. PostGIS Connection Example

CONNECTION "dbname=dcmms user=dummy password=dummy host=localhost"
	    

	Important
	Make sure that the PostgreSQL "dcmmsuser" group has the right to select from the tables used for your PostGIS layers.

2.2.2.3. Tiled Images

Tiled images allow mapserver to maximize performance for large raster datasets.

The following steps are required to prepare the tiled images, and include them on the map file.

Please refer to the mapserver documentation for details on tiled images.

Use the gdaltindex.exe from the mapserver distribution to create tile indexes.

Example of usage:

gdaltindex sana_index.shp *.tif

	Tip
	In order to increase the display, and rendering performance of the images it is prefered to create over views for these images using the following command: gdaladdo -r average imagename.tif 2 4 8 16 32 64 128

You can add the tiled images on the map file using the following statements:

	      LAYER
		      NAME "satellite"
		      STATUS default
		      TILEINDEX "c:\ms4w\apps\dcmms\tiff\image_index.shp"
		      TILEITEM "Location"
		      TYPE RASTER
	      END
	   

	Tip
	When using raster data, it is recommended to change the IMAGETYPE parameter to "JPEG" as it offers good compression for raster data.

esri_0 c:/windows/fonts/esri_0.ttf

LAYER
  NAME Valve
  data "c:/ms4w/apps/dcmms/data/valve"
  TYPE POINT
  STATUS DEFAULT
  maxscale 5000
  labelmaxscale 5000
  labelitem "symbol"
  labelangleitem "angle"
  CLASS
    NAME 'Valve'
    template "ttt_query.html"
    SYMBOL "circle"
    SIZE 1
    COLOR 0 0 255
    LABEL
    color 0 0 255
    position cc
    font esri_0
    type truetype
    size 10
  END	
  END
  
  METADATA
    "DESCRIPTION" "Valve"
    "RESULT_FIELDS" "DIAMETER"
  END
  TOLERANCE 5
END 

Plug-Ins provide configurable and extensible ways to extend the application functionality in a way that is compatible with future releases of the the software.

; Configuration file for map.php plug-ins
[IdentifyPlugin]
Plugin1 = ImageIdentifyPlugin
Layer1 = village
;Plugin2 = ???
;Layer2 = ???

2.2.3.2. Search Plug-Ins

Search plug-ins allow additional search functionality to be added to the find tool that is displayed on every page. Use of search plug-ins is triggered by configurable keywords that are followed by a colon (":") and the search term itself.

Search plug-ins are easy to implement. The DCMMS Developer Guide contains the details.

The search plug-ins are configured in conf/searchplugin.ini. The file is a simple text file that can be edited with any text editor.

DCMMS includes the CustomerSearchPlugin - see Section 2.2.3.2.1, “Customer Search Plug-In” for details.

Example 2.3. Excerpt from searchplugin.ini

; Configuration file for search.php plug-ins 
[SearchPlugin] 
Plugin1 = CustomerSearchPlugin 
; The keyword that triggers the plug-in to be executed. Case sensitive.
Keyword1 = customer 
;Plugin2 = ??? 
;Keyword2 = ??? 

[Plugin1] 

Lines starting with ";" are comments and are ignored.

The section header starting the search plug-in configuration section.

The CustomerSearchPlugin class is the first plug-in that is registered with the application. Keyword1 will define when the plug-in is executed. Additional configuration parameters for the

The first plug-in (CustomerSearchPlugin will be executed when the keyword "customer" is used (e.g. using the search term "customer:311").

An additional plug-in can be added by uncommenting this line and replacing the question marks with the plug-in class name.

This header starts the configuration section for Plugin1, in this example the CustomerSearchPlugin. See Section 2.2.3.2.1, “Customer Search Plug-In” for details.

2.2.3.2.1. Customer Search Plug-In

The customer search plug-in allows to find customer locations on their map using a numeric identifier like the contract number.

Geocoded customer locations (polygons) are required in order to use the plug-ins functionality. The CustomerSearchPlugin class in plugin/customersearchplugin.php contains the implementation.

The plug-in assumes a two table structure where the first table (customer) contains the search term (customer ID) and the geocode as a foreign key. The second table (building) contains the geocode and the polygon geometry that will be used to determine the map extent. The relationship between customer and building is one-to-many.

Example 2.4, “Customer Search Plug-In Configuration” contains a snippet from searchplugin.ini with an example CustomerSearchPlugin configuration.

Example 2.4. Customer Search Plug-In Configuration

[Plugin1] 
; PEAR DB Data Source Name (DSN). See PEAR DB documentation for details. 
DSN = pgsql://dcmms:dcmms@localhost/customer 
; Name of the table that contains customer id and geocode.
CustomerTable = customer 
; Name of the id field in the customer table. Should be indexed.
CustomerID = id 
; Name of the geocode field in the customer table
CustomerGeocode = geocode 
; Name of the table that contains geocode and polygon geometry. Should be indexed.
BuildingTable = building 
; Name of the geocode field in the building table
BuildingGeocode = nwsa_pk 
; Name of the geometry field in the building table
BuildingGeometry = the_geom 
          

Section "Plugin1" contains the CustomerSearchPlugin configuration if CustomerSearchPlugin was registered as Plugin1 (See Example 2.3, “Excerpt from searchplugin.ini”).

Lines starting with ";" are comments.

In this case, the customer database from the PostgreSQL server running on localhost will be used with the user name dcmms and the password dcmms.

The "customer" table will be queried for the search term (ID) provided by the user.

The "id" field of the customer table contains the customer id.

The "geocode" field of the customer table will be used to join the building table (foreign key).

The "building" table will be joined against the customer table. It contains the geographic information.

The "nwsa_pk" field (primary key) will be used to join the customer table.

The "the_geom" field of the building table contains the polygon geometry that will be used to determine the map extent.

	Tip
	The necessary SQL statements to create the table structure required for this example configuration is described in source code comments in plugin/customersearchplugin.ini.

	Important
	Note that the DSN configuration option contains database user name and password in clear text. Take protective measures like locking down this particular user account or protect conf/searchplugin.ini from unauthorized access.

Tip

If your customer data resides in an ORACLE database, the following instructions show how to move the data to an PostgreSQL database using ArcView 3.x: Create an ODBC connection to your ORACLE database. In the ArcView Project GUI, connect to the database using Project->SQL Connect.... Query the table that contains the customer information. In the ArcView table, choose Table->Properties.. from the menu. Make all fields except the id and geocode fields invisible. Close the Table Properties dialog. Ensure that the id field is before the geocode field. Export the table to a delimited text file by choosing File->Export... from the menu. The exported file should look like in Example 2.5, “First lines of sample customer.txt file”. Example 2.5. First lines of sample customer.txt file "Id","Nwsa_pk" 48859,1617410105001701 48433,1318310119001821 The customer.txt file can be loaded to PostgreSQL using the following SQL statement (adjust the path to the file accordingly): copy customer from 'c:/tmp/customer.txt' with csv header

	Tip
	The building table can be created directly from a polygon shapefile that contains the geocode field. See Section 2.3.1, “GIS Data Loading” for different options to load shapefiles to GIS databases.

Through modification of lookup table values in the database, DCMMS can be customized to meet different needs. Please explore the DCMMS data model and the DCMMS database for details.

	Caution
	To prevent future DCMMS updates from overwriting your customizations (or your customizations colliding with future DCMMS coded values, you are strongly advised to coordinate your database-side customizations with the developers, e.g. by sending an email to <dcmms-devel@lists.sourceforge.net>.

This section discusses various ways to load GIS data in various formats to the dcmms database.

Tip

Not all GIS data used by the application has to be loaded to the database. Data that is only displayed on the map and not used otherwise in the application can be kept in its original format and location if it is supported by Mapserver. This is the case for shapefiles. Unless you are restoring a backup, only the following three layers of GIS data have to be loaded to the DCMMS database: AdministrativeArea Landmark Village

Besides the options described in the following sections, tools like ogr, QGIS or FME can also be used to load the data.

If you would like to load and use data in multiple languages, an understanding of the translation system (Section 1.4.4, “Translation System”) is required.

	Tip
	For ArcView 3.x users, the AV PostGIS Connection extension is the preferred way to load shapefiles to PostGIS: http://avpgcon.sourceforge.net

2.3.1.1. Shapefile Loading

When loading certain shapefiles to the DCMMS database, it might be required to drop the views before loading and to restore them after loading. The scripts script/drop_views.sql and script/create_views.sql can be used for this purpose.

	Note
	Data that is edited in DCMMS uses sequences to determine the next primary key. For this reason it might be necessary to adjust a sequence if certain shapefiles are loaded. One example is the landmark table. The following SQL statement shows how to set the correct start value for the sequence after the landmark shapefile is loaded: select setval('landmark_seq', max(gid) from landmark);

	Note
	You may also want to update the Translation table after loading shapefiles that contain translations (Section 1.4.4, “Translation System”).

PATH=%PATH%;c:\Program Files\PostgreSQL\8.1\bin
	  

set PGCLIENTENCODING=WINDOWS-1256

psql -d dcmms -U postgres -f \
"c:\ms4w\apps\dcmms\script\drop_views.sql"
        

shp2pgsql -d -D landmark.shp landmark > landmark.sql
psql -d dcmms -U postgres -f landmark.sql

psql -d dcmms -U postgres -f \
"c:\ms4w\apps\dcmms\script\create_views.sql"
        

In case you have the unit cost information saved in an Excel sheet, to load unit cost information to the PostgreSQL database do the following:

	Caution
	A damaged DCMMS installation can be difficult to repair and may require a complete re-installation of the system. For this reason, a proper user privilege separation is of utmost importance.

The user operating the DCMMS application on the server must not have any administrator rights assigned.

The PostgreSQL administrator and the postgres accounts should be guarded by good passwords (not "password", "1234567quot; or "") and these password should only be known to the administrators.

	Caution
	When changing the password of the Windows user "postgres", the administrator has to re-enter the postgres password in the properties of the PostgreSQL Database Server 8.1 service.

Database administration can be performed e.g. using pgAdmin which is included in the PostgreSQL installation. The SQL language can be used to perform those tasks that are not directly accessible through the pgAdmin GUI.

See the PostgreSQL documentation for detailed information regarding the PostgreSQL database and SQL commands.

	Tip
	Experienced ORACLE administrators that are used to work with sqlplus may prefer the psql commandline environment over pgAdmin.

The script script/create_pressurizedmain_analysis.sql can be used to calculate the number of repairs for each pressurizedmain.

To remove the result fields and the nearest() function from the database, use the script script/delete_pressurizedmain_analyis.sql.

The pressure dependency of leaks can be proofed by showing that the repair frequency is higher in areas with higher network pressure.

To simplify the analysis, the topographic elevation will be used as an indicator of the network pressure. It is assumed that the lower areas of a distribution zone show higher static pressures.

The analysis can be performed by overlaying the elevation distribution of reported leaks with the elevation distribution of network nodes. Histograms are a suitable way to visualize these distributions.

The assignment of elevations to network nodes and leak repair locations can be done e.g. from spot elevations with ArcView's Geoprocessing Wizard or from a Digital Terrain Model (DTM). You should discard those node elevation that are higher than the maximum leak repair elevation or lower than the lowest leak repair elevation.

Once the elevations have been assigned, the R statistical analysis package can be used for the analysis. R is available from http://www.r-project.org/.

	Note
	The following example assumes that the elevation information is stored in the elevation fields of the DBF files.

If the histogram shows that the distribution of the leak repairs is shifted to the left compared to the distribution of the network nodes, the leak distribution is most probably pressure-dependent.

How GIS data is managed and reviewed in the case of NGWA.

NGWA's GIS data is kept in shapefile format, managed by the CVS version management system.

Figure 2.59. NGWA GIS Data Review

Figure 2.59, “NGWA GIS Data Review” outlines activities, roles and responsibilities of the GIS data review process. The process ensures that only quality-checked data is used in the DCMMS production system.

The DCMMS Manager has to check the lastest GIS data in the CVS using a DCMMS test installation. If necessary, the GIS operators have to correct errors (e.g. different field names used in a tiled set of shapefiles). Once the data has passed the quality control, the DCMMS has to mark the files in the CVS with the tag DCMMS.

	Important
	The DCMMS manager should update each shapefile used in the DCMMS indidually: Update the shapefile on the test machine, update the indexes, view it in the application. Updating of all files at the same time bears the risk of not being able to identify the file that causes the problem.

The DCMMS administrator is responsible for the CVS update script on the server. The script updates shapefile tilesets, shapefile indexes and the GIS data used in the DCMMS production system.

The following batch file illustrates the update on gisserver:

        e:
	cd sandbox\dcmms\ngwa
        cvs update -dP -C -r DCMMS
	tile4ms lot_line_index.txt lot_line_index
	tile4ms gravitymain_index.txt  gravitymain_index
	tile4ms pressurizedmain_index.txt pressurizedmain_index
	shptree ajlun\mapping\lot\lot_line.shp
	shptree ajlun\water\network\pressurizedmain.shp
	shptree ajlun\sewer\network\kufranja\gravitymain.shp
	shptree al_koura\mapping\lot\lot_line.shp
	shptree al_koura\water\network\pressurizedmain.shp
	shptree badia\mapping\lot\lot_line.shp
	shptree badia\water\network\pressurizedmain.shp
	shptree irbid\mapping\lot\lot_line.shp
	shptree irbid\water\network\pressurizedmain.shp
	shptree irbid\sewer\network\irbid\gravitymain.shp
	shptree irbid\sewer\network\dougrah\gravitymain.shp
	shptree jarash\mapping\lot\lot_line.shp
	shptree jarash\water\network\pressurizedmain.shp
	shptree jarash\sewer\network\gravitymain.shp
	shptree kinana\mapping\lot\lot_line.shp
	shptree kinana\water\network\pressurizedmain.shp
	shptree mafraq\mapping\lot\lot_line.shp
	shptree mafraq\water\network\pressurizedmain.shp
	shptree mafraq\sewer\network\mafraq\gravitymain.shp
	shptree ramtha\mapping\lot\lot_line.shp
	shptree ramtha\water\network\pressurizedmain.shp
	shptree ramtha\sewer\network\gravitymain.shp
	shptree shouna\mapping\lot\lot_line.shp
	shptree shouna\water\network\pressurizedmain.shp
	shptree ubaid\mapping\lot\lot_line.shp
	shptree ubaid\water\network\pressurizedmain.shp
	shptree ubaid\sewer\network\gravitymain.shp
	

The Windows Task Scheduler is used to run the update script every night.

Version 2.0.3 is a maintenance and bug fix, and additional added fuctionality release .

This release have many additions, especially in the reporting, and complaint information.

DCMMS 2.0.4 Installer Update

DCMMS 2.0.4 Manual Update

If you are not using DCMMS on Windows or are having problems with the Installer update, please follow the procedure below:

The 2.0.0 release marks a series of underlying technology changes. Use of PHP 5, MS4W and PostgreSQL 8.2 illustrates these changes.

Add the new monetary formatting option to dcmconfig.php. E.g.:

/**
 * Formatting options for monetary things. Used with the PostgreSQL to_char()
 * function.
 */
$_SESSION['strMonetaryFormat'] = '999999.99';

Add the new spatial referencing system identifier (SRID) to dcmconfig.php. E.g.:

/**
 * The spatial referencing system identifier (SRID) that should be used to for the spatial
 * data.
 */
$_SESSION['intSRID'] = 32636;

See the PostGIS documentation for more information on the spatial referencing system identifier.

Search plug-ins can now be used to provide additional search services such as zoom to a customer location (See Section 2.2.3.2, “Search Plug-Ins”).

Shapefile loader and dumper have been removed from the DCMMS application. You can used Gshp2pgsql and Gpgsql2shp instead.

Version 1.1.2 is a maintenance and bug fix release that does not add any additional functionality.

The workorder subtype descriptions are now translated using dcmmstranslation().

If you are not using DCMMS on Windows or are having problems with the Installer update, please follow the procedure below:

Version 1.1.1 is a maintenance and bug fix release that does not add any additional functionality.

If you are not using DCMMS on Windows or are having problems with the Installer update, please follow the procedure below:

As the status field was moved from the workorder table to the maintenance table, it it necessary to adjust the filter setting for the pending workorder layers in the map files from

filter "status = 1"

filter "1=(select status from maintenance where maintenance.id=workorder.id)"

Because PostgreSQL versions starting with 8.1.0 are not generating OID columns by default, it might be necessary to update your map files. See Section 2.8.8, “ERROR: column "oid" does not exist”.

Windows users should follow the steps below for an installer-based update:

set PGUSER=postgres
set PGPASSWORD=password
set PGCLIENTENCODING=WINDOWS-1256
set PGPATH=c:\program files\postgresql\8.0
PATH=%PATH%;c:\program files\postgresql\8.0\bin
pg_dump -Fc dcmms > dcmms.dump
        

set PGUSER=postgres
set PGPASSWORD=password
set PGCLIENTENCODING=WINDOWS-1256
set PGPATH=c:\program files\postgresql\8.1
PATH=%PATH%;c:\program files\postgresql\8.1\bin
dropdb dcmms
"%PGPATH%\share\contrib\postgis\postgis_restore.pl" \
"%PGPATH%\share\contrib\lwpostgis.sql" \
dcmms dcmms.dump "-E UNICODE" > restore.log
        

If you are not using DCMMS on Windows or are having problems with the Installer update, please follow the procedure below:

Version 1.0.5 is a bug fix and maintenance release that brings several improvements to the DCMMS application.

	Caution
	As mapserver 4.6.0 supports hatching, you should change the definition of the AreaOfInterest class in your map files. The old definition is shown in Example 2.8, “Old AreaOfInterest Class” and the new one is shown in Example 2.8, “Old AreaOfInterest Class”.

CLASS
  NAME 'AreaOfInterest'
  SYMBOL "circle"
  SIZE 1
  COLOR 255 255 0
  OUTLINECOLOR 255 255 0
END

CLASS
  NAME 'AreaOfInterest'
  STYLE
  SYMBOL "aoihatch"
    SIZE 10
    WIDTH 2
    ANGLE 45
    COLOR 255 255 0
    OUTLINECOLOR 255 255 0
  END
END

	Caution
	Make sure that you change your field names from arlocation to arname and enlocation to name. Likewise, ardescript should become arname and endescript should become name. Note that the new translation system is more flexible. The name field does not necessarily have to contain English values. See Section 1.4.4, “Translation System” for more information on the new translation system.

	Caution
	The format of the IdentifyPlugin configuration file (conf\identifyplugin.ini) has changed. See Section 2.2.3.1, “Identify Plug-Ins” and conf\identifyplugin.ini.default for the details.

Windows users should follow these steps using the DCMMS installer:

set PGUSER=postgres
set PGPASSWORD=password
set PGCLIENTENCODING=WINDOWS-1256
set PGPATH=c:\program files\postgresql\8.0
PATH=%PATH%;c:\program files\postgresql\8.0\bin
pg_dump -Fc dcmms > dcmms.dump
dropdb dcmms
"%PGPATH%\share\contrib\postgis\postgis_restore.pl" \
"%PGPATH%\share\contrib\lwpostgis.sql" \
dcmms dcmms.dump "-E UNICODE" > restore.log

If you are not using DCMMS on Windows or are having problems with the Installer update, please follow the procedure below:

psql -U postgres -h localhost -f drop_views.sql dcmms
psql -U postgres -E UNICODE -h localhost -f update_dcmms_ddl.sql dcmms
psql -U postgres -h localhost -f create_views.sql

	Tip
	One of the new features in 1.0.5 is the visual identification of duplicate workorders. You should add a new layer to show the area of interest for the pending workorders. This allows the visual identification of duplicate complaints. E.g. add the following to your map files before the first layer:

# PendingWorkorders
LAYER
  CONNECTIONTYPE postgis
  NAME PendingWorkorders
  maxscale 15000
  TYPE POLYGON
  STATUS DEFAULT
  CONNECTION "dbname=dcmms user=dummy password=dummy host=localhost"
  DATA "areaofinterest from workorder using unique oid using SRID=-1"
  filter "status = 1"
  CLASS
    NAME 'PendingWorkorders'
    STYLE
      SYMBOL "aoihatch"
      SIZE 8
      WIDTH 1
      ANGLE 315
      COLOR 255 150 150
      OUTLINECOLOR 255 150 150
    END
  END
  TOLERANCE 15
END # Layer

If you are not using a custom symbol file (not etc/symbols.sym), you should add the following symbol definition to it:

SYMBOL
  NAME 'aoihatch'
  TYPE HATCH
END

	Note
	There may be error messages caused by the update_dcmms_ddl.sql script that can be savely ignored. If you cannot judge yourself if the error message should be ignored, please file a support request including the suspicious error messages.

	Note
	When upgrading PostgreSQL, make sure that your postgresql.conf customizations are preserved (See Section 2.1.5, “Checklist”).

	Note
	Note that the introduction of the History table requires to update batch files used in the merging process (See Section 2.3.3.3, “Merge DCMMS Databases”).

Version 1.0.4 is a bug fix and maintenance release that brings several improvements to the DCMMS application.

See the "Upgrading" section in the PostGIS Manual for information how to upgrade to the latest PostGIS version.

You can use ActivePerl to run postgis_restore.pl. For example:

set PGUSER=postgres
set PGPASSWORD=password
set PGCLIENTENCODING=WINDOWS-1256
set PGPATH=c:\program files\postgresql\8.0
PATH=%PATH%;c:\program files\postgresql\8.0\bin
pg_dump -Fc dcmms > dcmms.dump
dropdb dcmms
postgis_restore.pl "%PGPATH%\share\contrib\lwpostgis.sql" \
dcmms dcmms.dump > restore.log

There are several changes to the data model, see script/update_dcmms_ddl.sql for the details.

The new streamlined GIS data translation system requires one map file per language. Existing map files and include/dcmconfig.php have to be adjusted manually. See the default configuration files for an example how the new system works.

The IdentifyPlugin configuration file is new and has to be adjusted where necessary (Section 2.2.3.1, “Identify Plug-Ins”).

User looking for improved performance should use PostGIS 1.0.0 or better with the definitions in lwpostgis.sql file. As of PostgreSQL 8.0.2, this is not part of the PostgreSQL installer, but a separate installer is available from the internet. Note that there's a known bug with the shapefile loader in PostGIS 1.0.0. The DCMMS installer will use lwpostgis.sql instead of postgis.sql when it is found.

Version 1.0.3 is a bug-fix release that fixes a problem in the update_dcmms_ddl.sql (See bug #1098354 for the details). In addition it provides some documentation how the Cygwin-based PostgreSQL database can be migrated to the native Windows version.

There are two upgrade options from the Cygwin PostgreSQL version to the native Windows one: You can edit an SQL dump file of the database or you can dump only the contents of selected tables. While the first option might be quicker, the second one ensures that you also update to the latest PostGIS version. Following are some hints:

For the Windows installation of DCMMS the most notable change in version 1.0.2 is the use of the native Windows PostgreSQL version 8.0. The Windows release of PostgreSQL includes an updated version of pgAdmin III featuring backup and restore functions. For this reason, the backup and restore functionality has been removed from the DCMMS interface.

When updating to version 1.0.2, make sure that all PostGIS layers in your mapfiles have a dummy user and password entry in the connection line like in Example 2.1, “PostGIS Connection Example”. The password entry was previously omitted.

Make sure that you update your dcmconfig.php as some functions might not work otherwise.

Please follow the steps below to update a Windows installation of DCMMS from version 1.0.0 to 1.0.1.

	Caution
	When you are upgrading from DCMMS 1.0.0 to 1.0.1 and the logon.php page is empty, make sure that you've installed the PEAR module "Log".

The coded values in the standard DCMMS installation cover the needs of all DCMMS users. If your installation does not need some of those values, simply remove them from the respective tables in the database. You can use pgAdmin for this.

	Caution
	When removing coded values, make sure that these have not been used during the data entry. Migrate those critical values to others first.

Materials in DCMMS are simple records in the MaterialDomain table of the dcmms database. Adding a material is as simple as adding a new record. See Section 2.2.4, “Database Side Customization” for the details.

The following query snippet can be used to identify Arabic texts:

where ascii(text) > 200

The dcmms-info mailing list may provide help to solve problems, either through the archives which are available under http://sourceforge.net/mailarchive/forum.php?forum_id=32901. or by sending an email to <dcmms-info@lists.sourceforge.net>.

See also Section 1.4.5, “Mailing Lists”.

The bug and support trackers are available through the DCMMS website, http://dcmms.sourceforge.net .

	Caution
	Please make sure that you look at all bug reports and support requests, not only the open ones. Eventually, a similar problem has occurred before and the support request is already closed.

The uninstallation steps described below will completely remove DCMMS and all of its components.

	Warning
	Make sure that you have backed up your DCMMS data.

If symbols like the hatching of in the area of interest symbol do not show transparent parts as expected, make sure that you use the following configuration line in the LAYER definition of your mapfiles:

TRANSPARENCY ALPHA

This applies especially when overlaying raster data with partially transparent symbols.

When encountering problems after loading shapefiles, use the DCMMS data model to double check that the required fields of all tables are in place.

The PostgreSQL timezone needs to be changed if DCMMS reports the error "Configuration error: PHP time != PostgreSQL time".

pgAdmin can be used to edit postgresql.conf: Select Tools->Server configuration->postgresql.conf from the menu.

Change the timezone value to e.g. GMT-2

Save the configuration: Select File->Save from the menu.

Reload the server configuration: Select File->Reload server from the menu.

Restart the PostgreSQL service.

	Note
	You can check the timezone setting by the following SQL statement: select now() This time needs to equal the system time (as displayed e.g. in the task bar).

	Note
	The error message on the logon page contains the correct timezone setting.

	Important
	Timezone names in Windows and PostgreSQL are different. If your Windows timezone is GMT-3, you'll have to use the PostgreSQL timezone setting GMT+3.

When running PostgreSQL 8.1 and creating login roles using pgAdmin, make sure to check the option "Inherits rights from parent roles". Otherwise the following error messages might occurr when logging on:

Warning: pg_query(): Query failed: ERROR: permission denied for relation causedomain in C:\dcmms\index.php on line 62

Warning: Your data model might be outdated. Please contact your administrator.

Starting with version 8.1.0, PostgreSQL is not creating the OID column by default any more.

Map files used with DCMMS up to version 1.0.5 may have implicitly used the OID column.

To fix the problem locate the layer with the problem. The layer name is mentioned in the error message. For example: Failed to draw layer named 'Landmark'.

Locate the layer in the map file. For example:

DATA "the_geom from landmarkview using SRID=-1"

Add the missing "using unique" statement. For the above example:

DATA "the_geom from landmarkview using unique id using SRID=-1"

Repeat this for all problematic layers

If newly inserted landmarks do not show up in the selection list, most probably they have been digitized outside of the Village or AdministrativeArea boundaries. See Section 2.3.1, “GIS Data Loading” for further information on quality control of Village and AdministrativeArea.

When upgrading a PostgreSQL installation using upgrade.bat, the PostGIS version might be downgraded if PostGIS was first installed through the PostgreSQL installer and later upgraded using the stand-alone installer.

Fix this by installing the latest PostGIS installation again.

If the application fails to connect to the database, check that the "PostgreSQL Database Server" service is up and running on the server. The Windows Services control panel can be reached for example by right-mouse clicking on the Apache Monitor symbol in the taskbar and selecting Open Services from the context menu.

	Tip
	If you're running a firewall, make sure that the firewall is not blocking the connection from PHP to PostgreSQL.

2.8.11.1. PostgreSQL Database Server Service Fails to Start

	Tip
	Try to reboot the machine. Alternatively, log on as administrator and restart the service. The most common startup problem is a leftover postmaster.pid file.

If the PostgreSQL Database Server service fails to start, the Windows event log might provide useful information.

	Caution
	If the PostgreSQL service fails to start make sure that there is no file named c:\program.

Make sure that PHP mapscript is configured as an extension in php.ini.

Make sure that php_mapscript_46.dll exists c:\windows\php\extensions.

Copy php_mapscript_46.dll to c:\windows\php and use depends.exe to verify that all DLL dependencies are fullfilled. depends.exe is available e.g. with the Windows XP Service Pack 2 Support Tools.

If map labels are not displayed properly (e.g. garbage diameters) and you're using tiled shapefiles, check that all your shapefiles have exactly the same table definition. Field name, type and order have to be exactly the same in all your shapefile tiles.

Suppose you have problems restoring a DCMMS database and you are getting the following error message: psql:dcmms-jerash-2004-01-19.sql.lib:34: ERROR: could not load library "/usr/lib/postgis.dll": dlopen: Win32 error 127

Edit your sql file and replace all occurrences of /usr/lib/postgis.dll with $libdir/postgis.dll.

If there are error messages like ERROR: function geometryfromtext(text, integer) does not exist., the text to geometry cast might be missing. It can be recreated with the following SQL command

create cast (text as geometry)
  with function geometry(text) as implicit;

	Warning
	The better way to fix this problem is to use the PostGIS postgis_restore.pl script.

When trying to open a page, the following message appears on the server: Unknown(): Unable to load dynamic 'C:/Program Files/PHP/extensions\php_gettext.dll' - The specified module could not be found.

The following points may help to solve the problem:

See also Section 2.8.12, “FATAL ERROR: PHP extension 'MapScript' is not loaded”.

If you have a PHP error displayed on the page "Warning: Cannot modify header information - headers already sent by ". The solution of this error is changing the output_buffering variable to <B> on </B>.

Apache, PostgreSQL, PHP and some of the installers write log files that are often helpful when troubleshooting.

The level of verbosity of the server logs can often be specified in the server configuration files.

The following locations might contain important log files:

DCMMS requires a long maximum execution time for PHP scripts, MapLab requires a short one (30 seconds).

In order to ovecome this problem, it may be required to use two different php.ini files.

As MapLab is using the .phtml extension for the PHP files, this is possible with the following directive in httpd.conf:

SetEnvIf Request_URI "\.phtml" PHPRC=c:/

Note that this directive has to be inserted after the SetEnvIf module is loaded.

Make sure that the DCMMS application is not indexed by htdig. This will lead to an endless loop and slow down your system.

The htdig package offers as search engine for websites. Please check wether you're running htdig before investigating further.

When upgrading from the Cygwin PostgreSQL version to the native Windows version, it could happen that some fields are too short while restoring because UNIX newlines (1 character) are converted to Windows newlines (2 characters). In this case, the dcmms.dump.ascii file generated by postgis_restore can be edited to adjust the field definitions.

Note that dcmms.dump.ascii has the same encoding as the database (probably UTF-8).

	Note
	This refers to rather old DCMMS versions.