The easiest way to install TeamForge is to
install it on a single server, dedicated to TeamForge taking the default configuration
settings.
Before you begin:
Remember:
- TeamForge 17.8 supports
both RHEL/CentOS 6.9 and 7.3. See TeamForge installation requirements
- 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.
All
the following services
run
on a single RHEL/CentOS 7.3 server (we call this server-01).
- TeamForge Application Server (ctfcore)
- Database Server (ctfcore-database and
ctfcore-datamart)
- Mail Server (mail)
- Codesearch Server (codesearch)
- 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)
-
Install Red Hat Enterprise Linux/CentOS 7.3 and log on as
root.
The host must be registered with the Red Hat Network if you are using Red
Hat Enterprise Linux.
See the Red Hat installation guide
for help.
-
Check your basic networking setup. See Set up Networking for
more information.
-
Configure your TeamForge installation repository.
- TeamForge installation repository configuration for sites with internet
access
-
Contact the CollabNet Support and download the TeamForge
17.8 installation repository package to /tmp.
-
Install the repository package.
- yum install -y
/tmp/collabnet-teamforge-repo-17.8-1.noarch.rpm
-
Refresh your repository cache.
- TeamForge installation repository configuration for sites without
internet access
-
Contact the CollabNet Support to get the auxiliary installer package for
TeamForge
17.8 disconnected installation and save it in
/tmp.
- Red Hat Enterprise Linux/CentOS
7.3 64 bit RPM package: CTF-Disconnected-media-17.8.655-104.rhel7.x86_64.rpm
Note: In
addition to the above CentOS
7.3 64 bit RPM package, you must get the following CentOS
7.3 compatibility RPM, which is required for TeamForge
17.8
disconnected media installation on CentOS
7.3 profile:
compat-ctf-dc-media-1.1-1.el7.noarch.rpm.
-
Unpack the disconnected installation package.
-
Unpack the
compat-ctf-dc-media-1.1-1.el7.noarch.rpm
package if you are installing TeamForge
17.8 on CentOS
7.3.
- 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.
Mount the Red Hat Enterprise Linux/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 Red Hat Enterprise Linux/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
-
Install the TeamForge application
packages.
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
...
...
-
Set up your site's master configuration file.
- vi /opt/collabnet/teamforge/etc/site-options.conf
-
Configure the services and domain name tokens.
Note: cliserver and reviewboard-adapter are the new services added
in TeamForge 17.4.
localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion
cvs codesearch eventq mongodb redis rabbitmq cliserver
localhost:PUBLIC_FQDN=my.app.domain.com
-
Add
Gerrit identifiers
if
you are installing Git.
localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion
cvs codesearch eventq mongodb redis rabbitmq cliserver gerrit gerrit-database
-
Add
Binary
identifiers
if
you are installing Nexus.
localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion
cvs codesearch eventq mongodb redis rabbitmq cliserver gerrit gerrit-database binary binary-database
-
Add
Review
Board identifiers
if
you are installing Review Board.
localhost:SERVICES=ctfcore ctfcore-database mail etl ctfcore-datamart search subversion
cvs codesearch cliserver eventq mongodb redis rabbitmq gerrit gerrit-database binary binary-database
reviewboard reviewboard-database reviewboard-adapter
-
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.
-
TeamForge 7.1 and later
support automatic password creation. See AUTO_DATA for more information.
-
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.8.
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.
-
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.
-
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?
-
Save the site-options.conf file.
-
Provision
services.
Note:
TeamForge 17.4 (and later) installer expects the system locale to be
LANG=en_US.UTF-8. TeamForge "provision" command fails otherwise.
-
Restart TeamForge.
-
Verify TeamForge installation.
-
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"
-
Create a sample project. See Create a TeamForge project
-
Write a welcome message to your site's users. See Create a
site-wide broadcast.