Purplecube metadata can be hosted either on "embedded repository" or on "external repository".  By default, it is hosted on embedded repository and a recommended option during installation. 

Hosting metadata on embedded repository 

The embedded repository is PostgreSQL database, installed along with Controller installation. Choosing this option at installation will configure it automatically on the server where you are installing the Purplecube Controller.

Hosting metadata on external repository

External repository is the PostgreSQL database which already exists in the client space or newly installed PostgreSQL database outside of where Controller is installed. As a standard practice, two user accounts are required on the repository database - one user account owned by the database/schema to create and manage the repository and the other to create or manage the metadata by Purplecube. Database/user account names can be created as per organization standards. 

Note: To install and setup PostgreSQL database and use to host metadata repository, refer to Installing PostgreSQL Extension.

To install Purplecube, following details of PostgreSQL database are required.

Parameters

Description

Repository Data Base type

PostgreSQL

Data Base Host

IP address of the data base system to be used for Repository

Data Base DB Port

Port on which database system accepts connection for Repository

Data Base DB name

Database name to be used for Repository

Data Base DB user

Dedicated User (Primary account) on DB for Repository

Data Base DB password

User password to connect to DB.

1. Create a dedicated database preferably 'direpdb' and add a primary user. The user must have privileges to login and create roles and other users on the database.

2. Create a schema. As a best practice use the name 'direp' and it should be capable of making the secondary user as its owner. You may choose to inherit superuser privileges for this primary user depending on your requirement.

3. With the help of primary user, create a user 'di' who can login to the repository database and can manage the metadata of the repository. The user should be privileged to CREATE and UPDATE database objects within the repository database.

4. Search_path variable value should be set to direp as a best practice.