Red Hat help


Option 6: Distribute TeamForge 6.1.1 services using Oracle

Option 6 is like Option 5, but it uses an Oracle database instead of a PostgreSQL database.

For simplicity, in this example we will have the site database and the reporting database share port 1521.
Note: If either of the remote machines (the data box or the source code box) is not under your direct control, check with the DBA or other person in charge of that resource to make sure you can carry out these instructions on that box.

Do this on the main TeamForge application server. We'll call this my.app.box.

  1. Install Red Hat Enterprise Linux 5.6 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 box for details.
  3. Download the TeamForge 6.1.1 installation repository from open.collab.net. Copy it to /etc/yum.repos.d/.
  4. Install the TeamForge application and reporting service.
    • yum install teamforge-app teamforge-etl
    Tip: If the yum installer balks, you may have duplicate rpm packages.
    1. Get the yum-utils package, if it isn't already installed.
      • yum install yum-utils
    2. Check for duplicate packages.
      • package-cleanup --dupes
    3. Clean up the older packages, if any.
      • package-cleanup --cleandupes
    4. Rerun the yum installer.
      • yum install teamforge-app teamforge-etl
  5. Rename the sample site configuration file from the installation package.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • cp conf/site-options-advanced.conf conf/site-options.conf
    Note: The files site-options-small.conf, site-options-medium.conf and site-options-large.conf contain options to tune the performance of the TeamForge site. To tune your site's performance, you can look through these files for the load specifications they are intended for, and use the appropriate one for your site's requirements.
  6. Configure the site-options.conf file.
    • vi conf/site-options.conf
    1. Identify the boxes and the services running on them. 
      HOST_localhost=app etl
DOMAIN_localhost=<myappbox.domain.com>
HOST_<mydbbox.domain.com>=database datamart
HOST_<myscmbox.domain.com>=subversion cvs
    2. Configure the database and the datamart.
      Tip: For more information about configuring variables, see site-options.conf.
      DATABASE_TYPE=oracle
DATABASE_USERNAME=sitedatabaseusername
DATABASE_PASSWORD=sitedatabasepwd
DATABASE_NAME=sitedatabaseinstancename
DATABASE_MAX_POOL_SIZE=100
REPORTS_DATABASE_USERNAME=reportingdatabaseusername
REPORTS_DATABASE_PASSWORD=reportingdatabasepwd
REPORTS_DATABASE_NAME=reportingdatabaseinstancename
REPORTS_DATABASE_READ_ONLY_USER=reportingreadonlyusername
REPORTS_DATABASE_READ_ONLY_PASSWORD=reportingreadonlyuserpwd
ETL_SOAP_SHARED_SECRET=<arbitrary_string>
SOAP_ANONYMOUS_SHARED_SECRET=<arbitrary_string>
DATABASE_SERVICE_NAME=
REPORTS_DATABASE_SERVICE_NAME=
      Tip:
      • The database name and user name values are arbitrary alphanumeric strings.
      • To find the value for the DATABASE_SERVICE_NAME variable, log into your Oracle server and execute this command:
        • su - oracle
        • tnsping <database_name>
        In the output, find the value of SERVICE_NAME. Use that as the value of DATABASE_SERVICE_NAME in site-options.conf.
    3. If you don't specify a domain name, replace the HOST_localhost token with the hostname. Otherwise, ViewVC pages for Subversion and CVS repositories created after the site is up, will be rendered with a CSS error.
    4. Important: It is mandatory that you include the SCM_DEFAULT_SHARED_SECRET token in the site-options.conf file of the primary TeamForge server, and give it a value of 16-24 characters.
      Remember that you need to use that same key in the external SCM integration server also.
    5. Don't forget to save the file.
  7. Note: Perform this step in case your Oracle server version is not 11.2.0.1.
    Download the corresponding version of Oracle client from http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html and run the following command:
    • yum localinstall <path to oracle client rpm>
  8. Run the installer.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • ./install.sh -r -I -V
  9. Copy the Oracle datamart setup script from /opt/collabnet/teamforge/runtime/scripts to the /tmp directory of my.data.box.
    • scp /opt/collabnet/teamforge/runtime/scripts/datamart-oracle-setup.sh <username>@<my.data.box>:/tmp

Do this on the database/datamart server. We'll call this my.data.box.

  1. Install Red Hat Enterprise Linux 5.6 and log in as root.
    Important: Don't customize your installation. Select only the default packages list.
  2. Install Oracle 11 (R1 and R2). See the Oracle wiki for details.
    Note: Make sure your database uses UTF8 or AL32UTF8 encoding. This is needed to support users in Asian languages. See this Oracle knowledge base article.
  3. Put the Oracle datamart setup script where TeamForge can find it.
    • mkdir /u1
    • cp /tmp/datamart-oracle-setup.sh /u1
  4. Log in as the Oracle user and create the site database user and permissions. See Set up an Oracle database for help.
  5. Create the reporting user and schema.
    • cd /u1
    • sh datamart-oracle-setup.sh
    Note: Your responses to the script's prompts must match the values of the equivalent variables in the site-options.conf file on my.app.box.

Do this on my.app.box

  1. Set up the initial site data.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • ./bootstrap-data.sh
  2. If you are installing on a machine that is behind a proxy, unset the http_proxy variable.
    • export http_proxy=
  3. Swap in the new Apache configuration file.
    • cd /etc/httpd/conf
    • mv httpd.conf httpd.conf_old
    • cp httpd.conf.cn_new httpd.conf
    • /etc/init.d/httpd start

Do this on the source control server. We'll call this my.code.box.

  1. Install Red Hat Enterprise Linux 5.6 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 box for details.
  3. Download the TeamForge 6.1.1 installation repository from open.collab.net. Copy it to /etc/yum.repos.d/.
  4. Install the TeamForge source control service.
    • yum install teamforge-scm
    Tip: If the yum installer balks, you may have duplicate rpm packages.
    1. Get the yum-utils package, if it isn't already installed.
      • yum install yum-utils
    2. Check for duplicate packages.
      • package-cleanup --dupes
    3. Clean up the older packages, if any.
      • package-cleanup --cleandupes
    4. Rerun the yum installer.
      • yum install teamforge-scm
  5. Rename the sample site configuration file from the installation package.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • cp conf/site-options-advanced.conf conf/site-options.conf
    Note: The files site-options-small.conf, site-options-medium.conf and site-options-large.conf contain options to tune the performance of the TeamForge site. To tune your site's performance, you can look through these files for the load specifications they are intended for, and use the appropriate one for your site's requirements.
  6. Configure the site-options.conf file.
    1. Identify the boxes and the services running on them. 
      HOST_localhost=subversion cvs
DOMAIN_localhost=<myscmbox.domain.com>
HOST_<myappbox.domain.com>=app
HOST_<mydbbox.domain.com>=database
    2. Configure the database connection. 
      DATABASE_TYPE=oracle
DATABASE_USERNAME=ctfuser
DATABASE_PASSWORD=ctfpwd
DATABASE_NAME=ctfdb
    3. Use the shared secret key, SCM_DEFAULT_SHARED_SECRET, from the site-options.conf file on the primary TeamForge server.
    4. If you don't specify a domain name, replace the HOST_localhost token with the hostname. Otherwise, ViewVC pages for Subversion and CVS repositories created after the site is up, will be rendered with a CSS error.
    5. Don't forget to save the file.
  7. Run the installer.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • ./install.sh -r -I -V
  8. Set up the initial site data.
    • cd /opt/collabnet/teamforge-installer/6.1.1.0
    • ./bootstrap-data.sh
  9. If you are installing on a machine that is behind a proxy, unset the http_proxy variable.
    • export http_proxy=
  10. Swap in the new Apache configuration file.
    • cd /etc/httpd/conf
    • mv httpd.conf httpd.conf_old
    • cp httpd.conf.cn_new httpd.conf
    • /etc/init.d/httpd start
  11. Start TeamForge.
    • /etc/init.d/collabnet start tomcat

Do this on my.app.box

  1. Start TeamForge.
    • /etc/init.d/collabnet start
    Note: Startup can take several minutes, depending on the speed of the host system. On some slower systems, you may get a false failure message from JBoss, like this: 
    jboss (app) (localhost:8080) ............................failed to start in 600 seconds, giving up now. Please check the log: /opt/collabnet/teamforge/log/apps/service.log FAILED

    This can safely be ignored.

Your installation is complete. Go to Verify your TeamForge 6.1.1 installation for recommended steps to get started with your site.
Up: Install TeamForge the advanced way
Related questions
Why can't Oracle connect to my TeamForge installation?
Related reference information
DATABASE_TYPE
Oracle logging
SCM_DEFAULT_SHARED_SECRET
More information
Oracle installation resources
Red Hat installation guide

Questions? Comments? Talk to other TeamForge users and CollabNet engineers.

Copyright 2011 CollabNet Corporation | Site Feedback | Terms of Use | Privacy Policy | Copyright and Trademark | Support