Upgrade a stand-alone TeamForge source control box on the same hardware

If your TeamForge setup includes source control running on its own box, you'll have to upgrade that box as well as the main TeamForge application box.

1. Back up your site data.
   1. Make an archive file with the following data directories:

      Directory	Contents
      /svnroot	Subversion source code repositories
      /cvsroot	CVS source code repositories (not present on all sites)

      • mkdir /tmp/backup_dir
      • cp -Rpf /svnroot /cvsroot /tmp/backup_dir
   2. Back up your SSH keys, if any.
   3. Back up your SSL certificates and keys, if any.
2. Stop TeamForge.
   • /etc/init.d/httpd stop
   • /etc/init.d/collabnet stop tomcat
3. Move the repositories from any previous installs out of the way.
   • mv /etc/yum.repos.d/collabnet-6.1.0.0.repo /etc/yum.repos.d/collabnet-6.1.0.0.repo.cn_backup
4. Download the TeamForge 6.1.1 installation repository from open.collab.net. Copy it to /etc/yum.repos.d/.
5. Uninstall the PostgreSQL support packages to clear the way for to install PostgreSQL. (These packages are installed with the OS by default.)
   • yum erase postgresql-libs postgresql-docs
6. On the source code box, install the source code component of the TeamForge application.
   
   • yum clean all
   • yum install teamforge-scm
7. Make sure your Java settings are right for TeamForge 6.1.1.
   1. Check the JAVA_HOME variable in /opt/collabnet/teamforge-installer/6.1.1.0/conf/site-options.conf to make sure TeamForge is using the right JDK.
      • vi /opt/collabnet/teamforge-installer/6.1.1.0/conf/site-options.conf
      The JAVA_HOME variable should look like this:
      • JAVA_HOME=/usr/java/jdk1.6.0_26
   2. In the JBOSS_JAVA_OPTS variable, increase the MaxPermSize value to 512.
8. If you don't specify a domain name, replace the HOST_localhost token with the hostname in the site-options.conf file. Otherwise, ViewVC pages for Subversion and CVS repositories created after the site is up, will be rendered with a CSS error.
9. In the site-options.conf file, use the shared secret key, SCM_DEFAULT_SHARED_SECRET, from the site-options.conf file on the primary TeamForge server.
10. In the site-options.conf file, make sure you do the following:
    1. Increase the Phoenix optimization interval.

       PHOENIX_JAVA_OPTS=-Xms256m -Xmx256m -server -XX:+HeapDumpOnOutOfMemoryError  -XX:HeapDumpPath=/tmp -verbose:gc -XX:+
       PrintGCTimeStamps -XX:+PrintGCDetails -Dsun.rmi.dgc.client.gcInterval=600000 -Dsun.rmi.dgc.server.gcInterval=600000 -Dsf
       .luceneOptimizeEvery=100000

    2. Increase the value MAX_WWW_CLIENTS.

       MAX_WWW_CLIENTS=200

    3. Review the variables you've changed, then save the site-options.conf file.
11. Create the runtime environment.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • ./install.sh -r -I -V
12. Update the file permissions on your site's data.
    • /opt/collabnet/teamforge/runtime/scripts/fix_data_permissions.sh
13. Swap in the new Apache configuration file.
    • cd /etc/httpd/conf
    • mv httpd.conf httpd.conf_old
    • cp httpd.conf.cn_new httpd.conf
    • /etc/init.d/httpd start
14. Start TeamForge.
    • /etc/init.d/httpd start
    • /etc/init.d/collabnet start tomcat