Upgrade Black Duck Code Sight on the same RHEL/CentOS 6.8 server

Follow these instructions to upgrade Black Duck Code Sight on the same server.

Attention: Installing or upgrading TeamForge needs root privileges. You must log on as root or use a root shell to install or upgrade TeamForge.
  1. Upgrade to Red Hat Enterprise Linux/CentOS 6.8.
    Important: Black Duck Code Sight is not supported on RHEL/CentOS 7.x. CollabNet recommends that you have Black Duck Code Sight run on a separate RHEL/CentOS 6.8 server if you upgrade to TeamForge 8.2 (or later) on RHEL/CentOS 7.2.
    Important: Don't customize your installation. Select only the default packages list.
  2. Check your basic networking setup. See Set up networking for your TeamForge server for details.
  3. 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
  4. Install Black Duck Code Sight.
    • yum install teamforge-codesearch
  5. Copy the master site-options.conf file from the app server and modify these tokens: 
    HOST_my.host.name=codesearch
    DOMAIN_my.host.name=<mycodesearchbox.domain.com>
    • If you have Black Duck Code Sight on SSL and the following external certificate tokens are not provided, the installer will generate a self-signed certificate.

      For valid SSL certificates, configure the following tokens:

      BDCS_SSL_CERT_FILE
      BDCS_SSL_KEY_FILE

      The ca.crt and chain files are optional -- leave out the tokens if you don't use the files.

      BDCS_SSL_CA_CERT_FILE
      BDCS_SSL_CHAIN_FILE
    Advanced Black Duck Code Sight configuration settings
    Note: The following are the advanced configuration tokens which can be set once during the time of installation.
    • The path where the repositories are enabled for codesearch to check out.
      BDCS_SCAN_SOURCE_DIR_ROOT=/opt/collabnet/blackduck/scan
    • The path where the codesearch software is installed.
      BDCS_INSTALL_PATH=/opt/collabnet/blackduck
    • The path where codesearch database is installed.
      BDCS_PGSQL_HOME_DIR_ROOT=/opt/collabnet/blackduck/postgres
    • The port number for the codesearch db server.
      BDCS_PGSQL_PORT=55435
    • The tomcat maximum heap memory size in megabytes.
      BDCS_TOMCAT_MX_IN_MB=1024
    • The shutdown port number for codesearch tomcat server.
      BDCS_TOMCAT_SHUTDOWN_PORT=9189
  6. Review the tokens you've changed, then save the site-options.conf file.
  7. 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.

  8. To start the Black Duck Code Sight service, use:
    • /etc/init.d/collabnet start tomcatcs
Parent topic: Set up Black Duck Code Sight