Upgrade from TeamForge 7.2 to 16.10 - All services on the same server

In this procedure, we'll assume that you are upgrading on the same server where your existing TeamForge 7.2 site is running.

Do the following on the TeamForge Application Server - server-01

1. Before you upgrade to TeamForge 16.10, uninstall hotfixes and add-ons, if any.
2. If you have Review Board installed, uninstall Review Board.
   • cd /opt/collabnet/RBInstaller-1.5.0.0.5
   • python ./install.py -u
3. Stop the TeamForge CLI add-on (This step is required only for TeamForge Application server).
   • service teamforge_cli_server stop
4. Stop TeamForge.
   • /etc/init.d/collabnet stop all
5. Migrate your PostgreSQL to the latest version supported by TeamForge 16.10.
   Important: You must have RHEL/CentOS 6.5 or later to run PGTurant. Upgrade the operating system packages (yum upgrade) before running PGTurant on sites running on RHEL/CentOS versions 6.4 or earlier.
   1. Install PGTurant. See Upgrade PostgreSQL using PGTurant for more information.
      Important: If your TeamForge site has no internet access, contact the CollabNet Support, get the pgturant-8.0.0.0-7.noarch.rpm package and unpack the RPM.

      • rpm -ivh pgturant-8.0.0.0-7.noarch.rpm
      • yum install pgturant -y
   2. Upgrade TeamForge PostgreSQL data directory to PostgreSQL 9.3.
      • cd /opt/collabnet/pgturant/bin/
      • ./pgturant -s /var/lib/pgsql/9.2/data -d /var/lib/pgsql/9.3 -u 9.3 -m
6. Important: This step is required only if you ran PGTurant. You can skip this step otherwise.
   Start the PostgreSQL service, run the analyze_new_cluster.sh script and stop PostgreSQL.
   • /etc/init.d/postgresql-9.3 start
   • su - postgres -c "/var/lib/pgsql/9.3/analyze_new_cluster.sh"
   • /etc/init.d/postgresql-9.3 stop
7. Do this only if your reporting database is running on a separate port.
   1. Upgrade your PostgreSQL reports data directory to PostgreSQL 9.3.
      • cd /opt/collabnet/pgturant/bin/
      • ./pgturant -s /var/lib/pgsql/9.2/reports -d /var/lib/pgsql/9.3 -u 9.3 -m
   2. Open the analyze_new_cluster.sh file.
      • vim /var/lib/pgsql/9.3/analyze_new_cluster.sh
   3. Find and replace all.
      • Find all occurrences of this: /usr/pgsql-9.3/bin/vacuumdb" --all --analyze-only
      • Replace with: /usr/pgsql-9.3/bin/vacuumdb" -p 5632 --all --analyze-only
   4. Create a new postgresql-9.3_reports file.
      • cp /etc/init.d/postgresql-9.3 /etc/init.d/postgresql-9.3_reports
   5. Open the newly created postgresql-9.3_reports file.
      • vim /etc/init.d/postgresql-9.3_reports
   6. Modify the PGPORT, PGDATA and PGLOG values in the postgresql-9.3_reports file as follows.
      • PGPORT=5632
      • PGDATA=/var/lib/pgsql/${PGMAJORVERSION}/reports
      • PGLOG=/var/lib/pgsql/${PGMAJORVERSION}/pgstartup_reports.log
   7. Start postgresql-9.3_reports.
      • /etc/init.d/postgresql-9.3_reports start
   8. Run the analyze_new_cluster.sh script.
      • su - postgres -c "/var/lib/pgsql/9.3/analyze_new_cluster.sh"
   9. Stop postgresql-9.3_reports.
      • /etc/init.d/postgresql-9.3_reports stop
8. No backup is required for same hardware upgrades. However, you can create a backup as a precaution. See Back up and restore TeamForge and EventQ to learn more about backing up TeamForge and EventQ database and file system.
9. Move the CollabNet-Orchestrate.repo file.
   Important: This is required only if you are upgrading from TeamForge 16.3 (or earlier) to TeamForge 16.10 (or later).
   • mv /etc/yum.repos.d/CollabNet-Orchestrate.repo /etc/yum.repos.d/CollabNet-Orchestrate.repo_old
10. Run the following commands to upgrade Red Hat/CentOS to the latest version.
    1. Remove the neon-devel package.
       • yum erase neon-devel -y
    2. Upgrade the operating system packages.
       • yum upgrade
11. If the TeamForge server has SELinux enabled, run it in 'Permissive' mode temporarily while installing or upgrading TeamForge.
    Important: If you have SELinux in "enforcing" mode, you must either disable SELinux or switch to "Permissive" mode (recommended) before running the /opt/collabnet/teamforge/bin/teamforge provision command. TeamForge create runtime fails otherwise.
    1. Verify if SELinux is running in enforcing mode.
       • getenforce
    2. If the output of the getenforce command is "Permissive", continue with the next step. If not, run the following command to bring it to 'Permissive' mode.
       • setenforce 0
    See Set up SELinux to have TeamForge run in SELinux enforcing mode after completing the installation or upgrade.
