Install Git on a separate server

In this option, we install the GIT integration services on a separate server.

Log on to the server as root user always.

Do this on the Git server. We'll call this my.git.host.

  1. Install SuSE Linux Enterprise Server 11 SP2 and log in as root.
    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 8.1 installation repository. See TeamForge installation repository configuration for SUSE.
  4. Install the Git packages.
    • zypper install teamforge-git
  5. Configure the token settings for Git in the site-options.conf file.
    • vi /opt/collabnet/teamforge-installer/8.1.0.1/conf/site-options.conf
    1. Modify the host token settings.
      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.git.host=gerrit
      DOMAIN_my.git.host=my.git.domain.com
      HOST_my.app.domain.com=app database datamart etl indexer subversion cvs
    2. Ensure to set the token DEDICATED_INSTALL=true. This makes the installation process very simple as the TeamForge installer takes care of configuring the Apache and PostgreSQL automatically.
    3. 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.
    4. 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.
    5. Remember to include the SCM_DEFAULT_SHARED_SECRET token in the site-options.conf file and provide it with a value of 16-24 characters. Remember to use the same key as used in the primary TeamForge application server.
    6. 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?
    7. Save the site-options.conf file.
  6. Run the install_jdk_suse.sh script.
    • cd /opt/collabnet/teamforge-installer/8.1.0.1
    • ./install_jdk_suse.sh
  7. Recreate the runtime environment.
    • cd /opt/collabnet/teamforge-installer/8.1.0.1
    • ./install.sh -r -I -V
  8. Run the TeamForge post installation script. For more information, see post-install.py.
    • /opt/collabnet/teamforge/runtime/scripts/post-install.py

Configuring James if Git is on a separate server

See James configuration if Git is on a separate server.

Installing TeamForge Orchestrate

To install TeamForge Orchestrate, see TeamForge Orchestrate installation and Set up Orchestrate.