The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server has been deprecated in TeamForge 17.11.

The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server has been deprecated in TeamForge 17.11. In addition, the REPORTS_DATABASE_PORT token has been deprecated in TeamForge 18.3. If you have the TeamForge database and datamart on separate PostgreSQL instances on the same server, follow these instructions to create a dump of both the database and datamart and load them into one PostgreSQL instance on the same server.

  • During TeamForge installation, the REPORTS_DATABASE_PORT token should no longer be used to assign a separate port for datamart.
  • If you have the TeamForge database and datamart running on separate PostgreSQL instances on the same server, create a dump of both the database and datamart and load them into the same PostgreSQL instance.
  1. Do this on the existing TeamForge Application Server where the database and datamart runs on two separate ports.
    1. Make a dump file of your site database.
      su - postgres
      /usr/bin/pg_dumpall > /var/lib/pgsql/9.x/backups/teamforge_data_backup.dmp
      exit
      mkdir /tmp/backup_dir
      cp /var/lib/pgsql/9.x/backups/teamforge_data_backup.dmp /tmp/backup_dir/
      
    2. Make a dump of your datamart.
      /usr/bin/pg_dumpall -p <reports_database_port> > /var/lib/pgsql/9.x/backups/teamforge_reporting_data_backup.dmp
      
  2. Do this on the new TeamForge server.
    1. Recreate the runtime environment (do not provision TeamForge directly).
      teamforge deploy
      
    2. Reload the site database.
      su - postgres
      /usr/bin/psql < /tmp/backup_dir/teamforge_data_backup.dmp
      exit
      
    3. Reload the datamart.
      su - postgres -c "/usr/bin/psql -p <reports_database_port> < /tmp/backup_dir/teamforge_reporting_data_backup.dmp"
      
  3. Provision services.
    teamforge provision