Topics of this section describe Collaborator integration with IBM Rational ClearCase.

ClearCase Server Integration

To take advantage of ClearCase integration, configure the Collaborator server so that it communicates with a ClearCase repository directly, without any client software.

GUI Client

The GUI Client can scan ClearCase for checked-out files and upload them before they are checked in. It uploads changes from your activities or changes from an activity or activities that you name. It can also upload any versions of ClearCase files after they are checked in.

Command-Line Client

The Command-Line Client can scan for checked-out files and upload them before they are checked in, upload any versions of ClearCase files after they are checked in, or upload UCM change sets for review.

Eclipse Plug-in

The Eclipse Plug-in integrates with the IBM Rational ClearCase SCM Adapter plug-in or with the open source ClearCase plug-in for Eclipse so you can upload locally modified files with full support from your ClearCase eclipse plug-in.

Supported Versions

Our integration uses your own ClearCase command-line client (cleartool) to communicate with the server. We support these versions:

Because we use client applications already present on your computer, we support all protocols, authentications, proxies, and other client configuration options you are currently using.

Support for ClearCase UCM

Collaborator supports ClearCase UCM activities. The change set associated with a ClearCase activity can be added to a review using the   Command-Line Client addactivity command. For each file in the activity, the latest version in the activity and the predecessor of the earliest version in the activity are uploaded to the review.

A Note about ClearCase Activities

Uploading activities for review generates file differences based on Multiple Version Changelists. Uploading activities is not supported by Rational ClearCase Remote Client.

Support for ClearCase Remote Client (CCRC 9.x only)

Collaborator integration with CCRC uses the Rational Change Management Server API. When running the Collaborator client installer, there is an edit field allowing you to select the location of the Rational CM API jar files on your system. The required files are:

remote_core.jar

stpcc.jar

stpcmmn.jar

stpwvcm.jar

These files are installed by the ClearCase Remote Client under the Rational Shared Resource Directory. The directory should look similar to one of the following:

C:\Program Files\IBM\IMShared\plugins\com.ibm.rational.teamapi_9.0.0.vNNNNNNNN, or

/opt/eclipse/plugins/com.ibm.rational.teamapi_9.0.0.vNNNNNNNN

Launch Collaborator client installer with administrator privileges, find the location of the Rational CM API jar files on your system and specify it in the "CM API Directory" field during installation. The installer will copy the abovementioned jar files to the following subdirectory under the Collaborator client installation directory:

<Collaborator Client>/ui/plugins/com.smartbear.collaborator_14.9.xxxx

After that, the Collaborator client would become able to use the Rational Change Management Server API.

If using the RPM installer, you will have to manually copy these jar files to the correct subdirectory.

Once installed, create a ClearCase SCM configuration using the the same connection parameters to the ClearCase CM server as your ClearCase Remote Client. These are your username and password, and the ClearCase TeamWeb services URL. For example, if your ClearCase server host name is cc-server, the default server URL would be:

http://cc-server:16080/ccrc

Be careful to specify your connection parameters correctly. These parameters are not authenticated up front, instead calling back when server activity must take place. If the authentication is wrong, a cascade of errors can occur which can exhaust the RPC connections to the CM server.

Troubleshooting CCRC Views

ClearCase Remote Client views can get corrupted in a way that causes the CM API to generate exceptions when trying to upload CCRC files to a review. We do not know the cause of these exceptions, but selecting "Refresh->Repair->Vob Tag Directories" from the view context menu in the CCRC client, or deleting and recreating the view, fixes this condition.

Technical Details and Limitations

Collaborator does not guarantee that Diff Viewer will display correct comparison results for the following cases: