Upgrade a TeamForge site to 6.1.1 on the same hardware

To upgrade to TeamForge 6.1.1 without changing the box where your TeamForge 6.1 site is running, you have to install the new TeamForge site and migrate the site data.

1. Back up your site data.
   1. Make a dump file of your site database. (This may be the same as your TeamForge application server or a separate box.)

      You have to do a PostgreSQL dump because we are upgrading the PostgreSQL application as part of this upgrade.

      Note: These commands are for a PostgreSQL database, which is the default. If your site uses an Oracle database, follow the Oracle backup procedure instead.
      • su - postgres
      • /usr/bin/pg_dumpall > /var/lib/pgsql/backups/teamforge_data_backup.dmp
      • exit
      • mkdir /tmp/backup_dir
      • cp /var/lib/pgsql/backups/teamforge_data_backup.dmp /tmp/backup_dir/
      Note: If your reporting database is running on a separate port, back up your reporting database too:

      • /usr/bin/pg_dumpall -p <reports_database_port> > /var/lib/pgsql/backups/teamforge_reporting_data_backup.dmp
   2. Make an archive file with the following data directories:

      Directory	Contents
      /opt/collabnet/teamforge/var	User-created data, such as artifact attachments
      /svnroot	Subversion source code repositories
      /sf-svnroot	Subversion repository for branding data
      /cvsroot	CVS source code repositories (not present on all sites)

      • cp -Rpf /svnroot /sf-svnroot /cvsroot /opt/collabnet/teamforge/var /tmp/backup_dir
      • cd /tmp
      • tar czvf 61backup.tgz backup_dir
   3. Back up your SSH keys, if any.
   4. Back up your SSL certificates and keys, if any.
2. Stop TeamForge.
   • /etc/init.d/apache2 stop
   • /etc/init.d/postgresql stop
   • /etc/init.d/collabnet stop
3. Uninstall the PostgreSQL support packages to clear the way for TeamForge to install PostgreSQL 9.0. (These packages are installed with the OS by default.)
   • zypper remove postgresql-libs postgresql-docs
4. Move the repositories from any previous installs out of the way.
   • mv /etc/zypp/repos.d/collabnet-6.1.0.0.repo /etc/zypp/repos.d/collabnet-6.1.0.0.repo.cn_backup
5. Download the TeamForge 6.1.1 installation repository from open.collab.net. Copy it to /etc/zypp/repos.d/.
6. Configure the zypper package manager to install the latest vendor packages.
   1. Add this line to the /etc/zypp/zypp.conf file:

      solver.allowVendorChange = true

   2. Refresh zypper.
      • zypper ref
7. Install the TeamForge application.
   • zypper install teamforge-sles
8. 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.
9. In the site-options.conf file, make sure you do the following:
   1. If you don't specify a domain name, replace the HOST_localhost token with the hostname. Otherwise, ViewVC pages for Subversion and CVS repositories created after the site is up, will be rendered with a CSS error.
   2. Important: It is mandatory that you include the SCM_DEFAULT_SHARED_SECRET token in the site-options.conf file of the primary TeamForge server, and give it a value of 16-24 characters.
      Remember that you need to use that same key in the external SCM integration server also.
   3. 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

   4. Increase the value of MAX_WWW_CLIENTS.

      MAX_WWW_CLIENTS=200

   5. Review the variables you've changed, then save the site-options.conf file.
10. Run the installer.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • ./install.sh -r -I -V
11. Set up the site database.
    1. Point the database to the local machine.
       • su - postgres
       • initdb -D /var/lib/pgsql/data
       • vi /var/lib/pgsql/data/postgresql.conf

       listen_addresses = '127.0.0.1,<IP address of database box>'

    2. Configure access as follows:
       • vi /var/lib/pgsql/data/pg_hba.conf

       local   all                           all                                                          trust
       # IPv4 local connections:
       host    all                           all                                    127.0.0.1/32          trust
       # IPv6 local connections:
       #host   all                           all                                    ::1/128               trust
       host    <DATABASE_NAME>       <DATABASE_USERNAME>            <IP address of my.app.box>/32   md5

