Create a user named "dnpwml" by using psql command.

Expand the file you transferred by FTP. In this example, it assumes that the file exists in "/home/guest" directory.
It assumes that "/tmp" is a temporary directory.
* Use "root" user for this operation.

After the expansion, a directory named "dnpwml" is created in "/tmp" directory.

Change the owner of "/tmp/dnpwml" directory to the user for running Apache.
In this example, the user is "apache" and the group is "apache".

First of all, move the static contents of Denbun to the document root of Apache.
In this example, it is "/var/www/html".
The following directory is the static contents of Denbun.
(1) dnpwmlroot directory (gif images, JavaScripts)

This directory exists in "dnpwml" directory you expanded.

Next, move "dnpwml" directory itself to the cgi directory of Apache.
In this example, it is "/var/www/cgi-bin".

Restore the Denbun database from the database file (dnpwmldb.pgdmp) by using pg_restore command. Since the database file is included in the install program, the file exists in "/var/www/cgi-bin/dnpwml" directory.
* Use "postgres" user for this operation.

* If a user named "postgres" does not exist in PostgreSQL, "ERROR: role " postgres" does not exist" error occurs while restoring. Even though the error occurred, there is no problem.

The following Apache configuration should be done.
(1) Set the environment variables for Denbun and PostgreSQL
Configure these variables in Apache configuration file (httpd.conf). The configuration file is included in "/etc/httpd/conf" directory if the Apache is packaged in a Redhat Enterprise Linux. Use an editor such as vi to edit the file.

Use SetEnv directive to add variables. You can add them at the end of the file.

Make sure the configuration and then restart Apache.

VACUUM and timeout settings should be done here.

VACUUM setting
In normal PostgreSQL operation, tuples that are deleted or obsoleted by an update are not physically removed from their table; they remain present until a VACUUM is done. Therefore it's necessary to do VACUUM periodically, especially on frequently-updated tables (Without vacuuming, you may have performance problem).

With autovacuum, you can automate the execution of VACUUM and ANALYZE commands. The settings of autovacuum described in the database configuration file (postgresql.conf). The file exists in the data directory (in this example, /var/pgsql/data). Use an editor such as vi to edit the file.

Open the database configuration file and use stats_start_collector and stats_row_level directives in RUNTIME STATISTICS section, and autovacuum directive in AUTOVACUUM PARAMETERS section to configure it.
Uncomment them and set them to "on" because these directives are commented out in the default.

Timeout settings
Without specifying the timeout value, the server will be occupied when queries hit many results.
The settings of the timeout described in the database configuration file (postgresql.conf).
Open the database configuration file and use statement_timeout directive in CLIENT CONNECTION DEFAULTS section to configure it.
The directive is commented out in the default.

In this example, the timeout is set to 30 seconds.

After the setting database configuration file, restart PostgreSQL.

Use rm command to delete the destination directory.
(If you type "\" just before "rm", no confirmation messages displayed)

Uninstalling Denbun
Delete the directories for Denbun program and static contents.

Delete the Denbun database and user
Use the following command to delete the database and user that were created by the installation process of Denbun POP Version.
* Use "postgres" user for this operation.

Remove the settings for scheduler
Remove the scheduler settings configured by the installation process of Denbun POP Version.
* Use "root" user for this operation.

The cron settings for Apache will be displayed. Delete the line for "dnpscheduler.sh" and save it and quit.

e.g.)
30 8 * * 1,2,3,4,5 /var/www/cgi-bin/dnpwml/dnpscheduler.sh
|
Delete the line from "cron" file.