For the ETL service to run as expected in a distributed TeamForge
installation, all servers must have the same time zone.

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. See
EventQ installation requirements.

Installing or upgrading TeamForge needs root privileges.
You must log on as root or use a root shell to install or upgrade
TeamForge.

In a distributed setup, stop TeamForge services on all the servers while
upgrading to TeamForge 17.11.

Reset the PASSWORD_CONTROL_EFFECTIVE_DATE token while
upgrading to TeamForge 17.8. If not reset, the Password Control Kit (PCK)
disables, deletes or expires user accounts immediately.

Note: In
addition to the above CentOS7.4 64 bit RPM package, you must get the following CentOS7.4 compatibility RPM, which is required for TeamForge17.11 disconnected media installation on CentOS7.4 profile:
compat-ctf-dc-media-1.1-1.el7.noarch.rpm.

Unpack the disconnected installation package.

rpm -Uvh <package-name>

Unpack the
compat-ctf-dc-media-1.1-1.el7.noarch.rpm
package if you are installing TeamForge17.11 on CentOS7.4.

rpm -ivh
compat-ctf-dc-media-1.1-1.el7.noarch.rpm

Note: If the Red Hat Enterprise Linux/CentOS installation DVD is mounted already, skip the following instructions.
If not, mount the DVD.

Important: The following warning message,
which shows up during TeamForge install/upgrade (while installing
CN-eventq rpm) can be safely
ignored.

Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.
...
...
Errno::ENOENT: No such file or directory - git
...
...

Install PostgreSQL 9.3
packages.
Do this if and only if you are upgrading from TeamForge 17.4 or
earlier.

yum install postgresql93-*

Reload site data.

If you are upgrading from TeamForge 16.7 or earlier to TeamForge 17.11:

cd /opt/collabnet/teamforge/

mkdir var

cd var

tar
zvxf
/tmp/backup_dir/pgsql.tgz

cp -Rpfv /tmp/backup_dir/svnroot
/svnroot

cp -Rpfv /tmp/backup_dir/cvsroot
/cvsroot

cp -Rpfv /tmp/backup_dir/sf-svnroot
/sf-svnroot

cp -Rpfv /tmp/backup_dir/var
/opt/collabnet/teamforge/

If Git integration is enabled

cp -Rpfv /tmp/backup_dir/gitroot
/gitroot

cp -Rpfv /tmp/backup_dir/gerrit/gerrit/etc
/opt/collabnet/gerrit

cp -Rpf /tmp/backup_dir/gerrit/gerrit/.ssh
/opt/collabnet/gerrit

cp -Rpf /tmp/backup_dir/gerrit/gerrit/bin
/opt/collabnet/gerrit

cp
-Rpf /tmp/backup_dir/gerrit/gerrit/index
/opt/collabnet/gerrit

EventQ

yes | cp -Rf
/tmp/backup_dir/*.yml
/opt/collabnet/eventq/config/

yes | cp -Rf
/tmp/backup_dir/mongodb
/opt/collabnet

yes | cp -Rf
/tmp/backup_dir/rabbitmq
/opt/collabnet

If you are upgrading from TeamForge 16.10 or later to TeamForge 17.11:

cp -Rpfv /tmp/backup_dir/var
/opt/collabnet/teamforge/

If Git integration is enabled

cp -Rpfv /tmp/backup_dir/gerrit/gerrit/etc
/opt/collabnet/gerrit

cp -Rpf /tmp/backup_dir/gerrit/gerrit/.ssh
/opt/collabnet/gerrit

cp -Rpf /tmp/backup_dir/gerrit/gerrit/bin
/opt/collabnet/gerrit

cp -Rpf /tmp/backup_dir/gerrit/gerrit/index
/opt/collabnet/gerrit

EventQ

yes | cp -Rf
/tmp/backup_dir/*.yml
/opt/collabnet/eventq/config/

yes | cp -Rf
/tmp/backup_dir/mongodb
/opt/collabnet

yes | cp -Rf
/tmp/backup_dir/rabbitmq
/opt/collabnet

Copy the site-options.conf file to the TeamForge installer directory.

cp /tmp/site-options.conf /opt/collabnet/teamforge/etc/

Set up your site's master configuration file.

Set up your site options. 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 the site-options.conf file of the TeamForge
version you are upgrading to.

Note: You may remove the identifiers of components you do not want. For
example, remove binary and
binary-database if you are not planning to
install binary repository managers such as Nexus.

Set the MONGODB_APP_DATABASE_NAME token with
EventQ’s database name in the site-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

Attention:SSL is
enabled by default and a self-signed certificate is auto-generated. Use
the following tokens to adjust this behavior. 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.

SSL_CERT_FILE=

SSL_KEY_FILE=

SSL_CHAIN_FILE=

Important: All SSL certificates including self-signed
certificates are added automatically.

If the token REQUIRE_PASSWORD_SECURITY is enabled,
then set this PASSWORD_CONTROL_EFFECTIVE_DATE token
with a future date. If already set, reset the
PASSWORD_CONTROL_EFFECTIVE_DATE with a future
date while upgrading to TeamForge 17.11.

CAUTION:

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 the
PASSWORD_CONTROL_EFFECTIVE_DATE token. If a
date is not set, the PCK disables, deletes or expires user accounts
immediately. You must set (or reset if required) this token with a
future date. For example, you can use the following logic and pick a
future date: PASSWORD_CONTROL_EFFECTIVE_DATE=<the day
on which TeamForge upgrade is done> +
PASSWORD_WARNING_PERIOD. See
PASSWORD_CONTROL_EFFECTIVE_DATE for more
information.

TeamForge 7.1 and later
support automatic password creation. See AUTO_DATA for more information.

Important: All JVM parameters but
-Xms1024m
and -Xmx2048m have been hard-coded in the TeamForge core
application. You cannot manually configure any of the following default JVM
parameters in the site-options.conf file.

-XX:+UseParallelGC

-XX:MaxMetaspaceSize=512m

-XX:ReservedCodeCacheSize=128M

-server

-XX:+HeapDumpOnOutOfMemoryError

-XX:HeapDumpPath=/tmp -verbose:gc

-XX:+PrintCodeCache

-Djsse.enableSNIExtension=false

-Dsun.rmi.dgc.client.gcInterval=600000

-Dsun.rmi.dgc.server.gcInterval=600000

-Djava.security.egd=file:/dev/urandom

-Djava.awt.headless=true.

When you change the default value of a JVM parameter such as
"-XX:HeapDumpPath", the JBoss runtime parameters include both the user defined
and default values for the JVM parameter. However, JBoss runs with the default
value and ignores any user defined value.

Save the site-options.conf file.

Install Review Board (note that you should have added the following identifiers
to the SERVICES token: reviewboard,
revieboard-database, and
reviewboard-adapter).