Plug-in Documentation

IBM Rational Team Concert – SCM

 

Overview

The IBM Rational Team Concert SCM source plug-in supports creating components from the Rational Team Concert source-code management system.

Compatibility

  • IBM UrbanCode Deploy version 6.0.1 or later
  • Rational Team Concert version 4.0.3 or later

This plug-in supports all operating systems that are supported by the IBM UrbanCode Deploy agent.

Installation

No special steps are required for installation. See Installing plug-ins in UrbanCode Deploy. The Rational Team Concert scm tool must be installed and available on the IBM UrbanCode Deploy agent that is used to import from Rational Team Concert.

To learn more about using and installing the Rational Team Concert scm tool, see Source control command line reference in the Rational Team Concert help.

To learn more about importing components by using agents, see Creating components.

To learn more about the Rational Team Concert scm tool, see Getting started with the Jazz SCM command line in Rational Team Concert.

To learn more about using Rational Team Concert source control with IBM UrbanCode Deploy, see Achieving continuous deployment with UrbanCode Deploy by integrating with Rational Team Concert.

History

Version 7.1044519

Version 7 includes a fix for APAR PI87707. The user who requested a manual version import is now being tracked.

Version 6.860157

Version 6 includes a change to support property file encryption.

Version 5.796848

Version 5 includes a fix for APAR PI62305. The plug-in now includes the version ID in the returned properties.

Version 4.786648

Version 4 includes a fix for APAR PI57417. The plug-in now checks the agent settings for acceptance of self-signed certificates.

Version 3.753645

Version 3 can import snapshots or live streams from the Rational Team Concert server. The Import Versions Automatically function is improved.

Usage

To create a component by importing from Rational Team Concert source-code management, complete the following steps. For more information, see Creating components in the product help, and the Jazz.net article Achieving continuous deployment with UrbanCode Deploy by integrating with Rational Team Concert.

  1. On the Components page in IBM UrbanCode Deploy, click Create New Component.
  2. In the Source Config Type list, select RTC SCM.
  3. Provide all of the necessary information, such as the RTC Server URL and Command Path to the scm executable file on the agent.
  4. Click Save.
  5. Click the Versions tab for the component.
  6. Click Import New Versions.

Settings

Settings in the IBM Rational Team Concert SCM plug-in

Create Component

The following settings are available when you create a component by using the IBM Rational Team Concert SCM plug-in.

Settings for creating components
Name Type Description
RTC Server URL String The URL of the Rational Team Concert server. For example, https://mycompany.example.com:9443/jazz.
RTC Username String The user name used to connect to the Rational Team Concert server.
RTC Password Password The password used to connect to the Rational Team Concert server.
Stream String The name or alias of the default flow target stream.
Version Naming Convention Enumeration:

  • ID
  • NAME
Use the ID or Name for the Versions Name when Importing Versions Automatically, Importing Stream, or when Import Versions name is left blank.
Includes String A list of ant-style include patterns, separated by newline characters.
Excludes String A list of ant-style exclude patterns, separated by newline characters.
Include Root Boolean Select Include Root to load the component names in the Rational Team Concert stream as top-level folders in the IBM UrbanCode Deploy component.
Command Path String The full path to the scm executable on the IBM UrbanCode Deploy agent, including the file name. For example, D:\IBM\RTCClient\scmtools\eclipse\scm.exe.


Import New Versions

The following settings are available when you import component versions manually by using the IBM Rational Team Concert SCM plug-in.

Settings for importing new versions of components
Name Type Description
Workspace History Enumeration:

  • SNAPSHOT
  • STREAM
Use a snapshot or stream as the initial workspace history.
Version Name String The name given to the imported component version. If snapshot is selected, it will search RTC for this snapshot name. If left blank, the latest snapshots name or ID will be used.