Page tree

 

If needed, you can change the default port used by the database instance for the Trifacta® platform. Please complete the following commands to avoid conflicts between versions.

If you are changing the port within the database, those changes must be applied through your database system by an administrator. To limit downtime, port number changes should be done at the same time in the platform and the database. For more information, please see the documentation included with your database product.

NOTE: By default, PostgreSQL and the platform use port 5432 for communication. If that port is not available at install/upgrade time, the next available port is used, which is typically 5433. This change may occur if a previous version of PostgreSQL is on the same server. When a non-default port number is used, the platform must be configured to use it. For more information, see Change Database Port.

NOTE: By default, the ports for all databases are set to the default database port for PostgreSQL. For more information on the default database ports, see System Ports.

Steps:

  1. Stop the Trifacta services. For more information, see Start and Stop the Platform.

  2. Stop the database server. 

  3. Change the port number in the database administration console. For more information, see the product documentation provided with your database distribution.

  4. Start the database server. Verify that it is listening on the new port number.
  5. You can apply this change through the Admin Settings Page (recommended) or trifacta-conf.json. For more information, see Platform Configuration Methods. Locate the following properties and modify as needed. The default PostgreSQL port number is listed below:
    1. Trifacta database:

      "webapp.db.port" = 5432;
    2. Jobs database:

      "batch-job-runner.db.port" = 5432;
    3. Scheduling database:

      "scheduling-service.database.port" = 5432;
    4. Time-based trigger database: 

      "time-based-trigger-service.database.port" = 5432;
  6. Save your changes and restart the platform.
  7. Verify that you can login and run a simple job. See Verify Operations.

This page has no comments.