Apply a patch

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

1. Stop TeamForge.
   • /etc/init.d/httpd stop
   • /etc/init.d/postgresql-9.0 stop
   • /etc/init.d/collabnet stop
2. Run the patch installer from the base installer directory.
   • cd /opt/collabnet/teamforge-installer/6.1.1.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.

   Note: If you have redirected the logs during the patch install process (./patch-install.sh -l 2 -d /opt/collabnet/teamforge &> /tmp/install.log), you may see the command prompt at this point. This does not indicate that the installation has ended. To verify that the install process is still running, you can run ps -ef | grep install.
3. Start TeamForge.
   • /etc/init.d/httpd start
   • /etc/init.d/postgresql-9.0 start
   • /etc/init.d/collabnet start
4. Verify that your patch change has worked.
   1. Log onto the site as a site administrator.
   2. On the Admin tab, click System Tools.
   3. Click Build Information and observe which patches are present.
5. Ensure that your users can access their source code.
   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.
   Note: By default, the DISABLE_CREATE_INTEGRATION_SERVERS flag in the site-options.conf file is set to false, which allows users to create new external integrations. To suppress the ability to add integrations, change this setting to true and recreate the runtime environment before making the site available to users.