In this single server setup, the following TeamForge services run on the TeamForge Application Server (server-01).
- TeamForge Application Server (ctfcore)
- Database Server (ctfcore-database and ctfcore-datamart)
- Codesearch Server (codesearch)
- Mail Server (mail)
- ETL Server (etl)
- Git Integration Server (gerrit and gerrit-database)
- SCM Integration Server (subversion and cvs)
- Search Server (search).
- TeamForge EventQ Server (eventq, mongodb, redis and rabbitmq)
- TeamForge CLI Server (cliserver)
- Review Board (reviewboard, reviewboard-database, reviewboard-adapter)
- CLI Server (cliserver)
- TeamForge Baseline (baseline, baseline-database, baseline-post-install)1
- TeamForge Webhooks-based Event Broker (webr webr-database)2
Dos and Don’ts
Here’s a list of dos, don’ts and points to remember when you install or upgrade TeamForge.
Dos
- Understand TeamForge installation requirements and plan your installation or upgrade.
- Get your TeamForge license key and keep it handy.
- Verify your basic networking setup before installing or upgrading TeamForge. See Set Up Networking for TeamForge.
- Look for new or modified
site-options.conf
tokens and update yoursite-options.conf
file as required during the upgrade process. See Site Options Change Log. - Set up a TeamForge Stage Server before you upgrade your Production Server.
- Stop TeamForge services on all servers in a distributed setup while upgrading to TeamForge 19.0.
- Uninstall hot fixes and add-ons, if any, before you start the TeamForge 19.0 upgrade procedure.
-
As a result of changes to the logging framework in Java 9, the
PrintGCDetails
andPrintGCTimeStamps
logging options are no longer supported. Remove these options from the following tokens while upgrading to TeamForge 18.1 or later. TeamForge provision fails otherwise.- JBOSS_JAVA_OPTS
- PHOENIX_JAVA_OPTS
- INTEGRATION_JAVA_OPTS
- ETL_JAVA_OPTS
- ELASTICSEARCH_JAVA_OPTS
Don'ts
- Do not customize your operating system installation. Select only the default packages list.
- While upgrading TeamForge, whether in place or on new hardware, always reuse the old
site-options.conf
file and make changes as necessary. Do not try to start with a newsite-options.conf
file. Reusing the oldsite-options.conf
avoids many potential problems, particularly around the management of usernames and passwords. - Do not manually modify TeamForge-managed site option tokens such as the
AUTO_DATA
token. See AUTO_DATA for more information. -
If you are creating symlinks, note that you must create symlinks only to the TeamForge data directory (
/opt/collabnet/teamforge/var
). You should not create symlinks to TeamForge application directories (such as/opt/collabnet
).
Points to Remember
- Installing or upgrading TeamForge needs root privileges. You must log on as root or use a root shell to install or upgrade TeamForge.
- SSL is enabled by default and a self-signed certificate is auto-generated. However, you can use a few
site-options.conf
tokens to adjust this behavior. To generate the SSL certificates, see Generate SSL Certificates. - For the ETL service to run as expected in a distributed TeamForge installation, all servers must have the same time zone.
- If you have Git integration on a separate server, both TeamForge and Git servers must have their time and date synchronized. Similarly, if Subversion is on a separate server, both TeamForge and Subversion servers must have their time and date synchronized.
- While you can run both EventQ and TeamForge on the same server, CollabNet recommends such an approach only for testing purposes. It’s always recommended to run EventQ on a separate server for optimal scalability.
- It’s highly recommended that you install the TeamForge Baseline services on a separate server as the baselining process can consume considerable CPU and database resources. For more information, see Install TeamForge in a Distributed Setup.
- No backup is required for same hardware upgrades. However, you can create a backup as a measure of caution. See Back up and Restore TeamForge for more information.
- Always use compatible JDBC drivers meant for specific database versions. See JDBC Drivers Reference for more information. Also see: Why do ETL jobs fail post TeamForge upgrade?
- You can run the initial load job any time after the installation of TeamForge. We recommend that you run it before you hand over the site to the users. For more information, see ETL Initial Load Jobs.
- SOAP50 APIs and event handlers are no longer supported in TeamForge 16.10 and later. Use the latest TeamForge SOAP/REST APIs.
- TeamForge 19.0 installer expects the system locale to be
LANG=en_US.UTF-8
. TeamForge create runtime (teamforge provision
) fails otherwise. - Installing TeamForge with service-specific FQDNs (instead of machine-specific host/domain names) is highly recommended so that you will be able to change the system landscape at a later point in time without having any impact on the URLs (in other words, end users do not have to notice or change anything). For example, you can create FQDNs specifically for services such as Subversion, Git, mail, Codesearch and so on. For more information, see Service-specific FQDNs.
- All such service-specific FQDNs must belong to a single sub domain and it is recommended to create a new sub domain for TeamForge.
- If you are using service-specific FQDNs
- A wildcard SSL cert is required. SNI SSL cert cannot be used.
- When SSL is enabled and no custom SSL certificates are provided, a self-signed wildcard cert is generated for the sub domain.
- When SSL is enabled and a custom SSL certificate is provided, the CN of the certificate is verified to be a wildcard CN.
- You cannot have a separate PUBLIC_FQDN for EventQ.
- The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server is being deprecated in TeamForge 17.11. If you have TeamForge database and datamart on separate PostgreSQL instances on the same server and if you are upgrading on a new hardware, you must Create a Single Cluster for Both Database and Datamart while upgrading to TeamForge 17.11 or later.
- While upgrading TeamForge-Git integration servers, it is important that Git master and slave servers are upgraded to the same version of TeamForge-Git integration. On sites with Git Replica Servers, you must upgrade the Git Replica Servers first and then upgrade the master Git servers.
- EventQ is not installed by default when you install TeamForge 19.0 or later. However, you can install EventQ separately, if required. EventQ installation instructions are included in the TeamForge installation/upgrade instructions, which you can ignore if EventQ is not required for you.
Do this before you stop TeamForge while upgrading to TeamForge 18.2 or later versions.
Get value of SUBVERSION_REPOSITORY_BASE
from the /opt/collabnet/teamforge/runtime/conf/runtime-options.conf
file of your existing TeamForge server and run the following command:
chmod -R 775 $SUBVERSION_REPOSITORY_BASE
Where $SUBVERSION_REPOSITORY_BASE
is the path tp the /svnroot
directory.
This is required to work around the unusually long time taken to migrate the Subversion data during the first run of the teamforge provision
command.


