...

For more information, see Install Databases in the Databases Guide.

Modify pg_hba.conf (PostgreSQL only)

For PostgreSQL, the Configuration Service database Any new databases must be referenced in pg_hba.conf.

Steps:

1. Locate the sample Postgres configuration file:

source /opt/trifacta/conf/env.sh
cd /opt/trifacta/tools/config-service-tools
node src/create-imports.js

/opt/trifacta/bin/setup-utils/db/pg_hba.conf.SAMPLE

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

Create DBs

1. Run the following script, which creates any new databases and users and roles for accessing them.

   1. PostgreSQL:

      Code Block
      sudo /opt/trifacta/bin/setup-utils/db/trifacta-create-postgres-roles-dbs.sh

   2. MySQL:

      Code Block
      /opt/trifacta/bin/setup-utils/db/trifacta-create-mysql-users-dbs.sh -u <MySql_admin_username> -w <MySql_admin_password>

   3. See Create Databases and Users in the Databases Guide.
2. Restart the databases.

Import configuration values

The Configuration Service database must be loaded with the exported configuration values. For more information on the specific properties that have been migrated, see Changes to Configuration in the Release Notes Guide.

Steps:

1. If you have not done so already, create a backup of the file containing the migrated parameter values (migrated_triconf_values.json) outside of the 

   D s item
   item install directory

   . 

2. Start the platform:

   Code Block
   sudo service trifacta start

3. Import the configuration values that you exported before upgrading as the 

   D s defaultuser
   Type os.user Full true

   .

   Code Block
   source /opt/trifacta/conf/env.sh /opt/trifacta/services/configuration-service/bin/import.sh -f /opt/trifacta/tools/config-service-tools/resources/migrate.conf

4. (optional) You can modify post-upgrade any of the values in the Configuration Service. Some of these values are available through the Workspace Admin page of the application.

   Info
   NOTE: Changing these values after import overwrites the imported values.

   Code Block
   vi /opt/trifacta/tools/config-service-tools/resources/migrated_triconf_values.json /opt/trifacta/services/configuration-service/bin/import.sh -f /opt/trifacta/tools/config-service-tools/resources/migrate.conf

5. You should perform a backup of the Configuration Service database after completing the import. See Backup and Recovery in the Admin Guide.

Merge Customized Configuration Files

Steps:

1. Review the following directories and files for .rpmnew versions:

   Code Block
   /opt/trifacta/conf/env.sh /opt/trifacta/conf/nginx.conf /opt/trifacta/conf/supervisord.conf /etc/init.d/trifacta /opt/trifacta/pkg3p/tripache/conf/conf.d/*

2. Configuration settings from the old files must be explicitly merged into the new files (*.rpmnew). 
3. Remove old files from 

   D s item
   item install directory

   :
   1. Create a directory outside of the 

      D s item
      item install directory

      .

   2. Move all of the config files from the previous version into this directory.

      Info
      NOTE: Do not leave the old config files in the install directory. There should not be multiple configuration files of the same kind.

   3. Rename these old config files outside of the directory to include a .backup extension. You could also put the version number of the config file. 
4. The .rpmnew extension must be removed from the new files.
5. Your previous configuration should be carried forward into the new version.

Next Steps

While the platform can now start, you should avoid doing so until have you completed all required steps in this guide.