About enabling a VOB and installing triggers

Using the Rational ClearQuest Integration Configuration tool that is supplied with DevOps Code ClearCase® integrations, a project manager enables a VOB for the base ClearCase integration. With the tool, you can do the following tasks:

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

This enabling operation installs into the VOB triggers that fire before or after a DevOps Code ClearCase operation. An integration trigger calls the cqcc_launch script which does the following tasks:

Examines the environment to decide where the source for the trigger is stored.
Decides the best version of Perl to use.
Runs the config.pl file which loads the main trigger source code.

On certain DevOps Code ClearCase operations (checkout, checkin, or cancel checkout), the triggers fire and do the following tasks:

Connect to the Rational ClearQuest user database
Run a query for specific change requests in the Rational ClearQuest user database
Display the change request listing and prompt the developers for information

The developer associates change requests with the elements that are being accessed by a DevOps Code ClearCase client. When the DevOps Code ClearCase operation completes, the trigger stores associations (change set) in the Rational ClearQuest user database and uses hyperlinks to store matching information (request set) in DevOps Code ClearCase storage. Thereafter, the result set of the Rational ClearQuest record that has associations displays in the ClearCase tab of the client window the names of the elements (the change set) that are associated with the defect (a change request).