Taking control in ClearCase

As a way of introducing ClearCase, we'll go through a typical work-session using it.

At this point your source code is now in XML the format that the UD6/CMtool Driver uses (in the directory c:\cc\sources), and is ready for ‘putting into’ ClearCase. The following describes a ClearCase setup which is a fairly straightforward one and should suffice for your initial evaluation, or to give more advanced ClearCase users an insight into the specifics of using ClearCase with the UD6/CMtool Driver for Uniface.

Before anything else is done, your Uniface source code has to be converted to ClearCase import format.

Copy the XML directory tree to ClearCase import format.

To copy the directory tree c:\cc\sources to ClearCase import format, the ClearCase tool clearexport_ffile is used:

C:\>     cd \cc\sources

C:\cc\sources> clearexport_ffile -r templates globals applications components glyphs menus other registers relationships sub-types tables

Installing and setting up ClearCase.

It is not necessary to create a baseline since ClearCase automatically creates an INITIAL baseline when the VOB is converted to a UCM Component in the final step.

Taking control

Set Case Insensitive MVFS
Create a project VOB
Create a component
Create a project

How to use the driver with ClearCase (cont.)

Configuration information
Releasing a form using ClearCase
Checking a form in using ClearCase
Adding a form using ClearCase
Finding the differences in versions using ClearCase
Problems when using ClearCase

UD6 Overview
A methodology to Uniface source code control
Using UD6/CMtool and Uniface with ClearCase.

$Revision: 1.11 $ $Date: 2011/02/28 02:56:32 $[go to top]