12. Attention: Do this only if you are upgrading TeamForge on RHEL/CentOS 6.8.
    Delete the python-crypto package.
    • yum erase python-crypto
13. Configure your TeamForge installation repository.
    • TeamForge installation repository configuration for sites with internet access
    1. Contact the CollabNet Support and download the TeamForge 16.10 installation repository package to /tmp.
    2. Install the repository package.
       • yum install -y /tmp/collabnet-teamforge-repo-16.10-1.noarch.rpm
    3. Refresh your repository cache.
       • yum clean all
    • TeamForge installation repository configuration for sites without internet access
    1. Contact the CollabNet Support to get the auxiliary installer package for TeamForge 16.10 disconnected installation and save it in /tmp.
       • Red Hat Enterprise Linux/CentOS 6.8 64 bit RPM package: CTF-Disconnected-media-16.10.658-76.rhel6.x86_64.rpm
    2. Unpack the disconnected installation package.
       • rpm -Uvh <package-name>
    3. Note: If the Red Hat Enterprise Linux/CentOS installation DVD is mounted already, skip the following instructions. If not, mount the DVD.
       Mount the Red Hat Enterprise Linux/CentOS installation DVD. The DVD contains the necessary software and utilities required for installing TeamForge without internet access.

       In the following commands, replace "cdrom" with the identifier for your server's CD/DVD drive, if necessary.

       • cd /media/
       • mkdir cdrom
       • mount /dev/cdrom ./cdrom/

       If there are any spaces in the automount, unmount it first and mount it as a filepath, with no spaces.

    4. Create a yum configuration file that points to the Red Hat Enterprise Linux/CentOS installation DVD.
       • vi /etc/yum.repos.d/cdrom.repo
       Here's a sample yum configuration file.

       [RHEL-CDROM] 
       name=RHEL CDRom 			
       baseurl=file:///media/cdrom/Server/
       gpgfile=file:///media/cdrom/RPM-GPG-KEY-redhat-release 
       enabled=1
       gpgcheck=0

    5. Verify your yum configuration files.
       • yum list httpd
       • yum list apr
    6. Download the code search installation package, CodeSearch-installer-2.1.3-1.noarch.rpm from https://ctf.open.collab.net/sf/go/rel4193 and save it in the /tmp directory. To install the Black Duck Code Sight installer, run the following command.
       • cd /tmp
       • rpm -ivh CodeSearch-installer-2.1.3-1.noarch.rpm
14. Uninstall the PostgreSQL RPMs.
    Note: When prompted, you must select the option to remove all the dependent packages.
    • yum erase postgresql92-libs postgresql92-docs postgresql92-server postgresql92
15. Install the following application packages.
    1. To install the TeamForge application packages run the following command:
       • yum install teamforge
       Attention: TeamForge installer is being optimized quite a bit. It's likely that you might come across a lot of warning messages while upgrading from TeamForge 8.2 (or earlier) to TeamForge 16.10 on the same hardware (when you run the yum install teamforge command). You can safely ignore such warning messages and proceed with the upgrade.
    2. To install the Black Duck Code Sight packages run the following command:
       • yum install teamforge-codesearch
