Apply a patch

The patch installer is built into the existing TeamForge installation, and it updates itself automatically when you run it.

1. Stop CollabNet TeamForge.
   Note: If your site is running on multiple machines, stop all the machines.
   • /etc/init.d/collabnet stop all
2. Run the patch installer from the base installer directory.
   • cd /opt/collabnet/teamforge-installer/5.4.0.0
   • ./patch-install.sh -l 1 -n -V -d /opt/collabnet/teamforge

   The -l parameter specifies the number of the patch (also called the patch level) and the -d parameter specifies the directory where the site is running.

3. Start CollabNet TeamForge.
   • On Red Hat or CentOS:
     • /etc/init.d/httpd start (On CentOS, you may need to start Apache manually: /sbin/chkconfig --level 2345 httpd on)
     • /etc/init.d/postgresql start
     • /etc/init.d/collabnet start
   • On SuSE:
     • /etc/init.d/apache2 start
     • /etc/init.d/postgresql start
     • /etc/init.d/collabnet start
4. Ensure that your users can access their source code normally.
   1. Click Admin in the CollabNet TeamForge navigation bar.
   2. On the site administration navigation bar, click Integrations.
   3. For each source control service you are supporting, verify that the right paths are specified.
      • SOAP service host should be localhost or the host name of the server on which you just installed TeamForge.
      • Repository base URL should be the URL for the top level of your source code server (which may be the same as your application server). For example, http://<myscmbox>/svn/repos
      • SCM Viewer URL should be the URL for the ViewVC application on your source control server. For example, http://<myscmbox>/integration/viewvc/viewvc.cgi
   4. Select all your source code integrations and click Synchronize Permissions. This updates the permissions on your code repositories so that users can access them from the new site.