Finish your upgrade

Here's how to make sure everything is running smoothly after upgrading to CollabNet TeamForge.

1. If your site uses LDAP integration, set it up again. A fresh LDAP configuration file, compatible with the new JBoss version in TeamForge 5.4, has been installed. You must reconfigure LDAP according to the instructions at Set up LDAP authentication for the CollabNet TeamForge server.
2. Install a project template. TeamForge comes with a sample project template that showcases some of the platform's most interesting features. Site administrators and project managers can use this template to jump-start projects without a lot of manual setup steps.
   Note: This procedure is recommended, but not required.
   • cd /opt/collabnet/teamforge-installer/5.4.0.0
   • ./install-project-templates.py -V

   Use a site administrator user name and password. For a new site, these are admin and admin.

   Tip: On some servers, it may take a few seconds for the SOAP server to be ready after installation. If install-project-templates.py returns an error, try waiting briefly and then running it again.
3. Log into your site as the administrator. The value you assigned to the DOMAIN variable in the site-options.conf file is the URL to log into.
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.
5. Verify that your site administrator email is still correct. This is the address that appears in the From field of messages automatically sent to users from your site.
   1. On the site toolbar, click Admin > Users > TeamForge Administrator .
   2. If your site's URL has changed, click Edit and provide a valid email address.
6. If your site has custom branding, get a copy of the latest branding bundle from open.collab.net and reconcile your customizations with the latest updates to those files.
   Tip: Commonly customized files include button_bar.vm, menu_bar.vm, and sf_functions.js.

   For more detailed information about branding, see Customize anything on your site.