12. If the reporting database (datamart) runs on a different port, you need to set it up.
    1. Point the database to the local machine.
       • su - postgres
       • initdb -D /var/lib/pgsql/reports
       • vim /var/lib/pgsql/reports/postgresql.conf

              listen_addresses = '127.0.0.1,<IP address of datamart box>'
              port=5632

    2. Configure access for the datamart.
       • vi /var/lib/pgsql/reports/pg_hba.conf

       local   all                           all                                                          trust
       # IPv4 local connections:
       host    all                           all                                    127.0.0.1/32          trust
       # IPv6 local connections:
       #host   all                           all                                    ::1/128               trust
       host    <REPORTS_DATABASE_NAME>       <REPORTS_DATABASE_USERNAME>            <IP address of my.app.box>/32   md5
       host    <REPORTS_DATABASE_NAME>       <REPORTS_DATABASE_READ_ONLY_USER>      <IP address of my.app.box>/32   md5

       • exit
    3. Copy the datamart control script from /opt/collabnet/teamforge/runtime/scripts on my.app.box to the /tmp directory of my.datamart.box.
       • mv /etc/init.d/postgresql /etc/init.d/postgresql_orig
       • cp /tmp/postgresql_reports /etc/init.d
       Note: The postgresql_reports script is the one to use only if the datamart is running on a different server from the database, as it is in this example. In all other cases, use the postgresql script.
    4. Start the reporting database service.
       • /etc/init.d/postgresql_reports start
13. Bring your site data back.
    • su - postgres
    • /usr/bin/psql < /var/lib/pgsql/backups/teamforge_data_backup.dmp
    • exit
    Note: If your reporting database is running on a separate port, restore that data too:

    • su - postgres -c "/usr/bin/psql -p <reports_database_port> < /var/lib/pgsql/backups/teamforge_reporting_data_backup.dmp"
14. Update the file permissions on your site's data.
    • /opt/collabnet/teamforge/runtime/scripts/fix_data_permissions.sh
    Note: This process can take a long time for a site with a lot of data.
15. Convert your site data to work with TeamForge 6.1.1.
    Tip: Before you kick off the data migration, use the /etc/init.d/collabnet status command to make sure Jboss and Tomcat are stopped.
    • /opt/collabnet/teamforge/runtime/scripts/migrate.py
    The migrate.py script locates the existing site data and modifies it as needed.

    This includes configuration data for LDAP and the James mail server. Any modifications that you have applied to these components on your old site are reproduced on your upgraded TeamForge 6.1.1 site.

16. Swap in the new Apache configuration file.
    • cd /etc/apache2
    • mv httpd.conf httpd.conf_old
    • cp httpd.conf.cn_new httpd.conf
    • cd /etc/sysconfig/
    • mv apache2 apache2_old
    • cp apache2.cn_new apache2
    • /etc/init.d/apache2 start
17. Start TeamForge.

    Start PostgreSQL if it is not running.

    • /etc/init.d/postgresql start
    Start the CollabNet services.
    • /etc/init.d/collabnet start
18. Apply the finishing touches and make sure everything is running smoothly after upgrading to TeamForge 6.1.1.
    1. Make sure your users can still access their source control services. See Synchronize TeamForge source control integrations.
    2. If you are bringing SSL certificates and keys from your old site, make sure their locations match the paths specified by the SSL_CERT_FILE and SSL_KEY_FILE variables in site-options.conf. See Set up SSL for your TeamForge site.
    3. Log into your site as the administrator.
    4. Reboot the server and make sure all services come up automatically at startup.
    5. Rebuild your site's search index so that users get up-to-date search results. See Rebuild TeamForge search indexes for details.
    6. If your site has custom branding, verify that your branding changes still work as intended. See Customize anything on your site.
    7. Let your site's users know they've been upgraded. See Create a site-wide broadcast.
    Important: Do not delete the teamforge-installer/6.1.1.0 directory. You will need it for future maintenance and upgrades.