To configure VOBs, branch types, and element types

On a Windows system, log in as the VOB owner and use this window to configure one or more VOBs.
Do the following steps in this window:
  1. Select a VOB from the list of VOB tags. Configuration specifications apply to the selected VOB.

    To specify a VOB that resides on Linux or the UNIX system, first use the Region Synchronizer to import the VOB tag. You can access the Region Synchronizer from the Windows Start menu. Click Start > Programs > IBM Rational > IBM Rational ClearCase > Administration > Region Synchronizer.

  2. In Checkout Policy, specify a policy for associating change requests when checking out versions by setting one of the options:
    • Never prompt the user for change requests. When a user checks out a version, no Associate Change Requests window appears.
    • Prompt the user for optional change requests. When a user checks out a version, the Associate Change Requests window opens. The user can associate zero or more change requests with the version being checked out. If the user later cancels (undoes) the checkout, any associations between change requests and the checked-out version are discarded.
  3. In Checkin Policy, specify a policy for associating change requests when checking in versions by setting one of the options:
    • Never prompt the user for change requests. When a user checks in a version, the Associate Change Requests window does not open.
    • Prompt the user for optional change requests. When a user checks in a version, the Associate Change Requests window opens. The user can associate zero or more change requests with the version being checked in.
    • Prompt user and require one or more change requests. When a user checks in a version, the Associate Change Requests window opens. The user must associate one or more change requests with the version being checked in.
  4. In Branch Type Restrictions, specify branch-type restrictions by setting one of the options:
    • Policies apply to branches of all types.
    • Policies apply to branches of selected types. Choose the branch types by selecting the check boxes for the types listed.
      Tip: All selected branch types must have the same association policies; you cannot specify different policies for different branch types. If you have multiple branch types, and you want the policies to apply to most of them, click Select All; then clear the check boxes of the branch types for which you do not want the policies to apply.
  5. In Windows Trigger Selection and UNIX Trigger Selection, specify whether the integration should use the V1-Visual Basic, V1-Perl, or V2-Perl trigger on checkin, checkout, and uncheckout operations. Prior to Rational® ClearCase® Version v2002.05.00, the integration used a Visual Basic trigger on Windows platforms and a Perl trigger on the UNIX system. In ClearCase v2002.05.00, a Perl trigger that runs on Windows platforms and the UNIX system was added . (This trigger is also available in a patch to Rational ClearCase Release 4.2). Specify which trigger you want to use by clicking V2-Perl or V1-Visual Basic. V1-Visual Basic and V1-Perl refer to the old Visual Basic and Perl triggers. V2-Perl refers to the cross-platform Perl trigger.

    The V2-Perl trigger provides a text-based user interface for developers who use the cleartool command-line interface and a graphic user interface (GUI) for developers who use one of the Rational ClearCase GUIs such as Rational ClearCase Explorer (on Windows platforms) or File Browser (xclearcase on the UNIX system). If you are configuring the integration for the first time, it is better to use the V2-Perl trigger. If you currently use the V1-Visual Basic trigger, evaluate the V2-Perl trigger and consider migrating to it.

    The V2-Perl trigger uses a configuration file, which specifies your local configuration parameters. If you set V2-Perl, the Integration Configuration tool fills in the Path field with CQCC/config.pl, the path to the configuration file, and enables Use trigger scripts in Path directory. In this path, CQCC resolves to ccase-home-dir/lib/CQCC on each local client. By default, the cqcc_launch script is installed in ccase-home-dir/bin on each local client. In this configuration, each time the integration starts or a trigger fires on a client machine, the local instances of the configuration file, the cqcc_launch script, and trigger scripts are run.

    You can change the path so that the integration uses one central configuration file and cqcc_launch script. In Path, specify a UNC path (on the Windows system) or a full path (on the UNIX system) to your config file as you would normally. In this configuration, you use a central configuration file, central cqcc_launch script, and local copies of trigger scripts.

    If you set Use trigger scripts in Path directory, you can use trigger scripts as well as configuration parameters and cqcc_launch script on a central server instead of local copies on the client machines. Triggers installed with this option use the configuration file, cqcc_launch script, and trigger source code in the same location as the configuration file. Placing the trigger scripts in a central location lets you improve security (for example, prevent users from disabling triggers) and increase maintainability (for example, facilitate extending or modifying the original triggers). This is the best configuration because it is easiest to secure and maintain.

    The options for using a central location have the following requirements:

    • For Linux, the UNIX system, or Windows platforms, the path must not have spaces. (This avoids the need for quotation marks in specifying executable file names.)
    • The directory that contains the trigger scripts must be named CQCC (required by the trigger scripts). For example:

      \\server-name\path\CQCC (on the Windows system)

      /global-path/CQCC (on the UNIX system)

    • The directories for the Windows and the UNIX systems must be separate because the launch script differs and the line-termination conventions differ.
    • Copy to the central CQCC directory on the server the entire contents of the directory to which CQCC resolves. On the UNIX system, the config.pl file in the path CQCC/config.pl is a symbolic link to the following location:
      /var/adm/rational/clearcase/config/config.pl

      On the UNIX system, copy the target config.pl file, not the symbolic link. As a result, no symbolic link must be in the central server location.

    • You must copy cqcc_launch.bat (on the Windows system) or cqcc_launch (on the UNIX system) from the ccase-home-dir/bin directory to the central CQCC directory on the server that contains configuration file and, optionally, the Perl trigger scripts.
  6. In Element Type Restrictions, specify element-type restrictions by clicking one of the options:
    • Policies apply to elements of all types.
    • Policies apply to elements of selected types. Choose the element types by selecting the check boxes for the types listed.
      Tip: All selected element types must have the same association policies; you cannot specify different policies for different element types.
  7. In ClearQuest Record Type, enter the default record type to be associated with versions in the selected VOB. The record type must be associated with Rational ClearCase definitions in the Rational ClearQuest® schema database. All versions in a given VOB must be associated with the same Rational ClearQuest record type.
  8. Confirm the settings for the selected VOB in one of the following ways:
    • Click Apply.
    • Click another VOB tag in the list of VOB tags. You are prompted to save changes you made to the previously selected VOB.
    • Click OK to save changes that you made to the selected VOB and exit the Configuration application.

To discard unconfirmed changes to settings for the selected VOB, click Restore VOB Settings. To discard unconfirmed changes to settings for the selected VOB and exit the Configuration application, click Cancel. You cannot discard changes to a VOB after you have confirmed the new settings.


Feedback