Install the CollabNet TeamForge 5.4 application

Install CollabNet TeamForge and bring over the data from your old site.

1. Update these tokens in the site-options.conf file:
   • JBOSS_JAVA_OPTS=-Xms1536m -Xmx1536m -XX:MaxPermSize=256m -server -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Dsun.rmi.dgc.client.gcInterval=600000 -Dsun.rmi.dgc.server.gcInterval=600000
   • INTEGRATION_JAVA_OPTS=-Xms160m -Xmx160m -server -XX:+HeapDumpOnOutOfMemoryError  -XX:HeapDumpPath=/tmp -verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Dsun.rmi.dgc.client.gcInterval=600000 -Dsun.rmi.dgc.server.gcInterval=600000
   • 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
   • DATABASE_MAX_POOL_SIZE=100
2. Run the installer.
   • cd /opt/collabnet/teamforge-installer/5.4.0.0
   • ./install.sh -a -V
3. Reload the PostgreSQL data.
   • su - postgres -c /usr/bin/psql < <old_box>/tmp/backup_dir/ctf53.dmp
4. Reload svnroot, sf-svnroot, and var.
5. Update the file permissions on your site's data. Use this command to do it automatically:
   • /opt/collabnet/teamforge/runtime/scripts/fix_data_permissions.sh
6. Convert your old site's data.
   • /opt/collabnet/teamforge/runtime/scripts/migrate.py
   The migrate.py script locates the existing site data and modifies it to work with the new CollabNet TeamForge version.

   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 CollabNet TeamForge site.

7. Update your Apache configuration, keeping the existing settings around in case you need to roll back any changes.
   1. Back up the existing Apache configuration file.
      • On Red Hat 5.4:
        • cd /etc/httpd/conf
        • cp httpd.conf httpd.conf.backup
      • On SuSE 11.x:
        • cd /etc/apache2
        • mv httpd.conf httpd.conf_old
        • cp httpd.conf.cn_new httpd.conf
   2. Review the new httpd.conf.cn_new or apache2 file that was created by the install process. This is an Apache web server configuration file that combines any existing web server configuration with directives specific to CollabNet TeamForge.
   3. When you are satisfied that the new configuration file meets all your networking requirements, rename it so it becomes the active version.
      • On Red Hat 5.4: mv httpd.conf.cn_new httpd.conf
      • On SuSE 11.x:
        • cd /etc/sysconfig/
        • mv apache2 apache2_old
        • cp apache2.cn_new apache2
8. Start the application services.
   • /etc/init.d/httpd start
   • /etc/init.d/postgresql start
   • /etc/init.d/collabnet start
   Note: You can use the start command in two ways:

   • /etc/init.d/collabnet start starts the application server and integration servers. This is the default startup command.
   • /etc/init.d/collabnet start all also starts the database and the Apache server.