Jazz Library TN0018: Running Rational Team Concert on Mac OS X
Author name

workflow-management,rational-team-concert

Tue, 23 Jun 2009
5 min read
0

TN0018: Running Rational Team Concert on Mac OS X

Last Updated: June 23, 2009
Author: André Weinand
Build basis: Rational Team Concert 1.0 and 2.0

Summary

Although officially unsupported, Rational Team Concert 1.0 and 2.0 both run on Mac OS X 10.4.x and 10.5.x. The Rational Team Concert client works without modification, and the Jazz Team Server and build engine work with minor changes to scripts and configuration files. This document describes how to install and run the Rational Team Concert 1.0 and 2.0 client and server components on Mac OS X.

More Information

The Rational Team Concert Eclipse Client

A Rational Team Concert client exists for Mac OS X. It works without modification.

  • Download the Client for Mac OS X ZIP file from the Incubator section of the All Downloads page on Jazz.net.
  • Move the ZIP file to the folder where you want to install Rational Team Concert, and unpack the ZIP file by double clicking it. A folder named jazz is created that contains the client and the SCM command line tools.
  • You can find the Rational Team Concert application as jazz/client/eclipse/Eclipse.app (for RTC 2.0) or jazz/client/eclipse/TeamConcert.app (for RTC 1.0).

The Rational Team Concert Web UI

The Rational Team Concert Web UI runs on both the Mozilla Firefox and Apple Safari Web browsers, though it is officially supported only on Firefox.

Jazz Team Server

Since there is no OS X version of Jazz Team Server, you will have to download the Linux version and edit some scripts and configuration files.

  1. Download the Server ZIP for Linux from the Standard section of the All Downloads page on Jazz.net.
  2. Move the ZIP file to the folder where you want to install Rational Team Concert, and unpack the ZIP file by double clicking it. A folder named jazz is created that contains the Jazz Team Server and the repository command line tools. (If there was already a folder named jazz, unpacking the ZIP file creates a folder named jazz 2. In this case copy the contents of jazz 2 into the jazz folder and remove the empty folder jazz 2).
  3. Open the script server.startup in jazz/server with a text editor:
    1. For RTC 2.0 modify the definition of JRE_HOME to this: 
            JRE_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
      For RTC 1.0 to this: 
            export JRE_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
    2. Append a -XX:MaxPermSize=256m to the JAVA_OPTS variable like this: 
            JAVA_OPTS="-Djava.awt.headless=true -DORACLE_JDBC=$ORACLE_ABSPATH       -DDB2I_JDBC=$DB2I_ABSPATH -DDB2Z_JDBC=$DB2Z_ABSPATH       -Dorg.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin=true       -Dcom.ibm.team.repository.provision.profile=`pwd`/provision_profiles       -Dcom.ibm.team.repository.tempDir=$TEMP_DIR -Xmx700M -XX:MaxPermSize=256m"
    3. Save the server.startup file.
  4. Open the script server.shutdown in jazz/server with a text editor:
    1. For RTC 2.0 modify the definition of JRE_HOME to this: 
            JRE_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
      For RTC 1.0 to this: 
            export JRE_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
    2. Save the server.shutdown file.
  5. Open the configuration file server.xml in jazz/server/tomcat/conf with a text editor:
    1. Search for the string IbmX509 and replace the single occurrence with SunX509
    2. For RTC 2.0 only: in the preceding line replace the string SSL_TLS with SSL.
    3. Save the server.xml file.
  6. To start the Jazz Team Server, open the Terminal application and navigate to jazz/server and run this command: 
      sudo ./server.startup
  7. You can verify that the server is operating properly by connecting a Web browser (e.g. Safari) to this URL https://localhost:9443/jazz/setup. If a certificate warning appears, click Continue. A Jazz Team Server login dialog should appear.
  8. Now is a good time to configure the server. You can find the details under “Running the setup wizard” in jazz/install_standard_zip.html.
  9. Stop the server by running this command: 
      sudo ./server.shutdown

Repository Tools Application

The Repository Tools Application is a standalone application that provides a way to manage a Jazz repository database. It lives in the same directory as the Jazz Team Server scripts, so we are again using the Linux version of the script and have to modify it for Mac OS X.
  1. Open the script repotools.sh in jazz/server with a text editor:
    1. Modify the definition of JAVA to this: 
            JAVA="/usr/bin/java"
    2. Uncomment (remove the leading hash character of) the following definition: 
            DEFINE="$DEFINE -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true"
    3. Save the repotools.sh file.
  2. Now you can run the Repository Tools Application, e.g. to rebuild the fulltext index: 
          ./repotools -rebuildIndices

Jazz Build Engine

The Jazz Build Engine is an Eclipse RPC application that lacks the native launcher application for OS X. The workaround is to launch the Linux version through the equinox launcher.

  1. Download the Build System Toolkit for Linux from the Standard section of the All Downloads page on Jazz.net.
  2. Move the ZIP file to the folder where you want to install Rational Team Concert, and unpack the ZIP file by double clicking it. A folder named jazz is created that contains the build system (If there was already a folder named jazz, unpacking the ZIP file creates a folder named jazz 2. In this case copy the contents of jazz 2 into the jazz folder and remove the empty folder jazz 2).
  3. To start the build engine, open the Terminal application and navigate to jazz/buildsystem/buildengine/eclipse and run this command: 
         java -jar plugins/org.eclipse.equinox.launcher_*.jar -repository https://localhost:9443/jazz/   	   -userId build -pass build -engineId junit -sleeptime 5
    Note that the user ID, password, and engine ID are the ones used by the JUnit example project area. If you do not intend to use the JUnit example, adapt the values accordingly. Make sure that the “build” user has a Developer Client Access License or a Build System Client Access License.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Tue, 23 Jun 2009