...
This section describes the preparations necessary to do when doing a customized production installation, using PostgreSQL as a platform database instead of the default Derby database.
...
Note!
This section is optional and can be omitted if you are doing the default installation with the Derby database.
Prerequisites
In order to use PostgreSQL, the admin user and password must be defined.
PostgreSQL Database Instead of the Default Derby Database
...
Configure Usage Engine to Use PostgreSQL
Change the db type to postgresql in the values.yaml file of the usage-engine-private-edition Helm chart:
Code Block usage-engine-private-edition / values.yaml: db: # derby or postgresql type: postgresql jdbcUser: mzadmin jdbcPassword: mzSet the following values in the values.yaml file of the usage-engine-private-edition Helm chart:
Code Block postgres: adminPassword: <admin password> #postgres superuser password, leave blank if platform is not allowed to create database and users adminUsername: <admin username> #postgres superuser, leave blank if platform is not allowed to create database and users mzownerPassword: <mzowner password> #Password to owner of all tables in postgres db: <name of database> #postgres DB name port: 5432 #postgres DB connection port host: <host name> #postgres DB hostnam
...
Note!
The passwords In the values.yaml file:
...
jdbcPassword, adminPassword and mzownerPassword are not shown in clear text (encoded using base64). If they are going to be used in the file, you will need to use the passwords in clear text. Consider
...
...
...
3) instead.
PostgreSQL when admin user and password are not defined
The subsections describe the additional installation of PostgreSQL that is necessary when using PostgreSQL as a database and admin user and password are not defined.
| Child pages (Children Display) |
|---|