Install Black Duck Code Sight on a separate RHEL/CentOS 6.7 server

Black Duck Code Sight is not supported on RHEL/CentOS 7.2. Follow these instructions to install Black Duck Code Sight on a separate RHEL/CentOS 6.7 server.

1. Install Red Hat Enterprise Linux/CentOS 6.7 and log in as root.
   • The host must be registered with the Red Hat Network if you are using Red Hat Enterprise Linux. See Platform specification for TeamForge 16.3 for the full platform requirements.
   • See the Red Hat installation guide for help.
   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 16.3 installation repository. See TeamForge installation repository configuration for Red Hat/CentOS.
4. Install Black Duck Code Sight.
   • yum install teamforge-codesearch
5. Copy the site-options.conf file from the application server to the /opt/collabnet/teamforge-installer/16.3/conf directory of the Black Duck Code Sight server.
6. Modify the host token settings on the site-options.conf file.
   Important: If you choose not to use the application server's site-options.conf file, then don't forget to copy the value of AUTO_DATA token from the application server.

   • HOST_my.codesight.host=codesearch

   • DOMAIN_my.codesight.host=my.codesight.domain.com

   • HOST_my.app.domain.com=app database datamart etl indexer subversion cvs gerrit binary

7. Save the site-options.conf file.
8. Run the installer.
   • cd /opt/collabnet/teamforge-installer/16.3
   • ./install.sh -r –I –V
9. To start the Black Duck Code Sight service, use:
   • /etc/init.d/collabnet start tomcatcs
10. 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.