Page tree

 

Contents:


Initialize

Use the following steps to initialize the databases of the Trifacta® platform.

NOTE: These steps assume that the Trifacta node is the host of these databases. Please modify the following steps if you are connecting to databases on other nodes.

Pre-requisites:

  • The initializing user must have write permissions to the directory from which the commands are executed.
  • The initializing user must have sudo privileges.

PostgreSQL

NOTE: In the following steps, the default version is PostgreSQL 9.6.

  1. For CentOS 7.x, CentOS 8.x:

    sudo /usr/pgsql-9.6/bin/postgresql96-setup initdb
  2. For CentOS 7.x - PostgreSQL 12.3:

    sudo /usr/pgsql-12/bin/postgresql12-setup initdb
  3. For RHEL 7.x, RHEL 8.x:

    sudo /usr/pgsql-9.6/bin/postgresql96-setup initdb
  4. For RHEL 7.x - PostgreSQL 12.3:

    NOTE: This feature is in Beta release.

    sudo /usr/pgsql-12/bin/postgresql12-setup initdb
  5. For Ubuntu 16.04 / 18.04:

    pg_createcluster -d /var/lib/postgresql/9.6/main 9.6 main

MySQL

No additional steps are required to initialize the databases in MySQL.

Set custom database parameters

Use the following steps to set custom database names, usernames, and passwords in the Trifacta platform:

  1. Edit  /opt/trifacta/conf/trifacta-conf.json

  2. For each database, you can review the parameters in the listed area and make modifications as needed.

    NOTE: For each database, you should change the default password. This change must also be applied on the database server. See Change Database Passwords for PostgreSQL . See Change Database Passwords for MySQL.

    NOTE: The type is set to POSTGRESQL by default. Modify the value if you are installing the databases into a different database server.


    DatabaseParameter area
    Main databasewebapp.database.*
    Jobs databasebatch-job-runner.database.*
    Scheduling databasescheduling-service.database.*
    Time-Based Trigger databasetime-based-trigger-service.database.*
    Configuration Service databaseconfiguration-service.database.*
    Job Metadata Service databasejob-metadata-service.database.*
    Artifact Storage Service database

    artifact-storage-service.database.*

    Authorization Service databaseauthorization-service.database.*
    Orchestration Service databaseorchestration-service.database.*
    Optimizer Service databaseoptimizer-service.database.*

    For more information, see Database Parameter Reference.

  3. Make changes in the file as needed and save.

Apply customizations on upgrade

If you have customized database properties, you must apply the edits from the new sample file to the existing configuration file after you have upgrade the Trifacta platform.

If you are using all defaults, you can just overwrite the existing file with the new version's sample file. 

PostgreSQL:

  1. Locate the sample Postgres configuration file:

    /opt/trifacta/bin/setup-utils/db/pg_hba.conf.SAMPLE
  2. If you are upgrading and have customizations in your existing version, you must apply the edits in the above to the following file. Otherwise, overwrite the following file with the above one based on your operating system:
    1. CentOS/RHEL dir: /var/lib/pgsql/9.6/data/pg_hba.conf
    2. Ubuntu dir: /etc/postgresql/9.6/main/pg_hba.conf

  3. From the SAMPLE file, copy the following declarations and paste them into the production pg_hba.conf file above any other declarations:

    NOTE: You can substitute different database usernames and groups for the ones listed below (trifacta and trifacta). These values may be needed for other configuration.

     

    1. Trifacta database:

      local   trifacta         trifacta                               md5
      host    trifacta         trifacta         127.0.0.1/32          md5
      host    trifacta         trifacta         ::1/128               md5
    2. Jobs database:

      local   trifacta-activiti         trifactaactiviti                               md5
      host    trifacta-activiti         trifactaactiviti         127.0.0.1/32          md5
      host    trifacta-activiti         trifactaactiviti         ::1/128               md5
    3. Scheduling database: 

      local   trifactaschedulingservice         trifactaschedulingservice                               md5
      host    trifactaschedulingservice         trifactaschedulingservice         127.0.0.1/32          md5
      host    trifactaschedulingservice         trifactaschedulingservice         ::1/128               md5
    4. Time-based Trigger database:

      local   trifactatimebasedtriggerservice         trifactatimebasedtriggerservice                               md5
      host    trifactatimebasedtriggerservice         trifactatimebasedtriggerservice         127.0.0.1/32          md5
      host    trifactatimebasedtriggerservice         trifactatimebasedtriggerservice         ::1/128               md5
    5. Configuration Service database:

      local   trifactaconfigurationservice         trifactaconfigurationservice                               md5
      host    trifactaconfigurationservice         trifactaconfigurationservice         127.0.0.1/32          md5
      host    trifactaconfigurationservice         trifactaconfigurationservice         ::1/128               md5
    6. Artifact Storage Service database:

      local   trifactaartifactstorageservice         trifactaartifactstorageservice                               md5
      host    trifactaartifactstorageservice         trifactaartifactstorageservice         127.0.0.1/32          md5
      host    trifactaartifactstorageservice         trifactaartifactstorageservice         ::1/128               md5
    7. Job Metadata Service database:

      local   trifactajobmetadataservice         trifactajobmetadataservice                               md5
      host    trifactajobmetadataservice         trifactajobmetadataservice         127.0.0.1/32          md5
      host    trifactajobmetadataservice         trifactajobmetadataservice         ::1/128               md5
    8. Authorization Service database:

      local   trifactaauthorizationservice         trifactaauthorizationservice                               md5
      host    trifactaauthorizationservice         trifactaauthorizationservice         127.0.0.1/32          md5
      host    trifactaauthorizationservice         trifactaauthorizationservice         ::1/128               md5
    9. Orchestration Service database:

      local   trifactaorchestrationservice         trifactaorchestrationservice                               md5
      host    trifactaorchestrationservice         trifactaorchestrationservice         127.0.0.1/32          md5
      host    trifactaorchestrationservice         trifactaorchestrationservice         ::1/128               md5
    10. Optimizer Service database:

      local   trifactoptimizerservice         trifactoptimizerservice                               md5
      host    trifactoptimizerservice         trifactoptimizerservice         127.0.0.1/32          md5
      host    trifactoptimizerservice         trifactoptimizerservice         ::1/128               md5
    11. Save the file.
  4. Restart the databases:

    1. If you are have also restarted the operating system, please execute the following first, followed by the O/S-specific commands:

      NOTE: This command is valid only if the Postgres DB is also hosted in the Trifacta node.


      chkconfig postgresql-9.6 on

      For PostgreSQL 12.3 on CentOS 7:

      chkconfig postgresql-12 on
    2. CentOS/RHEL:

      sudo service postgresql-9.6 start
    3. CentOS/RHEL 7 (PostgreSQL 12.3):

      sudo service postgresql-12 start
    4. Ubuntu:

      sudo service postgresql start

MySQL:

Upgrading MySQL versions is not supported in this release.

Next Steps

  1. If the configuration files indicate that the databases are listening on a port other than the default, this port number must be applied within the Trifacta platform configuration. For more information, see Change Database Port.
  2. If you are using non-default usernames and passwords, they must must be applied within the Trifacta platform configuration. For more information, see Change Database Passwords for PostgreSQL.
  3. When you have completed the above configuration, you can create the databases and their roles (users) and perform additional configuration. See Create Databases and Users.

This page has no comments.