Uninstall Custom Event Handlers, Hot Fixes, Add-ons and Review Board
- Log on to the TeamForge Application Server (server-01).
- SOAP 50 is no longer supported. Back up all your custom event handlers and remove all the event handler JAR files before starting your TeamForge upgrade process.
- Go to My Workspace > Admin.
- Click System Tools from the Projects menu.
- Click Customizations.
- Select the custom event handler and click Delete.
Tip: Post upgrade, you can add custom event handlers again from the backup while making sure that you don’t have SOAP50 (deprecated) library used.
- Uninstall hotfixes and add-ons, if any, installed on your site.
Create a Database Dump
TeamForge 19.0 supports PostgreSQL 11.1. If you are upgrading from TeamForge 17.1 or earlier versions, PostgreSQL 9.2/9.3 data cannot be migrated automatically. To migrate manually:
- Create a dump of your existing database.
- Stop the site.
- Remove the PostgreSQL cluster in
/var/lib/pgsql/9.x
. - Run ‘teamforge deploy’.
- Restore your database by loading the dumps.
- Run the ‘teamforge provision’ command to do the migration and start the site.
- Create a dump of your site’s database if and only if you are upgrading from TeamForge 17.1 or earlier versions.
su - postgres /usr/bin/pg_dumpall > /opt/collabnet/teamforge/var/pgsql/9.3/backups/teamforge_data_backup.dmp exit mkdir /tmp/backup_dir cp /opt/collabnet/teamforge/var/pgsql/9.3/backups/teamforge_data_backup.dmp /tmp/backup_dir/
- Remove the PostgreSQL cluster in
/var/lib/pgsql/9.3
.mv /var/lib/pgsql/9.3 /var/lib/pgsql/9.3_old
yum upgrade
-
Stop TeamForge.
- If you are upgrading from TeamForge 16.7 or earlier releases:
/etc/init.d/collabnet stop
- If you are upgrading from TeamForge 16.10, 17.1, or 17.4 releases:
/opt/collabnet/teamforge/bin/teamforge stop
- If you are upgrading from TeamForge 17.8 or later releases:
teamforge stop
- If you are upgrading from TeamForge 16.7 or earlier releases:
-
Stop EventQ.
- If you are upgrading from TeamForge 16.3:
/etc/init.d/orchestrate stop
- If you are upgrading from TeamForge 16.7, 16.10, or 17.1 release:
/etc/init.d/eventq stop /etc/init.d/collabnet-rabbitmq-server stop /etc/init.d/collabnet-mongod stop
- If you are upgrading from TeamForge 17.4 release:
/opt/collabnet/teamforge/bin/teamforge stop
- If you are upgrading from TeamForge 17.8 or later releases:
teamforge stop
- If you are upgrading from TeamForge 16.3:
-
Upgrade the operating system packages.
yum upgrade
Configure the TeamForge Installation Repository
-
TeamForge Installation Repository Configuration for Sites with Internet Access
- Contact the CollabNet Support and download the TeamForge 19.0 installation repository package to
/tmp
. - Install the repository package.
yum install -y /tmp/collabnet-teamforge-repo-19.0-0-noarch.rpm
- Refresh your repository cache.
yum clean all
TeamForge Installation Repository Configuration for Sites without Internet Access
- Contact the CollabNet Support to get the auxiliary installer package for TeamForge 19.0 disconnected installation and save it in
/tmp
.- RHEL/CentOS 6.10 64 bit:
CTF-Disconnected-media-19.0.573-1320.rhel6.x86_64.rpm
- RHEL/CentOS 7.6 64 bit:
CTF-Disconnected-media-19.0.573-1320.rhel7.x86_64.rpm
- In addition to the above CentOS 7.6 64 bit RPM package, you must get the following CentOS 7.6 compatibility RPM, which is required for TeamForge 19.0 disconnected media installation on CentOS 7.6 profile:
compat-ctf-dc-media-1.2-1.el7.noarch.rpm
.
- RHEL/CentOS 6.10 64 bit:
- Unpack the disconnected installation package.
rpm -Uvh <package-name>
- Unpack the
compat-ctf-dc-media-1.2-1.el7.noarch.rpm
package if you are installing TeamForge 19.0 on CentOS 7.6.rpm -ivh compat-ctf-dc-media-1.2-1.el7.noarch.rpm
-
If not mounted already, mount the RHEL/CentOS installation DVD.
The DVD contains the necessary software and utilities required for installing TeamForge without internet access. In the following commands, replace “cdrom” with the identifier for your server’s CD/DVD drive, if necessary.
cd /media/ mkdir cdrom mount /dev/cdrom ./cdrom/
If there are any spaces in the automount, unmount it first and mount it as a filepath, with no spaces.
- Create a yum configuration file that points to the RHEL/CentOS installation DVD.
vi /etc/yum.repos.d/cdrom.repo
Here’s a sample yum configuration file.
[RHEL-CDROM] name=RHEL CDRom baseurl=file:///media/cdrom/Server/ gpgfile=file:///media/cdrom/RPM-GPG-KEY-redhat-release enabled=1 gpgcheck=0
- Verify your yum configuration files.
yum list httpd yum list apr
- Contact the CollabNet Support and download the TeamForge 19.0 installation repository package to
Upgrade the TeamForge Services
- Upgrade TeamForge.
yum install teamforge
Install the Baseline packages.
yum install teamforge-baseline
Install the TeamForge Webhooks-based Event Broker.
yum install teamforge-webr
- Run the following command to upgrade the Binary application packages. This is required if and only if you are upgrading from TeamForge 16.10 (or earlier) to TeamForge 17.8 (or later).
yum install cn-binary
Set up the site-options.conf File
- Set up the
site-options.conf
file.Important: See Site options change log for a list of site option changes. While upgrading to a latest TeamForge release, make sure that obsolete site option tokens, if any, are removed from thesite-options.conf
file of the TeamForge version you are upgrading to.vi /opt/collabnet/teamforge/etc/site-options.conf
host:SERVICES Token
server-01:SERVICES = ctfcore ctfcore-database ctfcore-datamart mail etl search codesearch subversion cvs eventq redis mongodb rabbitmq cliserver gerrit gerrit-database binary binary-database reviewboard reviewboard-database reviewboard-adapter baseline baseline-database baseline-post-install webr webr-database
host:PUBLIC_FQDN Token
server-01:PUBLIC_FQDN = my.app.domain.com
Note: You cannot have a separate PUBLIC_FQDN for EventQ.MONGODB_APP_DATABASE_NAME
Set the
MONGODB_APP_DATABASE_NAME
token with EventQ’s database name in thesite-options.conf
file. Do this if and only if you are upgrading from TeamForge 17.1 or earlier to TeamForge 17.4 or later.MONGODB_APP_DATABASE_NAME=orchestrate
Save the
site-options.conf
file.For further customization of your site configuration (SSL settings, password policy settings, PostgreSQL settings, LDAP settings and so on):
SSL Tokens
SSL is enabled by default and a self-signed certificate is auto-generated. Use the following tokens to adjust this behavior.
SSL_CERT_FILE= SSL_KEY_FILE= SSL_CHAIN_FILE=
- To generate the SSL certificates, see Generate SSL certificates.
- Have the custom SSL certificate and private key for custom SSL certificate in place and provide their absolute paths in these tokens. SSL_CHAIN_FILE (intermediate certificate) is optional.
- You can also encrypt the data traffic between the application and database servers and between the ETL and datamart servers in a distributed setup. Use the [DATABASE_SSL][siteoptiontokens.html#DATABASE_SSL] token to do that. See Encrypt Database Network Traffic.
Password Tokens
- TeamForge 7.1 and later support automatic password creation. See AUTO_DATA for more information.
-
Set the REQUIRE_PASSWORD_SECURITY token to
true
to enforce password security policy for the site.If the token REQUIRE_PASSWORD_SECURITY is enabled, then set a value for the token, PASSWORD_CONTROL_EFFECTIVE_DATE.
Warning: The Password Control Kit (PCK) disables, deletes or expires user accounts that don’t meet the password security requirements starting from the date set for thePASSWORD_CONTROL_EFFECTIVE_DATE
token. If a date is not set, the PCK disables, deletes or expires user accounts immediately. See PASSWORD_CONTROL_EFFECTIVE_DATE for more information.You can also set the following tokens to enforce a more stricter password policy:
- If the token REQUIRE_RANDOM_ADMIN_PASSWORD is already set to
true
, then set the token ADMIN_EMAIL with a valid email address.ADMIN_EMAIL=root@{__APPLICATION_HOST__}
- If you have LDAP set up for external authentication, you must set the REQUIRE_USER_PASSWORD_CHANGE site options token to
false
. - Verify and update the list of non-expiring TeamForge user accounts (password never expires).
USERS_WITH_NO_EXPIRY_PASSWORD=admin,nobody,system,scmviewer,scmadmin
Prevent Cross-site Scripting
An attacker could potentially upload an HTML page to TeamForge that contains active code, such as JavaScript. This active code would then be executed by clients’ browsers when they view the page, which can harm the system.
To prevent an attack of this sort, you can specify whether or not HTML code is displayed in TeamForge. This flag applies to all documents, tracker, task, and forum attachments, and files in the file release system.
Set the SAFE_DOWNLOAD_MODE token according to your requirements. For more information, see SAFE_DOWNLOAD_MODE.
PostgreSQL Tokens and Settings
Make sure the PostgreSQL tokens in the
site-options.conf
file are set as recommended in the following topic: What are the right PostgreSQL settings for my site?JAVA_OPTS
Configure the JBOSS_JAVA_OPTS
site-options.conf
token. See JBOSS_JAVA_OPTS.Note: All JVM parameters but-Xms1024m
and-Xmx2048m
have been hard-coded in the TeamForge core application. You need not manually configure any other parameter (such as-XX:MaxMetaspaceSize=512m
-XX:ReservedCodeCacheSize=128M
-server -XX:+HeapDumpOnOutOfMemoryError
-Djsse.enableSNIExtension=false
-Dsun.rmi.dgc.client.gcInterval=600000
-Dsun.rmi.dgc.server.gcInterval=600000
) in the site-options.conf file.TeamForge 18.1 (and later) supports Java 9. As a result of changes to the logging framework in Java 9, the
PrintGCDetails
andPrintGCTimeStamps
logging options are no longer supported. Remove these options from the following tokens while upgrading to TeamForge 18.1 or later.- JBOSS_JAVA_OPTS
- PHOENIX_JAVA_OPTS
- INTEGRATION_JAVA_OPTS
- ETL_JAVA_OPTS
- ELASTICSEARCH_JAVA_OPTS
TeamForge provision fails on sites that use these options post upgrade to TeamForge 18.1.
Save the
site-options.conf
file. -
Deploy TeamForge and reload the PostgreSQL dump. Do this if and only if you are upgrading from TeamForge 17.1 or earlier versions (with PostgreSQL 9.3/9.2).
Warning: You must move the PostgreSQL 9.x directory (mv /var/lib/pgsql/9.x /var/lib/pgsql/9.x_old
) after reloading the database dump, failing which theteamforge provision
command will not be successful.teamforge deploy
su - postgres psql < /tmp/backup_dir/teamforge_data_backup.dmp (for TeamForge database) psql -p 5632 < /tmp/teamforge_reportsdata_backup.dmp (for reporting database)
Provision Services
-
Do this if and only if you have EventQ integration and are upgrading from TeamForge 17.1 or earlier to TeamForge 19.0.
Copy the
/opt/collabnet/rabbitmq/var
and/opt/collabnet/mongodb/data
directories to/opt/collabnet/teamforge/var/rabbitmq
and/opt/collabnet/teamforge/var/mongodb
directories respectively.cp -R /opt/collabnet/rabbitmq/var /opt/collabnet/teamforge/var/rabbitmq cp -R /opt/collabnet/mongodb/data /opt/collabnet/teamforge/var/mongodb
- Provision services.
teamforge provision
TeamForge 19.0 installer expects the system locale to beLANG=en_US.UTF-8
. TeamForge create runtime (teamforge provision
) fails otherwise.
Finishing Tasks
- Run the
/var/lib/pgsql/analyze_new_cluster.sh
script. This is required if and only if you are upgrading from TeamForge 17.1 (or earlier) to TeamForge 17.8 (or later).su - postgres -c "/var/lib/pgsql/analyze_new_cluster.sh"
- If you have CVS integrations, synchronize permissions post upgrade. See Synchronize TeamForge Source Control Integrations.
- Verify TeamForge upgrade.
- Reboot the server and make sure all services come up automatically at startup.
- Log on to the TeamForge web application using the default Admin credentials.
- Username:
admin
- Password:
admin
- Username:
- If your site has custom branding, verify that your branding changes still work as intended. See Customize TeamForge.
- Let your site’s users know they’ve been upgraded. See Create a Site-wide Broadcast.
Post Upgrade Tasks
- Run TeamForge in SELinux
enabled
Mode - Add EventQ to Existing Projects
- Users are not getting email notifications for review requests and reviews. What should I do?
- Integrate using TeamForge Webhooks-based Event Broker (Jenkins and JIRA)
Also See…
- FAQs on Install / Upgrade / Administration
- TeamForge upgrade fails when migrating Baseline database to the latest schema. What should I do?
[]:
-
It’s highly recommended that you install/upgrade the TeamForge Baseline services on a separate server as the baselining process can consume considerable CPU and database resources. For more information, see Upgrade TeamForge on Same Hardware in a Distributed Multi-host Setup. ↩
-
TeamForge Baseline, if installed, requires TeamForge Webhooks-based Event Broker. ↩