IDempiere/Importing DB Seed Manually

From WikiQSS
Revision as of 21:28, 12 January 2012 by CarlosRuiz (talk | contribs) (breadcrumb)

Table of Contents | Setting up Eclipse | Importing DB Seed Manually | Running iDempiere within Eclipse

Please note this procedure is intended for technical people wanting to configure iDempiere to run in Eclipse, there is an easier mechanism on the installers to create the database.

Let's check the steps to create an idempiere postgres database:

Create adempiere user

sudo su - postgres
psql -U postgres -c "CREATE ROLE adempiere SUPERUSER LOGIN PASSWORD 'adempiere'"
logout

WARNING: Of course this is an insecure password, it is recommended that you set up a proper password for this user account

Create the idempiere database

createdb  --template=template0 -E UNICODE -O adempiere -U adempiere idempiere
psql -d idempiere -U adempiere -c "ALTER ROLE adempiere SET search_path TO adempiere, pg_catalog"

When asked the password please provide the adempiere password that you set up in the previous step.

NOTE: It is possible that you will confront problems related to pg_hba.conf configuration, it's beyond of the scope of this tutorial to solve those problems at this moment, please check and configure proper permissions. Also, this tutorial is intended to work on a postgres installed locally, if your postgres is elsewhere you must use corresponding -h (host) and -p (port) parameters for createdb and psql.

Import the seed

cd /tmp
jar xvf $IDEMPIERE_REPOSITORY/org.adempiere.server-feature/data/seed/Adempiere_pg.jar
psql -d idempiere -U adempiere -f Adempiere_pg.dmp

You must replace $IDEMPIERE_REPOSITORY with the folder of your cloned repository.

Applying additional migration scripts

You can check the latest applied migration script on that seed with this command:

cat $IDEMPIERE_REPOSITORY/org.adempiere.server-feature/data/seed/LAST_SCRIPT_APPLIED_ON_THIS_SEED

Again, replace $IDEMPIERE_REPOSITORY with the folder of your cloned repository.

Now, you must check if there are new migration scripts after the last applied, you can check the migration scripts this way:

ls $IDEMPIERE_REPOSITORY/migration/360lts-release/postgresql

If you find there are unapplied migration scripts then you can apply them with:

psql -d idempiere -U adempiere -f $IDEMPIERE_REPOSITORY/migration/360lts-release/postgresql/810_ProbableFutureMigrationScript.sql

Please check carefully the output of the migration scripts, if you find errors please ask for help on the support forums

You must repeat the previous for each unapplied migration scripts, it's recommended also to take note of the last applied for future reference.

At the end you can run the post-migration processes like this:

cat $IDEMPIERE_REPOSITORY/migration/processes_post_migration/postgresql/*.sql | psql -d idempiere -U adempiere