About configuring a VOB, branch types and element types

Using the base ClearCase® Integration Configuration tool on a Windows system, a Rational® ClearCase project manager performs the following steps:

Selects a VOB to enable and install triggers.
Specifies a policy for checkouts, checkins, and branch types.
Selects the version of triggers to use (either V2-Perl or V1-Visual Basic) and, for V2-Perl triggers, selects whether to use a central server configuration and trigger files.
Specifies element type restrictions, branch type restrictions, or both.
Specifies the default Rational ClearQuest® record type to be used in associations.

For information about procedures for a VOB that resides on Linux or the UNIX system, see Installing triggers in a VOB on Linux or the UNIX system. The help for the configuration tool window describes the details of the settings.

The project manager sets a policy for each VOB for associating versions with change requests. This policy determines when the Associate Change Requests window opens (for the graphic user interface) or a prompt appears (for the command line interface). Policies can specify that developers must make associations when they check out a version, check in a version, or both. A policy can also specify that prompting occurs only for some branch types or element types. Associations of checked-in versions with change requests can be either optional or required.

If a policy specifies that developers are prompted when they check out a version, the tool defines a trigger type in the VOB that causes a trigger to fire on checkout and opens the Associate Change Requests window. A trigger type also causes a trigger to fire when a checkout is canceled and to remove any associations with change requests for the checked-out version. If a policy specifies that developers are prompted when they check in a version, the tool defines a trigger type in the VOB that causes a trigger to fire on checkin and opens the Associate Change Requests window.

The base ClearCase Integration Configuration tool is started from the Windows Start menu.

About other configuration tasks

To configure the integration completely, a project manager must also ensure that the following tasks are done:

The ClearCase 1.0 package has been added to an existing Rational ClearQuest schema.
A configuration file (config.pl) has been set up with the appropriate configuration parameter values.

For more information about these tasks, see IBM Rational ClearCase Guide to Managing Software Projects.

Installing triggers in a VOB on Linux or the UNIX system

If the VOB resides on Linux or the UNIX system, install the triggers from a Windows system that uses the same registry server as the system on which the VOB resides. The VOB tag must be imported from the region in which the Linux and the UNIX systems run to the region in which the Windows system runs. Then, you can use the base ClearCase Integration Configuration tool.