ConfiguringUbuntuForRTCClients < Deployment

<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> Configuring Ubuntu for Rational Team Concert clients
%DKGRAY% Authors: Main.MichaelAfshar, Main.SudarshaWijenayake <br>
Build basis: Rational Team Concert clients 3.x and higher
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

You must configure your Ubuntu system before you can use Rational Team Concert clients.

---++ Configuring Rational Team Concert Eclipse client 

---+++ Before you begin

For the supported versions of Ubuntu client, see the [[DeploymentInstallingUpgradingAndMigrating][System Requirements page]].

For Rational Team Concert Eclipse client to display correctly in Ubuntu, you must have the Mozilla XULRunner plug-in installed. The XULRunner plug-in is not included in the Rational Team Concert Eclipse client installation, therefore, the plug-in must be manually installed if it does not exist on your system. To determine if your system includes the XULRunner plug-in, open the Rational Team Concert Eclipse client and if the Welcome screen looks like figure 1, the XULRunner plug-in is missing. 

 _Figure 1: Welcome page with missing XULRunner plug-in_ <br />
<img src="%ATTACHURLPATH%/welcomePageNoXULRunner.png" alt="welcomePageNoXULRunner.png" width="1012" height="700" />

Not all versions of Eclipse are compatible with all versions of XULRunner. For a complete list of compatible versions, see [[http://eclipse.org/swt/faq.php#browserlinux][http://eclipse.org/swt/faq.php#browserlinux]].

---+++ Downloading a compatible version of XULRunner
If your operating system is 32-bit, you can download a compatible version of XULRunner from [[http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/][http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/]].

If you have a 64-bit operating system, you must download 64-bit binaries from one of the nightly builds, as only the 32-bit versions are available from the official releases. The main directory for nightly builds can be found at [[http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/][http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/]].

Both the 3.6 and 4.2 versions of Eclipse support all releases of version 1.9.x of XULRunner. XULRunner 1.9.1 can be downloaded from [[http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2009/12/2009-12-08-03-mozilla-1.9.1/][http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2009/12/2009-12-08-03-mozilla-1.9.1/]].

Both releases and nightly builds include SDK archives and runtime archives. Only the runtime archive is required for running the Rational Team Concert clients.

---+++ Procedure

   1 After downloading the required version of the XULRunner plug-in archive, extract it to a directory on your drive, for example, =/opt/IBM/TeamConcert/XULRunner=.
   1 Go to the installation directory of Rational Team Concert Eclipse client.
   1 Open the eclipse.ini file for editing and enter the following line at the end of the file:<verbatim>-Dorg.eclipse.swt.browser.XULRunnerPath=/opt/IBM/TeamConcert/XULRunner</verbatim>
   1 Save the eclipse.ini file and launch the Rational Team Concert Eclipse client. If the Welcome screen looks like figure 2, XULRunner is working properly.

 _Figure 2: Welcome page with XULRunner plug-in properly installed_ <br />
<img src="%ATTACHURLPATH%/welcomePageXULRunner.png" alt="welcomePageXULRunner.png" width="996" height="682" />


---++ Configuring Built system Toolkit

Because Build System Toolkit is only available as a 32-bit binary, you might have difficulty installing it on a 64-bit version of Ubuntu. If you encounter the =jbe: no such file or directory= error message, or the Jazz Build Engine crashes because it cannot find =jre/bin/jave=, even though the file does exist, you will need to enable support for 32-bit architecture.

---+++Procedure

   1 To confirm the default architecture for your computer, open a terminal and enter: <verbatim>dpkg --print-architecture</verbatim> If the output is =amd64=, then you must install libraries that support a 32-bit foreign architecture.
   1  To install the 32-bit packages, you must be logged into your terminal session as root or have permission to execute commands by using sudo. In your terminal enter the following command: <verbatim>apt-get install ia32-libs</verbatim> This initiates a long package installation process that installs the 32-bit versions of the core libraries.
   1 After installation completes, confirm that the installation was successful by typing the following command: <verbatim>dpkg --print-foreign-architectures</verbatim> If the installation was successful, the output should be =i386=.

 _Figure 3: Terminal with i386 output_ <br />
     <img src="%ATTACHURLPATH%/i386.png" alt="i386.png" width="739" height="68" />

You should now be able to run the Jazz Build Engine normally. 

---+++++!! Related topics:
---+++++!! External links:          
---+++++!! Additional contributors: 

<sticky></div></sticky>
This topic: Deployment > WebHome > DeploymentInstallingUpgradingAndMigrating > ConfiguringUbuntuForRTCClients
History: r4 - 2013-12-06 - 23:56:24 - Main.mafshar
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
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.