Get CollabNet TeamForge 5.4

Download the packages you need to install and set up CollabNet TeamForge.

1. Download the software you'll need to install the TeamForge application.
   1. Get the main TeamForge install package from open.collab.net. Copy it to a temporary location, such as /tmp, on the server where TeamForge will run.
   2. If you are installing TeamForge on a server without an Internet connection, ask your CollabNet representative for one of these auxiliary packages and save it in /tmp. This download includes the extra software and utilities you would otherwise be downloading automatically during the install process.

      The exact auxiliary package you will download depends on your operating system:

      Operating system	Installer package
      Red Hat Enterprise Linux 5.4 32-bit	CTF-Disconnected-media-5.4.0.0-308.el5.i386.rpm
      Red Hat Enterprise Linux 5.4 64-bit	CTF-Disconnected-media-5.4.0.0-308.el5.x86_64.rpm
      SuSE Linux Enterprise Server 11.x 32-bit	CTF-Disconnected-media-5.4.0.0-308.sles11.i386.rpm
      SuSE Linux Enterprise Server 11.x 64-bit	CTF-Disconnected-media-5.4.0.0-308.sles11.x86_64.rpm

2. Unpack the main installation package.
   • rpm -ivh TeamForge-installer-5.4.0.0-308.noarch.rpm
   Tip: To specify the directory where you want the installation package deployed, add the --prefix flag to the rpm command.

   • rpm -ivh TeamForge-installer-5.4.0.0-308.noarch.rpm --prefix /some/other/path
3. If you are installing TeamForge on a server without an Internet connection, unpack the auxiliary installer package that you downloaded.
   • rpm -ivh <package-name>

   (See the table for the exact package name.)

   1. Insert the installation DVD for the operating system. This will provide some of the necessary software and utilities for installing TeamForge.
   2. Mount the Red Hat (or CentOS) installation DVD.
      Note: On SuSE, you don't need to mount the DVD. Just check that the contents of /etc/zypp/repos.d/SUSE-Linux-Enterprise-Server-11-0.repo are appropriate for your installation environment. For example, replace sr0 with the identifier for your server's CD drive, if necessary.
      • umount /media/RHEL_5.3\ i386\ DVD/
      • cd /media/
      • mkdir cdrom
      • mount /dev/cdrom ./cdrom/

      Replace cdrom with the identifier for your server's CD drive, if necessary.

      Tip: If there are any spaces in the automount, unmount it first and mount it as a filepath, with no spaces.
   3. Create a yum configuration file that points to the OS installation DVD contents. For example, if you are using vi:
      • vi /etc/yum.repos.d/cdrom.repo
   4. Copy this into the file you just created:

      [RHEL-CDROM]
      name=RHEL CDRom
      baseurl=file:///media/cdrom/Server/
      gpgfile=file:///media/cdrom/RPM-GPG-KEY-redhat-release
      enabled=1
      gpgcheck=0

      Note: On CentOS 5, omit "Server" from the baseurl path, like this: baseurl=file:///media/cdrom/
   5. Check that your configuration files are correct.
      • yum list httpd
      • yum list apr
   Now the yum package manager will look for the standard OS installation components on the DVD and not on the Internet.
4. If there is any software on the box that won't work with TeamForge 5.4, this is a good time to fix that.
   1. To determine whether you need to do this, check your site's master configuration file: /opt/collabnet/teamforge-installer/5.4.0.0/conf/site-options.conf. If the DEDICATED_INSTALL variable is set to true, the installer will take care of your package versions automatically, and you can skip this whole step.
   2. If the DEDICATED_INSTALL variable is not set to true (or is not there), then run the automatic environment checking utility and resolve any issues it reports.
      • cd /opt/collabnet/teamforge-installer/5.4.0.0
      • ./environment_check.sh
      The environment checking utility compares your system environment with the list of packages required by the CollabNet TeamForge installer, and reports on which required packages are installed, missing, or out of version tolerance. Any package that is not the right version triggers a WARNING message. For each such message, you have three choices:
      1. Remove the package and its dependencies.
      2. Have the versions fixed automatically by running the prepare-environment tool.
         • ./prepare-environment.sh
         The TeamForge installer automatically installs the versions that TeamForge needs.
      3. If you can't have packages changed automatically (for example, if some other application depends on the same Subversion or PostgreSQL installation on your application server, or the prepare-environment tool finds a package conflict it cannot resolve on its own), you can do the upgrade yourself.
   3. Run environment_check.sh again until no WARNING messages appear.
      Important: Do not go on with the installation until all WARNING messages are resolved.