Migrating to Postgres: Steps and Requirements for Pulse 7.2+

Pulse: 7.2.+

Pulse now supports Postgres database from this version onwards. This article describes the steps involve to migrate your existing database into Postgres and things to check out.

Prerequisites

This assumes that you already have an existing Postgres database server running. It is recommended to prepare a fresh database, with a Postgres username and password with full admin access into this database.

Preparation

Stop Pulse services
Open Pulse.cfg and look for the following section,

[Postgres]
JDBCURL = 
UserName = 
Password =

If they are not yet there, you can add them manually.

Update the above section with your Postgres database information and credentials

Migrating H2

There is not much to do except to start the Pulse services. Once Pulse server has started and it detected Postgres and H2, it will then automatically migrate data from H2. Afterwards, it will rename the docs.h2.db file into docs-topg.h2.db

Migrating MSSQL Server

Similar to H2, there is not much to do. Once it starts migration, it will create a simple log file under db folder named pulse-migration-db_sqlserver-to-db_postgres.info. This is what it will then check next time Pulse starts up to see if an existing MSSQL Server configuration has already been migrated.