Preface

These instructions will help you connect BellaDati application to a PostgreSQL database.

We recommend using database engines  PostgreSQL 9.5 or PostgreSQL 9.6.

Starting BellaDati version 2.9.3.5 PostgreSQL 9.6 database engine is tested and recommended too.

On this page:

Create and Configure the PostgreSQL Database

host belladati_db belladati_dbuser 0.0.0.0/0 md5

 

  1. Create a database user which BellaDati will connect as (e.g. belladati_dbuser). Remember this database user name, as it will be used to configure BellaDati's connection to this database in subsequent steps. Do not forget to configure the pg_hba.conf file, which controls the database access.

    $ createuser -sDRP belladati_dbuser
  2. Create a database for BellaDati to be used as data warehouse (e.g. belladati_db) with Unicode collation.

    CREATE DATABASE belladati_db WITH ENCODING 'UNICODE' TEMPLATE template0;

    Or from the command-line:

    $ createdb -E UNICODE -O belladati_dbuser belladati_db -T template0
  3. Ensure that the user has permissions to connect to the database, and to create and write to tables in the database.
  4. Check if your database has the plpgsql language. If not, you can define it using this command:

    CREATE LANGUAGE plpgsql

    Or from the command line:

    $ createlang -U belladati_dbuser plpgsql belladati_db

When using the default PostgreSQL configuration file pg_hba.conf, you have to execute this command by connecting via TCP socket:
createlang -h 127.0.0.1 -U belladati_dbuser plpgsql belladati_db

Remember the database name; it will be used to configure BellaDati's connection to the database in subsequent steps.

PostgreSQL configuration

We strongly recommend performing the following PostgreSQL configuration changes in $POSTGRES_HOME/data/postgresql.conf. This example specifies parameters when you run the BellaDati application and database on a single server with 4GB memory. 2GB are allocated for the BellaDati application server running on Java (using the -Xmx parameter). The rest should be available for the operating system and database server.

This configuration may change according to real usage needs.

Example below shows the minimal configuration for single server installation.

Name

Value

Description

Note

max_connections

50

Sets the maximum number of concurrent connections.

 

shared_buffers

512MB

Sets the number of shared memory buffers used by the server.

min 1/4 RAM, 1/2 RAM recommended

temp_buffers

2MB

Sets the maximum number of temporary buffers used by each session.

per session

work_mem

16MB

Sets the maximum memory to be used for query workspaces.

min 16MB, RAM / 128 recommended

maintenance_work_mem

64MB

Sets the maximum memory to be used for maintenance operations.

min 64MB, RAM / 32 recommeneded

max_stack_depth

2MB

Sets the maximum stack depth, in kilobytes.

 

wal_buffers

512kB

Sets the number of disk-page buffers in shared memory for WAL.

 

effective_cache_size

1024MB

Sets the planner's assumption about the size of the disk cache.

RAM / 2 recommended

log_statement

none

Sets the type of statements logged.

 

autovacuumonStarts the autovacuum subprocess. 
autovacuum_analyze_scale_factor0.05Number of tuple inserts, updates, or deletes prior to analyze as a fraction of reltuples. 
autovacuum_analyze_threshold10Minimum number of tuple inserts, updates, or deletes prior to analyze. 
autovacuum_freeze_max_age200000000Age at which to autovacuum a table to prevent transaction ID wraparound. 
autovacuum_max_workers5Sets the maximum number of simultaneously running autovacuum worker processes. 
autovacuum_multixact_freeze_max_age400000000Multixact age at which to autovacuum a table to prevent multixact wraparound. 
autovacuum_naptime15sTime to sleep between autovacuum runs. 
autovacuum_vacuum_cost_delay10msVacuum cost delay in milliseconds, for autovacuum. 
autovacuum_vacuum_cost_limit1000Vacuum cost amount available before napping, for autovacuum. 
autovacuum_vacuum_scale_factor0.1Number of tuple updates or deletes prior to vacuum as a fraction of reltuples. 
autovacuum_vacuum_threshold25Minimum number of tuple updates or deletes prior to vacuum. 

We recommend set the archive_mode parameter to off, using the pg_dump command instead.

Backup and restore

You can backup the BellaDati database using the PostgreSQL dump command:

pg_dump -U user -F c -v -f "path_to_dump/dump.backup" belladati_db

To restore a backup, use the pg_restore command:

pg_restore -v -c -O -d belladati_db -U user path_to_dump/dump.backup

Next steps

Installing BellaDati on Linux - continue  Installing BellaDati on Linux, step "check that default ports"

 

Installing BellaDati WAR

continue installing the BellaDati.war application on your application server as described in: