|
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 |
belladati_db
) with Unicode collation.
CREATE DATABASE belladati_db WITH ENCODING 'UNICODE'; |
$ createdb -E UNICODE -O belladati_dbuser belladati_db |
CREATE LANGUAGE plpgsql |
$ createlang -U belladati_dbuser plpgsql belladati_db |
When using default PostgreSQL configuration file |
Remember this database name, as it will be used to configure BellaDati's connection to this database in subsequent steps. |
Skip this step if you are using BellaDati virtual applicance distribution. BellaDati virtual appliance includes the PostgreSQL JDBC driver.
lib/
directory of your application server.We are strongly recommending to perform the following PostgreSQL configuration changes in $POSTGRES_HOME/data/postgresql.conf
. This example specifies parameters when you are running BellaDati and database on a single server with 4GB memory. 2GB of the are allocated for BellaDati application server running on JAVA (the -Xmx parameter). The rest should be available for operating system and database server.
Name |
Value |
Note |
---|---|---|
max_connections |
50 |
|
shared_buffers |
512MB |
min 1/4 RAM |
temp_buffers |
2MB |
per session |
work_mem |
10MB |
per client connection |
maintenance_work_mem |
64MB |
|
max_stack_depth |
2MB |
|
wal_buffers |
512kB |
|
effective_cache_size |
512MB |
|
We are recommending set the |
|
The database user, which BellaDati uses for establishing the database connection |
|
Database user password |
|
Server name or IP address of the machine, where the database is running |
|
The database name |
Do not forget to configure your PostgreSQL database instance's |
Continue configuring BellaDati WAR for your application server as described on: