Initialize

Use the following steps to initialize the databases of the

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

1. For CentOS 7.x:

   Code Block
   sudo /usr/pgsql-9.6/bin/postgresql96-setup initdb

2. For CentOS 6.x, RHEL 6.x:

   Code Block
   sudo service postgresql-9.6 initdb

3. For RHEL 7.x:

   Code Block
   sudo /usr/pgsql-9.6/bin/postgresql96-setup initdb

4. For Ubuntu 14.04 / 16.04:

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

Verify datastyle value

Please verify the datestyle setting for your PostgreSQL instance.

Steps:

1. Execute the following in PostgreSQL:

   Code Block
   trifacta=# show datestyle; DateStyle ----------- ISO, MDY (1 row)

2. If the first value is not ISO, please edit the following file (PostgreSQL 9.6):
   1. RHEL/CentOS:  /var/lib/pgsql/9.6/data/postgresql.conf
   2. Ubuntu:  /etc/postgresql/9.6/main/postgresql.conf

3. Set the datestyle property to the following:

   Code Block
   datestyle = 'ISO,MDY';

4. Save the file. Restart the PostgreSQL instance.

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

1. Edit 

   D s triconf
   path true

   . 

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

   Info
   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.

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

   
   

   Database	Parameter area
   Main database	webapp.database.*
   Jobs database	batch-job-runner.database.*
   Scheduling database	scheduling-service.database.*
   Time-Based Trigger database	time-based-trigger-service.database.*
   Configuration Service database	configuration-service.database.*
   Artifact Storage Service database	artifact-storage-service.database.*
   Job Metadata Service database	job-metadata-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

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:

   Code Block
   /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:

   Info
   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. D s item
      item database

      :

      Code Block
      local trifacta trifacta md5 host trifacta trifacta 127.0.0.1/32 md5 host trifacta trifacta ::1/128 md5

   2. Jobs database:

      Code Block
      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: 

      Code Block
      local trifactaschedulingservice trifactaschedulingservice md5 host trifactaschedulingservice trifactaschedulingservice 127.0.0.1/32 md5 host trifactaschedulingservice trifactaschedulingservice ::1/128 md5

      For more information on scheduling, see Configure Automator. 

   4. Time-based Trigger database:

      Code Block
      local trifactatimebasedtriggerservice trifactatimebasedtriggerservice md5 host trifactatimebasedtriggerservice trifactatimebasedtriggerservice 127.0.0.1/32 md5 host trifactatimebasedtriggerservice trifactatimebasedtriggerservice ::1/128 md5

      For more information on scheduling, see Configure Automator.

   5. Configuration Service database:

      Code Block
      local trifactaconfigurationservice trifactaconfigurationservice md5 host trifactaconfigurationservice trifactaconfigurationservice 127.0.0.1/32 md5 host trifactaconfigurationservice trifactaconfigurationservice ::1/128 md5

   6. Artifact Storage Service database:

      Code Block
      local trifactaartifactstorageservice trifactaartifactstorageservice md5 host trifactaartifactstorageservice trifactaartifactstorageservice 127.0.0.1/32 md5 host trifactaartifactstorageservice trifactaartifactstorageservice ::1/128 md5

   7. Job Metadata Service database:

      Code Block
      local trifactajobmetadataservice trifactajobmetadataservice md5 host trifactajobmetadataservice trifactajobmetadataservice 127.0.0.1/32 md5 host trifactajobmetadataservice trifactajobmetadataservice ::1/128 md5

   8. 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:

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

      
      

      Code Block
      chkconfig postgresql-9.6 on

   2. CentOS/RHEL:

      Code Block
      sudo service postgresql-9.6 start

   3. Ubuntu:

      Code Block
      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 

   D s 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 

   D s 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.