Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

This section describes the preparations necessary to do when doing a customized  production installation, using PostgreSQL as platform database instead of the the default Derby database.

Note!

This section is optional and can be omitted if you are doing the default installation with Derby database.

Prerequisites

  • In order to use PostgreSQL, the admin user and password must be defined.

PostgreSQL Database Instead of the Default Derby Database

Usage Engine supports both Derby or PostgreSQL as platform databases. Derby is the default database and requires no preparations.

PostgreSQL

If you choose to use PostgreSQL as your platform database, you must install your own instance prior to deployment. 

For further information, see https://github.com/helm/charts/tree/master/stable/postgresql.

Configure Usage Engine to Use PostgreSQL

  1. Change the db type to postgresql in the values.yaml file of the usage-engine-private-edition Helm chart:

    usage-engine-private-edition / values.yaml:
    db:
        # derby or postgresql
        type: postgresql
        jdbcUser: mzadmin
        jdbcPassword: mz


    [hide] Line Brake [/hide]

  2. Set the following values in the values.yaml file of the usage-engine-private-edition Helm chart:

    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 need to be defined in clear text (and not encoded using base64) if they are going to be used. Consider using Bootstrapping System Certificates and Secrets - Private Cloud(3.0) 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.


  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.