16. Set up your site's master configuration file.
    1. Set up your site options. See Site options change log for a list of new and obsolete tokens.
       • vi /opt/collabnet/teamforge/etc/site-options.conf
    2. TeamForge 16.7 and later versions support automatic JAVA_HOME configuration. Remove the JAVA_HOME token, if present, from the site-options.conf file.
    3. Update the host name and domain name, if required.

       HOST_localhost=app database datamart etl indexer subversion cvs

       DOMAIN_localhost=my.app.domain.com

       Add 'gerrit' to the HOST_localhost token if you are installing Git.

       HOST_localhost=app database datamart etl indexer subversion cvs gerrit

       Add 'codesearch' to the HOST_localhost token if you are installing Black Duck Code Sight.

       HOST_localhost=app database datamart etl indexer subversion cvs gerrit codesearch

       Add 'binary' to the HOST_localhost token if you are installing Nexus.

       HOST_localhost=app database datamart etl indexer subversion cvs gerrit codesearch binary

       Add 'reviewboard' to the HOST_localhost token if you are installing Review Board.

       HOST_localhost=app database datamart etl indexer subversion cvs gerrit codesearch binary reviewboard

    4. Add the following database read-only tokens.

       • DATABASE_READ_ONLY_USER

       • DATABSE_READ_ONLY_PASSWORD

    5. Turn on the SSL for your site by editing the relevant variables in the site-options.conf file. To generate the SSL certificates, see Generate SSL certificates.

       SSL=on

       SSL_CERT_FILE

       SSL_KEY_FILE

       SSL_CHAIN_FILE

       Note: The SSL_CERT_FILE and SSL_KEY_FILE tokens need an absolute path. The SSL_CHAIN_FILE token is optional.
    6. If the token REQUIRE_PASSWORD_SECURITY is enabled, then set a value for the token, PASSWORD_CONTROL_EFFECTIVE_DATE.
       CAUTION:
       The Password Control Kit (PCK) disables, deletes or expires user accounts that don't meet the password security requirements starting from the date set for the PASSWORD_CONTROL_EFFECTIVE_DATE token. If a date is not set, the PCK disables, deletes or expires user accounts immediately. See PASSWORD_CONTROL_EFFECTIVE_DATE for more information.
    7. TeamForge 7.1 and later support automatic password creation. See AUTO_DATA for more information.
    8. Password obfuscation: The password obfuscation is enabled by default. As a result, all password-related tokens are encrypted in all the TeamForge configuration files.
       Restriction: The password-related tokens cannot contain the following characters in the site-options.conf file: $<>/\'"`
       • To disable password obfuscation, set OBFUSCATION_ENABLED=false.
       • To configure the obfuscation key, set OBFUSCATION_KEY=<Any AlphaNumeric value with length >= 8 bytes>. The default value of OBFUSCATION_KEY token is XSJt43wN.
    9. Configure the Black Duck Code Sight tokens. See Black Duck Code Sight site-option tokens.
    10. To enable the history protection feature of TeamForge Git integration, set the GERRIT_FORCE_HISTORY_PROTECTION=true. For more information, see GERRIT_FORCE_HISTORY_PROTECTION.
    11. If you have LDAP set up for external authentication, you must set the “REQUIRE_USER_PASSWORD_CHANGE” site options token to false.
    12. Make sure the PostgreSQL tokens in the site-options.conf file are set as recommended in the following topic: What are the right PostgreSQL settings for my site?
    13. Enable the POSTGRES_INTERFACE token in the site-options.conf file if the value of "ifconfig -a" is not eth0/enp0*.
    14. Configure the JBOSS_JAVA_OPTS site-options.conf token. See JBOSS_JAVA_OPTS.
        Important: All JVM parameters but -Xms1024m and -Xmx2048m have been hard-coded in the TeamForge core application. You need not manually configure any other parameter (such as -XX:MaxMetaspaceSize=512m -XX:ReservedCodeCacheSize=128M -server -XX:+HeapDumpOnOutOfMemoryError -Djsse.enableSNIExtension=false -Dsun.rmi.dgc.client.gcInterval=600000 -Dsun.rmi.dgc.server.gcInterval=600000) in the site-options.conf file.

        When you change the default value of a JVM parameter such as "-XX:HeapDumpPath", the JBoss runtime parameters include both the user defined and default values for the JVM parameter. However, JBoss runs with the user defined value and ignores the default value.

    15. Configure TeamForge site options to proxy EventQ through TeamForge. For more information, see "EventQ and TeamForge on the same server" section in this topic: Proxying EventQ through TeamForge. Also see Proxy settings and ports used by TeamForge EventQ services.
    16. Save the site-options.conf file.
17. Deploy services.
    • /opt/collabnet/teamforge/bin/teamforge provision

    The "provision" command prompts for response before it bootstraps or migrates data during TeamForge installation and upgrade respectively. Enter "Yes" or "No" to proceed. For more information, see The teamforge script.

18. Run the following script to upgrade the Subversion working copies.
    • /opt/collabnet/teamforge/runtime/scripts/svn-upgrade-working-copies.sh
19. If you have CVS integrations, synchronize permissions post upgrade. See, Synchronize TeamForge source control integrations.
20. Run the TeamForge post installation script. For more information, see post-install.py.
    • /opt/collabnet/teamforge/runtime/scripts/post-install.py
    Note: In case you face any Git-related issues while running the post-install.py script, see Post install fails for Git. What should I do?.
21. Install the Black Duck Code Sight license on the server where Black Duck Code Sight is installed. For more information see these instructions.
22. Run the svn_cache.sh script.
    • cd /opt/collabnet/teamforge/runtime/scripts/codesearch/
    • ./svn_cache.sh <Repository Base URL Path of the SCM Integration Server>

    Provide a repository base URL path of the SCM Integration Server, for example, "http://myint.box.net/svn/repos", where myint.box is the server with the SCM integration server.

    In addition, if you add a new integration server at some point later, you must run this svn_cache.sh script, (after creating the new integration server), on the TeamForge application server.

23. Upgrade EventQ. See Upgrade EventQ.
24. Apply the finishing touches and make sure everything is running smoothly after upgrading to TeamForge 16.10.
    1. Log on to the TeamForge web application using the default Admin credentials.
       • Username: "admin"
       • Password: "admin"
    2. If your site has custom branding, verify that your branding changes still work as intended. See Change your site's look and feel.
    3. Let your site's users know they've been upgraded. See Communicate with all site users at once.
25. Remove the backup files, if any, after the TeamForge site is up and running as expected.