Configuring PostgreSQL with DevTest After Install
search cancel

Configuring PostgreSQL with DevTest After Install

book

Article ID: 213609

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

 
 
 

Currently IAM, Enterprise Dashboard and Registry connect to Derby.

Need configuring all of these components to connect to PostgreSQL.

Environment

All supported DevTest releases.

Resolution

The PostgreSQL database must provide collation and characters set supporting UTF-8, that is, the default encoding that we support and tested.

You must use lowercase table names for PostgreSQL to work.

NOTE: When upgrading Identity Access Managers to DevTest version 10.8.1 from versions 10.5 or 10.6 with a PostgreSQL database, ensure that you perform the following post-installation steps: (This file is with the installer)

1. Perform an in-place upgrade installation.
2. Do not start the Identity Access Manager service immediately.
3. Replace the org.keycloak.keycloak-model-jpa-25.0.6.jar file located at  <DevTestHome>/IdentityAccessManager/lib/lib/main/.
4. Start the Identity Access Manager service.

 

NOTE: It is assumed there is a familiarity with PostgreSQL or can confer with a DBA for guidance.

DevTest delivers a PostgreSQL JDBC driver with the product.  

Bring down all DevTest services.

 

Configuring PostgreSQL for IdentIty Access Manager (IAM)

1. Edit file ${IAM_HOME}iam.properties.
2. Configure the file using this example (this is a current working example)

iam.db.vendor=postgres
iam.db.url=jdbc:postgresql://[server]:5432/database_name 
 or
iam.db.url=jdbc:postgresql://[server]:5432/database_name?schema_name
iam.db.user=postgres
iam.db.password=<password in plain text, once IAM is started the password will be encrypted>

3. Start the IAM Service.

 

Configuring PostgreSQL for the Enterprise Dashboard (EDB)

1. Edit file DEVTEST_HOME/dradis.properties.
2. Configure the file using this example (this is a current working example)

## Should we start the internal Derby DB instance in the Enterprise Dashboard?
dradis.db.internal.enabled=false

## ==================================================================================
## PostgreSQL
## ==================================================================================
dradis.db.driverClass=org.postgresql.Driver
dradis.db.url=jdbc:postgresql://[server]:5432/database_name
or
dradis.db.url=jdbc:postgresql://[server]:5432/database_name?schema_name
dradis.db.user=postgres
dradis.db.password=<password in plain text, once the EDB is started the password will be encrypted>

3. Start the Enterprise Dashboard service.

 

Configuring PostgreSQL for the Registry

1. Edit file DEVTEST_HOME/site.properties.
2. Configure the file using this example (this is a current working example)

## ==================================================================================
## PostgreSQL
## ==================================================================================
lisadb.pool.common.driverClass=org.postgresql.Driver
lisadb.pool.common.url=jdbc:postgresql://[server]:5432/database_name

or

lisadb.pool.common.url=jdbc:postgresql://[server]:5432/database_name?schema_name
lisadb.pool.common.user=postgres
lisadb.pool.common.password=<password in plain text, once the Registry is started the password will be encrypted>

## ==================================================================================
## Should the internal Derby DB instance in the Registry be started?
## ==================================================================================
lisadb.internal.enabled=false

3. Start the Registry service.

 

Example of the different connection types:

 

 

Additional Information

NOTE: When starting IAM, Enterprise Dashboard or Registry, if you get an error similar to this:

"Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "[IP address]", user "postgres", database "REG_DB", SSL off" you are missing some configuration on the PostgreSQL database side. 

Please refer to this Knowledge Document: Resolving error: Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "{{IP address}}", user "postgres", database "IAM_X_X_0", SSL off