CC Intro

Rational ClearCase and ClearCase LT
Version 7.0.0
Windows, UNIX, and Linux
Introduction
GI11-6360-00
Rational ClearCase and ClearCase LT
Version 7.0.0
Windows, UNIX, and Linux
Introduction
GI11-6360-00
Before using this information, be sure to read the general information under Notices, on page 37.
7th edition (May 2006) This edition applies to version 7.0.0 of IBM Rational ClearCase (product number 5724G29) and IBM Rational ClearCase LT (product number 5724G31) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces G126-5309-00. Copyright International Business Machines Corporation 1992, 2006. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . v Tables . . . . . . . . . . . . . . . vii Preface . . . . . . . . . . . . . . . ix About this book . . . . . . . . . . . xi
User Roles and the Rational ClearCase Documentation Set . . . . . . . . . . . Who should read this book . . . . . . . . Related information . . . . . . . . . . Rational ClearCase documentation roadmap . Rational ClearCase LT documentation roadmap Rational ClearQuest documentation roadmap Typographical conventions . . . . . . . . Contacting IBM Customer Support for Rational software products . . . . . . . . . . . Downloading the IBM Support Assistant . . . xi . xi . xii . xii xiii xiv . xiv . xv . xv Creating labels . . . . . . . . . Using metadata to implement policies . Integrating base ClearCase with Rational ClearQuest . . . . . . . . . . Rational ClearCase MultiSite . . . . . . . . . . . . . . 18 . 18 . 19 . 19
Chapter 2. Planning for and installing Rational ClearCase . . . . . . . . . 21

Planning issues . . . . . . . . . . . Using Unified Change Management or base ClearCase . . . . . . . . . . . . Integrating with Rational ClearQuest . . . Planning to use Rational ClearCase MultiSite Rational ClearCase site preparation . . . . Installation requirements . . . . . . . Running site preparation . . . . . . . Installing Rational ClearCase server software . Installing Rational ClearCase on individual computers . . . . . . . . . . . . . . . . . . . . . . . 21 . . . . . . . 21 22 22 22 22 23 23
. 24
Summary of changes . . . . . . . . xvii Chapter 1. Overview of Rational ClearCase . . . . . . . . . . . . . . 1

Benefits of using Rational ClearCase . . . . . . 1 Basic terminology of Rational ClearCase . . . . . 1 Differences between Rational ClearCase and Rational ClearCase LT . . . . . . . . . . . . . . 4 Using Unified Change Management . . . . . . 5 UCM terminology . . . . . . . . . . . 5 Creating a project . . . . . . . . . . . . 8 Joining a project . . . . . . . . . . . . 10 Delivering work to the integration stream . . . 10 Rebasing private work areas . . . . . . . . 11 Implementing development policies . . . . . 12 Integrating UCM with Rational ClearQuest . . . 12 Using base ClearCase . . . . . . . . . . . 13 Terminology . . . . . . . . . . . . . 13 Setting up a project . . . . . . . . . . . 15 Planning a branching strategy . . . . . . . 16 Using a private branch . . . . . . . . . 16 Merging work between branches . . . . . . 17 Creating standardized config specs . . . . . 18
Chapter 3. Working in Rational ClearCase . . . . . . . . . . . . . 25

Project managers . . . . . . . . . . . Using UCM . . . . . . . . . . . . Using base ClearCase . . . . . . . . . Developers working on Windows . . . . . . Developers working on Linux or the UNIX system Working in UCM . . . . . . . . . . Working in base ClearCase . . . . . . . Using cleartool . . . . . . . . . . . . Using Rational ClearCase integrations with IDEs . Microsoft Visual Studio.NET . . . . . . . Rational Application Developer for WebSphere Software . . . . . . . . . . . . . Using the Rational ClearCase Web interface . . Using the Rational ClearCase Remote Client . . . . . . . . . . . 25 25 25 26 27 28 28 28 29 29
. 29 . 30 . 31
Glossary . . . . . . . . . . . . . . 33 Appendix. Notices . . . . . . . . . . 37 Index . . . . . . . . . . . . . . . 41
Copyright IBM Corp. 1992, 2006
iii
iv
IBM Rational ClearCase and ClearCase LT: Introduction
Figures
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Elements and their versions . . . . . . Storing elements in a versioned object base (VOB) . . . . . . . . . . . . . . Using the check out/check in model . . . Using a view to see shared elements . . . An activity . . . . . . . . . . . . A stream . . . . . . . . . . . . . A baseline . . . . . . . . . . . . Composite baseline . . . . . . . . . Private work areas . . . . . . . . . Shared work area . . . . . . . . . Delivering work to the integration stream Rebasing the development stream . . . . Using a Rational ClearQuest to-do list to find UCM activities . . . . . . . . . . Branches . . . . . . . . . . . . . 2 . 3 . 3 . 4 . 6 . 6 . 7 . 8 . 9 . 10 11 . 12 . 13 . 14 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. Version label . . . . . . . . . . . Selecting versions used in development work Selecting versions included in a particular release . . . . . . . . . . . . . Branches in a file system directory tree Working on a private branch . . . . . . Merging branches . . . . . . . . . Rational ClearCase MultiSite VOB family Rational ClearCase Project Explorer . . . Rational ClearCase Explorer . . . . . . Rational ClearCase integration with Visual Studio.NET . . . . . . . . . . . Rational ClearCase integration with Application Developer . . . . . . . . Rational ClearCase Web interface . . . . . 14 15 . 15 16 . 17 . 18 20 . 25 . 27 . 29 . 30 . 31
vi
Tables
1. 2. Features in Rational ClearCase that are not in Rational ClearCase LT . . . . . . . . . 4 Rational ClearCase objects created by installation procedure . . . . . . . . . 23 3. Frequently used cleartool commands . . . . 28
vii
viii
Preface
Rational ClearCase and Rational ClearCase LT are configuration management (CM) systems that manage multiple versions of evolving software systems. Rational ClearCase is IBM's enterprise configuration management solution for large development teams working in parallel. Rational ClearCase LT contains a subset of Rational ClearCase features and is suitable for customers who do not need the scalability, flexibility, and robustness provided by Rational ClearCase. Rational ClearCase MultiSite is an optional add-on product that extends Rational ClearCase by supporting parallel development across geographically distributed project teams. Unless otherwise noted, Rational ClearCase refers to both Rational ClearCase and Rational ClearCase LT throughout this manual.
ix
About this book

This book provides the following information about Rational ClearCase: v Description of the products features, concepts, and main user workflows v Overview of the planning and installation process v Overview of the products main tools and user interfaces In this manual, the references to Windows apply to all Microsoft Windows platforms on which Rational ClearCase is supported. References to the UNIX system apply to all platforms running the UNIX system on which Rational ClearCase is supported. References to Linux apply to all Linux platforms on which Rational ClearCase is supported. See the IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT Installation and Upgrade Guide for a current list of operating systems supported by Rational ClearCase.
User Roles and the Rational ClearCase Documentation Set

Rational ClearCase documentation consists of task-oriented information, supporting Rational ClearCase users acting in the following roles: v Project manager Defines, implements, and manages the objects, policies, and processes of a software development project v Developer Makes changes to the software configuration (that is, the files and directories) of a software development project v Integrator (also called build engineer or release engineer) Builds and integrates the products of a software development project v Administrator Configures and maintains the Rational ClearCase infrastructure, including Rational ClearCase VOBs, views, servers, and clients, for part or all of your organization
Who should read this book

This book is intended for evaluators and new users of Rational ClearCase. This book provides information about how using Rational ClearCase enables development teams to work more efficiently to produce high quality work in less time. This book assumes familiarity with basic configuration management concepts such as parallel development, version control, and project policy implementation.
xi
Related information Rational ClearCase documentation roadmap

Orientation Introduction Release Notes Online tutorials
Software Development Developing Software (online help)
Project Management Guide to Managing Software Projects More Information Command Reference Online documentation Help files
Build Management Guide to Building Software OMAKE Guide (Windows platforms)
Administration Installation and Upgrade Guide Administrator's Guide (Rational ClearCase/ Rational ClearCase LT) Administrator's Guide (Rational ClearCase MultiSite) Platforms Guide (Rational ClearCase)
Guide to Deployment Tracking (Rational ClearCase/Rational ClearQuest)
xii
Rational ClearCase LT documentation roadmap

Orientation Online tutorials Release Notes Introduction
Software Development
Project Management Guide to Managing Software Projects
Developing Software (online documentation)
More Information Command Reference Online documentation Help files
Administration
Installation and Upgrade Guide Administrator's Guide
About this book
xiii
Rational ClearQuest documentation roadmap

Orientation Introduction Release Notes (See online documentation)
Designer tutorials (See online documentation)
Database Design Administrator's Guide (Rational ClearQuest) API Reference (See online documentation) More Information Online documentation Help files
Project Management Using Project Tracker (Windows platforms; see online documentation)
Administration Installation Guide (Rational Desktop Products) Installation Guide (Rational Server Products) Installation Guide (UNIX) Administrator's Guide (Rational ClearQuest) Administrator's Guide (Rational ClearQuest MultiSite) Upgrade Guide (Rational Suite)
Typographical conventions
This manual uses the following typographical conventions: v ccasehomedir represents the directory into which Rational ClearCase, Rational ClearCase LT, or Rational ClearCase MultiSite has been installed. By default, this directory is /opt/rational/clearcase on the UNIX system and C:\Program Files\Rational\ClearCase on Windows. v cquest-home-dir represents the directory into which Rational ClearQuest has been installed. By default, this directory is /opt/rational/clearquest on the UNIX system and C:\Program Files\Rational\ClearQuest on Windows. v Bold is used for names the user can enter; for example, command names and branch names. v A sans-serif font is used for file names, directory names, and file extensions. v A serif bold font is used for GUI elements; for example, menu names and names of check boxes. v Italic is used for variables, document titles, glossary terms, and emphasis.
xiv
v A monospaced font is used for examples. Where user input needs to be distinguished from program output, bold is used for user input. v Nonprinting characters appear as follows: <EOF>, <NL>. v Key names and key combinations are capitalized and appear as follows: Shift, Ctrl+G. v [ ] Brackets enclose optional items in format and syntax descriptions. v { } Braces enclose a list from which you must choose an item in format and syntax descriptions. v | A vertical bar separates items in a list of choices. v ... In a syntax description, an ellipsis indicates you can repeat the preceding item or line one or more times. Otherwise, it can indicate omitted information. Note: In certain contexts, you can use ... within a pathname as a wildcard, similar to * or ?. For more information, see the wildcards_ccase reference page. v If a command or option name has a short form, a slash ( / ) character indicates the shortest legal abbreviation. For example:
lsc/heckout
Contacting IBM Customer Support for Rational software products

If you have questions about installing, using, or maintaining this product, contact IBM Customer Support as follows: The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support Home page for Rational products can be found at http://www.ibm.com/software/rational/support/. Voice Support is available to all current contract holders by dialing a telephone number in your country (where available). For specific country phone numbers, go to http://www.ibm.com/planetwide/. Note: When you contact IBM Customer Support, please be prepared to supply the following information: v Your name, company name, ICN number, telephone number, and e-mail address v Your operating system, version number, and any service packs or patches you have applied v Product name and release number v Your PMR number (if you are following up on a previously reported problem)
Downloading the IBM Support Assistant

The IBM Support Assistant (ISA) is a locally installed serviceability workbench that makes it both easier and simpler to resolve software product problems. ISA is a free, stand-alone application that you download from IBM and install on any number of machines. It runs on AIX, (RedHat Enterprise Linux AS), HP-UX, Solaris, and Windows platforms. ISA includes these features: v Federated search v Data collection
About this book
xv
v Problem submission v Education roadmaps For more information about ISA, including instructions for downloading and installing ISA and product plug-ins, go to the ISA Software Support page. IBM Support Assistant: http://www.ibm.com/software/support/isa/
xvi
Summary of changes
This edition includes the following changes: v Using the Rational ClearCase Remote Client on page 31 features information about how the Rational ClearCase Remote Client enables you to perform Rational ClearCase operations over wide-area networks (WANs), local-area networks (LANs), and dial-up connections.
xvii
xviii
Chapter 1. Overview of Rational ClearCase

This chapter introduces features of Rational ClearCase and Rational ClearCase LT, and describes different models for using the products. This chapter also introduces Rational ClearCase MultiSite. Unless otherwise noted, Rational ClearCase refers to both Rational ClearCase and Rational ClearCase LT. Rational ClearCase features two configuration management interfaces: v Unified Change Management (UCM), an activity-based change management process included in Rational ClearCase. v Base ClearCase, which is a set of tools can be used to create a configuration management solution tailored to a particular development environment.
Benefits of using Rational ClearCase

Rational ClearCase can be used to manage and track all software assets, whether they are mission-critical software artifacts, documentation, Web pages, or source code. Like other source code control tools, Rational ClearCase can be used to: v v v v v v Create new versions of a software artifact Compare versions of a software artifact Merge changes from one version of an artifact into another version Control simultaneous changes to a software artifact Mark certain versions of artifacts as stable sources to be used in builds Determine the who, when, and why of a particular change to an artifact
Rational ClearCase also provides advantages to different development team members: v Team leaders can coordinate the activities of people developing products together v Project managers have control over the extent and frequency with which team members synchronize their work v Developers can work in parallel, developing their artifacts in private areas so that the work of other team members is not affected by their changes v Integrators can combine the efforts of the team in a controlled manner
Basic terminology of Rational ClearCase

It is helpful for you to understand the following terms before learning about the most important features of Rational ClearCase: v File element v Version v Versioned object base (VOB) v Check out-edit-check in model v View A file element is a file that contains source code, requirements data, visual models, HTML source, XML source, or other data that can be stored in a file system.
A directory element contains file elements and other directory elements. A version is a specific revision of an element. For instance, instead of overwriting the same copy of a draft each time you work on it, you store a copy of the first version, the second version, and so on. Figure 1 displays several elements and their versions.
prog.c 0
util.h 0
msg.cat 0
lib.c 0
3 4
Figure 1. Elements and their versions
3 4
A versioned object base, or VOB, is a secure repository that stores versions of file elements and directory elements. Figure 2 displays a VOB.
VOB
prog.c 0
util.h 0
msg.cat 0
lib.c 0
3 4
Figure 2. Storing elements in a versioned object base (VOB)
Rational ClearCase's check out-edit-check in model enables you to manage changes to your project. When you check out an element, an editable copy of the element is created in your view. When you check in an element, a new version of it is added to your VOB. For example, you can check out a chapter of a book from the documentation VOB. You can then work on a copy of the chapter in your view. When you want your changes to become a part of a new version of the chapter, you can save the changes and check in the chapter, as displayed in Figure 3.
Checking out the version

Figure 3. Using the check out/check in model
Checking in the version
A view provides access to a specific version of one or more elements in a VOB. It lets you select a set of versions of elements that you want to work on, without requiring you to explicitly specify the versions. It also provides a workspace, displayed in Figure 4, in which you can work on tasks in isolation from other developers. For example, as you work on the latest version of a Web page, no one can see the changes you make until you check in your work to the VOB.
Name View Activities (UCM only)

pat_v1.4_CropCircle My Activities doc guivob lib.c msg.cat
Versions of file elements

prog.c util.h src temp lost+found hello_world
Versions of directory elements
Figure 4. Using a view to see shared elements
Differences between Rational ClearCase and Rational ClearCase LT

This manual describes Rational ClearCase and Rational ClearCase LT. Rational ClearCase is an enterprise configuration management system designed for medium to large development teams working in parallel. Customers who do not need the scalability, flexibility, and robustness provided by Rational ClearCase can use Rational ClearCase LT as their configuration management solution. Table 1 describes the main differences between Rational ClearCase and Rational ClearCase LT.
Table 1. Features in Rational ClearCase that are not in Rational ClearCase LT Feature Dynamic views Description Rational ClearCase and Rational ClearCase LT offer snapshot views. Snapshot views work by copying versions of elements from VOBs to your computer. Your snapshot view will need to be updated periodically to see the latest versions of elements. An update operation copies the latest versions of elements from the VOB to your view. Rational ClearCase also offers dynamic views. A dynamic view uses the Multiversion File System (MVFS) to provide immediate, transparent access to data stored in VOBs. When you work in a dynamic view, you do not need to copy data from VOBs to your view; you see the latest versions of elements in real time. Multiple servers Rational ClearCase and Rational ClearCase LT use a client-server architecture. A Rational ClearCase client process issues a request for a Rational ClearCase operation, such as checkout or checkin. Server processes that run on the host where the VOB resides handle the request. Rational ClearCase supports a multiple server configuration, so VOBs can be located on multiple, distributed hosts. Rational ClearCase LT supports a single server configuration, so VOBs can be located on only one server host.
Table 1. Features in Rational ClearCase that are not in Rational ClearCase LT (continued) Feature Advanced build tool Description You can use the Rational ClearCase commands clearmake, omake, and clearaudit to perform makefile based builds of software systems. These commands provide the following powerful features: v Build auditing, with automatic detection of source dependencies, including header file dependencies v Automatic creation of permanent bill-of-materials documentation of the build process and its results v Sophisticated build-avoidance algorithms to guarantee correct results when building in a parallel development environment v Sharing of binaries among views, saving both time and disk storage v Parallel building, which applies the resources of multiple processors and multiple hosts to builds of large software systems These features are available only if you use dynamic views; therefore, they are available in Rational ClearCase but not in Rational ClearCase LT. Rational ClearCase MultiSite Rational ClearCase MultiSite is an optional add-on to Rational ClearCase. Rational ClearCase MultiSite can be used for parallel software development and software reuse across geographically distributed project teams. Rational ClearCase MultiSite is not supported with Rational ClearCase LT.
Using Unified Change Management

UCM structures the work of a project team into a defined, consistent, repeatable process. This section provides an overview of key concepts and tasks involved in using UCM.
UCM terminology
A project is a specific product of a development effort, such as a corporate Web site or order fulfillment process. In UCM, a project is an object that contains the configuration information (for example, components, activities, and policies) needed to manage and track work on a product. A typical UCM project in Rational ClearCase consists of one shared work area and many private work areas (one for each developer). A component is a group of source code and other relevant elements or files, such as a license module or a GUI, that the team develops, integrates, and releases as a unit. Components constitute parts of a project. An activity is an object that records the set of files (known as the change set) that a developer creates or modifies to complete and deliver a development task, such as a bug fix.Figure 5 displays an activity. Other activities could include an update to a help file or the addition of a menu item to a GUI component.
Fixing bug 2144 Creator: pat lib.c, version 4 prog.c, version 5

Figure 5. An activity
Headline Activity creator Change set
A work area consists of a view and a stream. As described in Basic terminology of Rational ClearCase on page 1, a view is a directory tree that shows a single version of each file in your project. A stream is an object that maintains a list of activities and baselines, and determines which versions of elements are shown in your view.Figure 6 displays an example of a stream.
View
Fixing bug 2144 l prog.c, version 5 l lib.c, version 4
Activity
Baseline
Figure 6. A stream
Stream
A project contains one integration stream, which records the projects baselines and enables access to versions of the projects shared elements. The integration stream and a corresponding integration view represent the projects primary shared work area. Each developer on a project has a private work area, which consists of a development stream and a corresponding development view. The development stream maintains a list of the developers activities and determines which versions of elements are displayed in the developers view. Although the integration stream is the projects primary shared work area, project managers can designate a development stream to be a shared work area for several developers who are working on the same feature.
A baseline identifies one version of each element in a component that represents the integrated or merged work of team members, as displayed in Figure 7. A baseline represents a version of a component at a particular stage in project development, such as the first draft of a book, a beta release, or a final product release. As milestones are reached throughout the project lifecycle, the project manager creates and recommends baselines and changes their promotion level attributes to reflect these milestones.
Element
Version
Component Baseline
Figure 7. A baseline
When developers join a project, they populate their work areas with the versions of directory and file elements represented by the projects recommended baselines. Alternatively, developers can join a project at a feature-specific development stream level, where they populate their work areas with the development streams recommended baselines. This practice ensures that all members of the project team base their development on the same set of files. If your project team works on multiple components, you may consider using a composite baseline. A composite baseline is a baseline that selects baselines in other components. In Figure 8, the ProjBL1 composite baseline selects baselines BL1 and BL2 of components A and B, respectively. The Proj component does not contain any elements of its own. Its sole purpose is to contain the composite baseline that selects the recommended baselines of the projects components. By using a composite baseline in this manner, you can identify one baseline to represent the entire project.
Component A
Component Proj
Baseline BL1
PB1
Component B
Baseline Baseline BL2
Figure 8. Composite baseline
Creating a project
Before creating a UCM project, the project manager maps files and directories in the product architecture to a set of UCM components. Using utilities provided in Rational ClearCase, the project manager or administrator converts existing files and directories from other version control software systems to elements in a VOB. For details about importing existing files and directories into Rational ClearCase components, see the IBM Rational ClearCase Guide to Managing Software Projects and the IBM Rational ClearCase Administrators Guide. The project manager then creates a UCM project, along with its baselines and integration stream, with the Rational ClearCase Project Explorer. A new project can be created from scratch or populated with baselines from an existing project. The project includes a private work area for each developer, displayed in Figure 9, and one shared work area, displayed in Figure 10. The project manager manages the shared work area. These areas are explained in more detail in Joining a project on page 10 and Delivering work to the integration stream on page 10.
Pat's development stream Joe's development stream Chris's development stream
Baseline BL1
Figure 9. Private work areas
Pat's integration view Joe's integration view Integration stream
Chris's integration view
Figure 10. Shared work area
Joining a project
To join the UCM project, use the Join Project wizard to create a development stream, a development view, and an integration view. The development stream and development view make up the private work area, where you work on activities. You use the development view to access and change elements. The development stream determines which versions of elements are displayed in each development view. The integration view gives developers and project managers access to work that has been delivered to the shared work area.
Delivering work to the integration stream

The project manager created the UCM project with one shared work area, or integration stream. When you are ready to integrate your work with the work of your team, you deliver your work from your development stream to the integration stream. The deliver operation may involve a merge if other team members have already delivered versions of one or more of the same elements, as displayed in Figure 11.
10
Development stream Deliver Integration stream
Baseline BL1
Figure 11. Delivering work to the integration stream
After all team members' work is delivered and merged, you use the integration view to build and test work in the integration stream. The integration stream determines which versions of delivered elements are displayed in the integration view.
Rebasing private work areas

Periodically, the project manager creates new baselines. Each new baseline includes work that has been delivered since the last baseline was created. When a new baseline passes a certain level of testing, the project manager promotes it, designating it as the projects recommended baseline. You then update, or rebase, your development stream to use the new recommended baseline, as displayed in Figure 12. The rebase operation updates the development view to include versions from the new baseline. If the baseline includes new versions of the same element that you checked in from a private work area (that is, if other developers have checked in and delivered new versions of the same element to the integration stream), the rebase operation merges the new versions into your development stream.
11
Development stream Rebasing
Baseline BL1
Baseline BL2
Figure 12. Rebasing the development stream
Implementing development policies

UCM includes a set of policies that you can use to enforce development practices among members of the project team. By setting policieson projects and streams, you can improve communication among project team members and minimize problems you may encounter when integrating their work. For example, you can set a policy that requires developers to update their work areas with the projects latest recommended baseline before they deliver work to the integration stream. This practice reduces the likelihood that developers will need to work through complex merges when they deliver their work. For a description of all policies that you can implement in UCM, see IBM Rational ClearCase Guide to Managing Software Projects. In addition to the set of policies that UCM provides, you can create triggers on UCM operations to enforce customized development policies. A trigger is a mechanism that specifies one or more programs or actions to be run whenever a given Rational ClearCase operation is performed. For details about creating triggers, see the IBM Rational ClearCase Command Reference and the IBM Rational ClearCase Administrators Guide.
Integrating UCM with Rational ClearQuest

Rational ClearQuest is a change request management solution. Using Rational ClearQuest, team members can submit change requests for their product, view and modify existing change requests, and create and run user-specific or site-specific queries and reports to determine project status. The Rational ClearQuest integration with UCM provides activity management capabilities by linking project activities in UCM to corresponding records in a Rational ClearQuest user database. The integration enables the project team to track an activitys progress from creation through completion. Project managers can assign activities to developers, and developers can use Rational ClearQuest queries, as displayed in Figure 13, to find their assigned activities. Because activities have corresponding records in a Rational ClearQuest user database, project managers can use the query, reporting, and charting utilities in Rational ClearQuest to help manage their projects.
12
Headline Anti-virus program crashes Use one button to stop and start Integrate product with Eclipse
State Active Active Active
State Type Active Active Active
UCM Project CropCircle_1.4 CropCircle_1.4 CropCircle_1.4
View
UCM Stream pat_CropCircle_1.
pat_CropCircle_1
pat_CropCircle_1. pat_CropCircle_1.
Result set
Query editor
Display editor
SQL editor
Figure 13. Using a Rational ClearQuest to-do list to find UCM activities
For information about planning and setting up the Rational ClearQuest integration with UCM, see the IBM Rational ClearCase Guide to Managing Software Projects. For information about working on activities in a project that is linked to a Rational ClearQuest user database, see the IBM Rational ClearCase Developing Software Manual.
Using base ClearCase

A project team can use Rational ClearCase tools to develop its own system of managing and tracking software resources. This section describes the basic steps involved in setting up a work environment in base ClearCase. For more information about creating a customized configuration management environment, see the IBM Rational ClearCase Guide to Managing Software Projects, and the IBM Rational ClearCase Administrators Guide.
Terminology
A branch is an object that specifies a sequence of versions of an element. Each element has one main branch , which represents the principal line of development. Each element may also have multiple subbranches, each of which represents a separate line of development. A branch is displayed in Figure 14.
13
util.h main 0
2
r1_bugs
3
0
4
1
bug404
2
0
3
1
Figure 14. Branches
A label can be attached to any version of an element to identify that version in a meaningful way. A single version of an element can have several different labels. Labels are usually applied to a set of elements to mark important project milestones. Labels can also be applied to a specific version of an element to indicate the proposed starting point of a branch, a displayed in Figure 15.
util.h main 0
V1.0
3 4
Figure 15. Version label
14
A configuration specification, or config spec, contains rules used by a view to select versions of elements. The rules are very flexible, and you can use various criteria to indicate which versions of elements you want the view to display. For example, a config spec for a view used in ongoing development could contain a rule that selects the latest version on the development branch, as displayed in Figure 16.
prog.c 0
util.h 0
msg.cat 0 V1.0
lib.c 0
1 V1.0
1 V1.0
2 3 V1.0
2 3
2 3
2 3
Figure 16. Selecting versions used in development work
To examine versions that are included in a particular release, use a config spec that uses a label rule to select the versions that were labeled for that release. An example of how to select versions that are included in a release is displayed in Figure 17.
prog.c 0
util.h 0
msg.cat 0 V1.0
lib.c 0
1 V1.0
1 V1.0
2 V1.0
3 4
3 4
3 4
Figure 17. Selecting versions included in a particular release
Setting up a project
When project managers set up projects in base ClearCase, they map files and directories in the product architecture to a set of VOBs (just as project managers
15
map files and directories to components in UCM). For instructions on creating VOBs and populating them with files and directories, see the IBM Rational ClearCase Developing Software Manual. After files and directories are imported into VOBs, the project manager usually applies labels to a set of versions of elements in those VOBs to designate the versions from which development should start.
Planning a branching strategy

When you use base ClearCase, you must use branches to implement parallel development. (UCM uses streams to manage branches for you.) This section provides a simple example of how to define a branching strategy. As you read the section, keep in mind that the possible branching and merging combinations are almost infinite. A project team can work on many branches concurrently. In Figure 18, the main branch represents the integration branch, an r1_port subbranch is a port to a new platform, an r2_beta subbranch contains work for the beta version of the next release, and so on.
opt.c main 0
1 r1_port 2 r2_beta 3 0 1 4 1 2 2 3 3
Figure 18. Branches in a file system directory tree
Using a private branch

At times, you may want to create a private branch based on the project branch. For example, say you want to work on a bug fix without affecting the work that other developers are doing. To do this, choose the version from which you want to start. Then you can create a second config spec for a second view that will create a private branch starting at that version. A private branch is displayed in Figure 19.
16
util.h main 0
3 4 smg_bugfix 0
Figure 19. Working on a private branch
To incorporate your work into the project, merge the changes on your private branch to the project branch. If you decide to abandon your work, do not merge the changes. In either case, when you want to resume your work on the project branch, change your view back to use the project branch view. For more information about creating private branches for development work and merging your work back to the project branch, see the IBM Rational ClearCase Developing Software Manual.
Merging work between branches

To integrate work from one branch with work on another branch, you merge work from one subbranch to another branch. In Figure 20, all work must be merged to the main branch before it can be included in a product release. After the fix on the bug102 branch is tested and approved for integration, you first merge the work to the r1_fix branch. You then test all the work on the r1_fix branch; when that work is ready to be incorporated into the main project, you merge from that branch to the main branch.
17
element: opt.c main 4 r1_fix 5 0 6 1 7 2 8 3 0 4 1 merge 5 2 6

Figure 20. Merging branches
bug102
merge
Creating standardized config specs

To ensure that team members are working on the correct branches (that is, on the appropriate directory and file versions), the project manager can create a standardized config spec that team members use for their views. For more information on creating config specs, see the IBM Rational ClearCase Guide to Managing Software Projects and the IBM Rational ClearCase Developing Software Manual.
Creating labels
A label in base ClearCase is a name that can be attached to a version. Labels are a powerful tool for project managers. By applying labels to groups of elements, the relationship of a set of file and directory versions to one another can be defined and preserved at a given point in the development lifecycle. For example, you could apply a BASELINE label to all versions that are considered stable after integration and testing. You can then use this label as the foundation for new work.
Using metadata to implement policies

In base ClearCase, project managers use metadata to define project policies and to annotate objects in the VOB. Metadata includes the following: v Attributes
18
v v v v v
Branch types Hyperlinks Locks Triggers Labels
Note: You can also use attributes, hyperlinks, locks, and triggers when using UCM. Project managers can use attributes, hyperlinks, and labels to annotate objects in the VOB. The following section provides definitions of attributes, hyperlinks, and labels and gives examples of how they can be used. v Attributes are name-value pairs that are attached to objects. You could use attributes to attach bug numbers to versions. You could also use them to identify which versions in a baseline have been tested. v Hyperlinks connect two VOB objects. For example, you can define a hyperlink to connect a design specification to its associated executable file. v Labels identify specific versions of elements. You can use labels in config spec rules to identify branching points, or to mark all versions that were used in a build. Project managers can use locks and triggers to define and enforce project policies. For example, a project manager could temporarily lock an integration branch to prevent developers from merging work onto it. A project manager could also create a trigger that prompts developers to enter the bug number associated with a checkin and then attaches that bug number to the new, checked-in version. For details about using Rational ClearCase metadata, see the IBM Rational ClearCase Guide to Managing Software Projects and the IBM Rational ClearCase Developing Software Manual.
Integrating base ClearCase with Rational ClearQuest

Rational ClearQuest is a change request management solution. Using Rational ClearQuest, team members can submit change requests for their product, view and modify existing change requests, and create and run user-specific or site-specific queries and reports to determine project status. You can associate change requests with versions of elements using the base ClearCase integration with Rational ClearQuest. Versions associated with a change request constitute a change set. In Rational ClearQuest, a page on the change requests record form displays its change set information. You can specify conditions under which developers are prompted to associate versions with change requests when you configure the integration. For example, you can require developers to specify a change request associated with a given file when they check out or check in that file, and you can apply this requirement only to specific VOBs, branch types, or element types.
Rational ClearCase MultiSite

Rational ClearCase MultiSite extends Rational ClearCase by supporting parallel software development across geographically distributed project teams.
19
Developers at different locations can use Rational ClearCase MultiSite to work on the same VOB, as displayed in Figure 21. Each site has its own copy, or replica, of that VOB. The set of replicas of a particular VOB is called a family. At any time, a site can propagate changes made in its VOB replica to other members of the VOB family, using an automated or manual synchronization process.
peer-to-peer pattern
Boston San Francisco Bangalore
Figure 21. Rational ClearCase MultiSite VOB family
This manual describes Rational ClearCase MultiSite only where it applies to a given Rational ClearCase operation or concept. See the IBM Rational ClearCase MultiSite Administrators Guide for details about configuring, using, and administering Rational ClearCase MultiSite.
20
Chapter 2. Planning for and installing Rational ClearCase

This chapter provides a high-level overview of the Rational ClearCase installation process. It identifies major planning decisions you need to make and summarizes the steps required to install Rational ClearCase. It is not intended to be a complete installation guide. For details about installing Rational ClearCase at your site, see the IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT Installation and Upgrade Guide. If you are a Rational ClearCase administrator who is responsible for installing Rational ClearCase at your site, read this chapter. If you are a project manager, read Planning issues. This section contains information about using UCM, base ClearCase, Rational ClearQuest, and Rational ClearCase MultiSite in your organization. If you need information about installing Rational ClearCase on your client computer, start with Installing Rational ClearCase on individual computers on page 24.
Planning issues
This section describes significant decisions administrators or project managers must make before installing Rational ClearCase.
Using Unified Change Management or base ClearCase

UCM is an optional activity-based process that you can use with Rational ClearCase to implement configuration management. You do not need to have mastered the details of base ClearCase to work in UCM. UCM provides the convenience of a built-in, automated solution; base ClearCase offers the flexibility you need to implement virtually any configuration management solution that is appropriate for your environment. Think of base ClearCase as a feature-rich toolset and UCM as a process, based on recommended software development practices, that uses that toolset. If v v v your team plans to use UCM, you need to make the following decisions: Which components your team will work on What stream hierarchy your project will use Which development policies you will enforce
v What naming scheme you will use for baselines If your team plans to use base ClearCase, you need to make the following decisions: v What branching strategy your team will use v What configuration specification (config spec) rules developers will use so that their views to select particular versions of elements v What label types and labels you will use to identify project milestones
21
For an overview of differences in configuring, working in, and managing software development projects between base ClearCase and UCM, see Chapter 1, Overview of Rational ClearCase, on page 1. For detailed information, see the following sources: v For information about creating and managing projects using UCM or base ClearCase, including details about what you must consider for either environment before you install Rational ClearCase, see the IBM Rational ClearCase Guide to Managing Software Projects. v For information about how UCM or base ClearCase affects how developers work in Rational ClearCase, see the IBM Rational ClearCase Developing Software Manual.
Integrating with Rational ClearQuest

In UCM, you can use Rational ClearQuest to provide additional activity management features to your development environment, such as assigning activities, moving activities through states, and querying and reporting on activities based on state, user assignment, project, and so on. For details about configuring Rational ClearQuest and Rational ClearCase to support activity management using UCM, see the IBM Rational ClearCase Guide to Managing Software Projects. If you are using the base ClearCase integration with Rational ClearQuest instead of UCM, you can associate Rational ClearQuest change requests with Rational ClearCase versions. For details about configuring this integration, see the IBM Rational ClearCase Guide to Managing Software Projects.
Planning to use Rational ClearCase MultiSite

If your team plans to use Rational ClearCase MultiSite, you need to make the following decisions: v Which development artifacts you will share among geographically diverse sites v How developers at various sites will access and change those artifacts v How and when you will synchronize changes among sites For details about planning for use of Rational ClearCase MultiSite, see the IBM Rational ClearCase MultiSite Administrators Guide.
Rational ClearCase site preparation

The Rational ClearCase administrator (possibly with advice from the Rational ClearCase project manager) decides how to configure the Rational ClearCaseinstallation for the site. The administrator creates a shared release area from which users can install Rational ClearCase on their individual computers. When creating the shared release area, the administrator specifies default values for installation parameters that are based on the configuration decisions that have been made for the site. These parameter values will then be used when Rational ClearCase is installed on individual hosts.
Installation requirements
Before you install Rational ClearCase at your site, see the IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT Installation and Upgrade Guide for the following information: v Supported platforms and file systems (including system file access for all supported platforms) v Hardware and software requirements
22
v Platform-specific information relevant to installation, such as disk space required, OS patches required, layered software packages required, and so on v Rational ClearCase and Rational ClearCase MultiSite fix packs incorporated into this release v Information about upgrading from a previous Rational ClearCase release v Known issues relevant to installation
Running site preparation

The Rational ClearCase Site preparation program prepares the shared release area from which users can install Rational ClearCase on their computers. Rational ClearCase Site preparation configures the sitewide defaults that users see when they install Rational ClearCase on their computers. This simplifies sitewide installation because the Rational ClearCase administrator defines Rational ClearCase installation parameters for the site only once, rather than requiring everyone to specify appropriate values for these parameters when they install Rational ClearCase. Instead, users can accept the default parameter values when prompted during the installation process. On Windows, running Rational ClearCase Site preparation requires local administrator privileges and often also requires network administrator privileges. On Linux and the UNIX system, running Rational ClearCase Site preparation requires root privileges. For detailed information about running Rational ClearCase Site preparation, see the IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT Installation and Upgrade Guide.
Installing Rational ClearCase server software

After running the Rational ClearCase Site preparation program, the administrator installs the Rational ClearCase server software on one or more server hosts. Rational ClearCase LT allows you to install the server software on one host only; Rational ClearCase enables you to install it on multiple hosts. In addition to installing Rational ClearCase server software, the installation procedure creates some Rational ClearCase objects, displayed in Table 2, and performs initial configuration to set up your teams development environment.
Table 2. Rational ClearCase objects created by installation procedure Rational ClearCase Object Project Project VOB (PVOB) Component VOB Administrative VOB VOB UCM X X X X X Base ClearCase
In Table 2, the term administrative VOB refers to a VOB that contains global type objects, such as branch types, that are copied to client VOBs when users create instances of the type objects in the client VOBs.
Chapter 2. Planning for and installing Rational ClearCase
23
Installing Rational ClearCase on individual computers

To install Rational ClearCase on your computer, go to the release area created by your Rational ClearCase administrator and run the Rational ClearCase installation program. (On Windows, this is setup.exe; on Linux or the UNIX system, it is install_release.) Typically, you should accept the default installation parameters. Consult your Rational ClearCase administrator before you override any default values. For detailed information about installing Rational ClearCase, see the IBM Rational ClearCase, ClearCase MultiSite, and ClearCase LT Installation and Upgrade Guide.
24
Chapter 3. Working in Rational ClearCase

This chapter describes the main tasks that project managers and developers perform and the tools that they use while working in Rational ClearCase.
Project managers
As a project manager, you are responsible for creating and maintaining the development environment for your team. The tasks that you perform and the tools that you use differ depending on whether you use UCM or base ClearCase.
Using UCM
The primary tool used for managing UCM projects is the Rational ClearCase Project Explorer. The left pane provides a hierarchical view of UCM objects, starting with the project VOB (PVOB). This view displays components, folders, projects, and streams. The right pane displays the contents of the object that you highlight in the left pane. For example, Figure 22 displays activities created in the integration stream.
Exploring ClearCase Projects
File View Tools Help OM_proj1.0_Integration ccase Components OM_projects OM_proj1.0 OM_proj1.0_Integration ktessier_OM_proj1.0 OM_proj2.0 Name ktessier_OM_proj1.0 act for creating test_el2 act1 Owner ktessier ktessier ktessier Created On 08/10/01 12:59:54 PM 08/10/01 04:14:35 PM 08/10/01 03:46:00 PM
For Help, press F1
Figure 22. Rational ClearCase Project Explorer
The Rational ClearCase Project Explorer enables you to do the following: v Create projects, streams, and views v Set development policies v Create and recommend baselines v View baseline histories and compare the contents of baselines with the contents of previous baselines v Deliver to and rebase from streams in other projects
Using base ClearCase

To manage a project in base ClearCase, you must do the following: v Define and implement a branching strategy v Create a standard config spec for developers to use for their views v Create label types and apply them to versions of elements to identify project milestones
25
v Merge versions from one branch to another branch
Linux or the UNIX system

On Linux or the UNIX system, you can perform all Rational ClearCase project managementtasks from the File Browser. To run the File Browser, invoke the xclearcase command.
Windows
Several tools that can help you perform project management tasks are included in Rational ClearCase on Windows: v The Type Explorer can be used to create branch types and label types v The View creation wizard and the VOB creation wizard can be used to create views and VOBs v The Merge Manager can be used to merge versions of elements between branches To run Rational ClearCase, click Start > Programs > IBM Rational > IBM Rational ClearCase To run Rational ClearCase LT, click Start > Programs > IBM Rational > IBM Rational ClearCase LT
Developers working on Windows

As a developer, you are responsible for setting up your work environment, creating and modifying files, and sharing those files with other members of your project team. The tasks you perform differ slightly depending on whether you use UCM or base ClearCase; however, you can use the same user interface for both environments. The Rational ClearCase Explorer, as shown in Figure 23, is the primary tool for developers to use to work in UCM or base ClearCase on Windows.
26
Rational ClearCase Explorer - ktessier_view (Z:\doc\ccase\relnotes)

File View Go Tools Enviorment Help
Name Getting Started UCM ccase 4.2_supplement admin api cc_bugs.fm cc_bugs.xml cc_issues.cclt.fm
Size
Kind
26624 File Ele 2664 File Ele 164864 File Ele
Join Project
Deliver from Stream
Rebase Stream
Project Explorer
Base ClearCase Views Ready Toolbox View: ktessier_view
Figure 23. Rational ClearCase Explorer
The Rational ClearCase Explorer contains three main panes. The Shortcut pane on the left contains shortcuts for UCM, base ClearCase operations, and your views. The UCM page contains shortcuts for the following operations: v Joining a project v Delivering work to a stream v Rebasing your stream with a new baseline v Starting the Project Explorer The Base ClearCase page contains shortcuts for the following operations: v Merging versions of an element v Creating, starting, and removing views v Updating snapshot views v Editing a views properties v Running the Rational ClearCase Reporting wizard After you set a view context, you can use the Folder pane to browse the hierarchy of folders within your VOBs. The Details pane, on the right, displays versions of elements within the folder you select. If you are using UCM, the Folder pane also contains folders for your activities.
Developers working on Linux or the UNIX system

As a developer, you are responsible for setting up your work environment, creating and modifying files, and sharing those files with other members of your project team. The tasks you perform differ slightly depending on whether you use UCM or base ClearCase; however, you can use the same user interface for both environments.
27
The Rational ClearCase File Browser provides you with access to most Rational ClearCase operations. You can run the File Browser by invoking the xclearcase command.
Working in UCM
The Project menu of the File Browser contains selections for the following UCM developer operations: v Joining a project v Delivering work to a stream v Rebasing your stream with a new baseline v Running the Project Explorer
Working in base ClearCase

The View menu of the File Browser contains menu items for creating, setting, and updating your view. The Versions menu contains menu items for checking in and checking out files, comparing versions of elements, and merging versions.
Using cleartool
In addition to GUIs, Rational ClearCase includes a robust command-line interface utility called cleartool. Table 3 lists cleartool commands that are used to perform common Rational ClearCase operations. For more information about cleartool commands, see the IBM Rational ClearCase Command Reference.
Table 3. Frequently used cleartool commands cleartool Command checkin checkout deliver merge mkactivity mkbl mkbrtype, mkbranch mkelem mklbtype, mklabel mkproject mkstream mkview rebase Description Creates a new version of an element Creates a modifiable copy of a version Merges changes from one stream to another stream Combines the contents of two or more versions of files or directories into a new version Creates a UCM activity Creates a baseline Creates a branch type; creates a branch on the version tree of an element Creates a file or directory element Creates a label type; applies a label to versions of elements Creates a UCM project Creates a UCM stream Creates a view Updates your the configuration of a stream with a new set of foundation baselines
28
Using Rational ClearCase integrations with IDEs

Rational ClearCase supports integrations with a variety of interactive development environments (IDEs). This section describes integrations with two IDEs: Microsoft Visual Studio.NET and Rational Application Developer for WebSphere Software.
Microsoft Visual Studio.NET

Developers can use the Rational ClearCase integration with Microsoft Visual Studio.NET to perform all their development tasks from within one user interface. To use this integration, developers add views to the Visual Studio.NET integration and then place their Visual Studio.NET projects under Rational ClearCase source control. Figure 24 shows the ClearCase Front Desk page of the Visual Studio.NET GUI. Developers can use the Front Desk page to set their base ClearCase or UCM view context. In Figure 24, the developer has chosen to work in UCM and has navigated to the ucm_proj1_mydev stream within the ucm_proj1 project. The View Details area displays the view associated with the selected stream. After setting a view context, developers can use the Rational ClearCase Explorer within the Visual Studio.NET GUI to perform Rational ClearCase operations, such as checking out and checking in files and selecting UCM activities to work on.
Microsoft Development Environment [design] - ClearCase Home File Edit View Project Build Debug ClearCase Tools Window Debug Help
ClearCase Explorer Create View
Start Page Join Project
Front Desk Submit Default Change Request Run Query

Rational Developer Network Rational.com
Rational ClearCase
View Details UCM Views Views Change Requests Tools Help ucm_proj1 ucm_proj1_mydev ucm_proj1_myint Open Solution New Project Deliver Rebase
Selected View: UCM Project: UCM Stream: Parent Stream:
ucm_proj1_mydev ucm_proj1 ucm_proj1_mydev ucm_proj1_Integration
VS.NET Projects
Name
Path
Figure 24. Rational ClearCase integration with Visual Studio.NET
Rational Application Developer for WebSphere Software

Developers can use the Rational ClearCase integration with Rational Application Developer for WebSphere Software to access most Rational ClearCase operations from within the Rational Application Developer GUI. As shown in Figure 25, this integration adds a ClearCase menu and toolbar icons to the Application Developer
29
GUI. Developers can set up their integrated environments by associating their Rational ClearCase views with Application Developer workspaces. Developers can then perform Rational ClearCase operations, such as checking out and checking in files, by clicking a toolbar icon or a context menu option or by starting Rational ClearCase Explorer. Icons in the Navigator pane indicate which files are under Rational ClearCase source control and whether they are checked out.
Resource - Eclipse Platform

File Edit Navigate Search Project ClearCase Run Window Help Connect to Rational ClearCase Navigator Set Current Activity . . . Deliver Stream . . . newjava2 [java_Example] newjava.mkelem . . . .classpath .project .project.keep .project.keep Rebase Stream . . . Update View . . . ClearCase Build Run ClearCase Explorer Show Project Checkouts . . . Run Merge Manager Create New View . . . Edit View Properties . . . Start View . . . Outline Stop View . . . An outline is not available. Mount VOB . . . Unmount VOB . . . ClearCase Help Task (1 item)
C
Description The declared package does not . . .
Resource SampleClass
In Folder newjava2/example . . .
Writable
Insert
Figure 25. Rational ClearCase integration with Application Developer
Using the Rational ClearCase Web interface

In addition to its native user interfaces, Rational ClearCase provides a Web interface, shown in Figure 26. Developers can perform the following operations through the Web interface: v Access VOBs v Create views v Add files to source control v Check out and check in files v Compare and merge versions v View properties and histories of elements v Join UCM projects v Deliver work from streams v Rebase their streams with recommended baselines To use the Web interface, developers need only a Web browser; they do not need to install Rational ClearCase on their computers.
30
VOB View of \doc_ctg\nonpii\en-us\clearcase\books\cc_intro - Microsoft Internet Explorer File Edit View Favorites Tools Help
Back Search Favorites Media Go Links
http://www.ctg.rational.com:81/ccase/bin/ccweb.exe?session=3viqXVKxk6hFjQOhw%40GxhnRPTDhge22ii3_o&
Search Web Site popups allowed ClearCase Home Enter VOB Directory: AutoFill Help Options About Logo Out
Documentation
\CLQ_project\install\src
Go
Select View All VOBs \ CLQ_project \ install
Add to ClearCase
Update View
Find Modified Files
Edit View Config
VOB View (Location: C:\ClearCase_Storage\views\nll_view)
Check Out \src Filter: Select All
Check In
Undo Checkout
Undo Hijack
Compare
Merge
Properties Filter
History
Include Select None Name config.java interface.java license.java registry.java Size 97kb 2kb 253 40 Modified 5 Jul 2005 3:21 PM 5 Jul 2005 3:21 PM 5 Jul 2005 3:21 PM 5 Jul 2005 3:21 PM
Exclude
Unfilter
Version \main\9 \main\10 \main\8 \main\8
View: nlum_nll_view
View location: C:\ClearCase_Storage\views\nll_view
Internet
Figure 26. Rational ClearCase Web interface
Using the Rational ClearCase Remote Client

Developers can use the Rational ClearCase Remote Client to access Rational ClearCase from a variety of network connections, including broadband (WAN), dial-up, and local area networks (LANs). The Rational ClearCase Remote Client is available in three forms: v The Rational ClearCase Remote Client standalone interface, which is designed for those who do not work in an integrated development environment. This interface includes: Viewers, such as the Rational ClearCase Navigator and Rational ClearCase Details view, that provide access to resources loaded into Rational ClearCase views and allow you to browse the contents of remote Rational ClearCase repositories Windows that developers can use to perform Rational ClearCase operations such as checkout and checkin Wizards that automate tasks such as joining a UCM project and creating Rational ClearCase views Toolbars and context menus that provide access to windows and wizards v The Rational ClearCase Remote Client for Microsoft Visual Studio.NET, which integrates the Rational ClearCase Remote Client with the Microsoft Visual Studio.NET IDE. v The Rational ClearCase Remote Client for Eclipse, which integrates the Rational ClearCase Remote Client with the Eclipse platform, including IBM Rational Software Development Platform products based on Eclipse. In the Rational ClearCase Remote Client for Eclipse, all Rational ClearCase Remote Client viewers are available in the Rational ClearCase perspective and can also be added to other Eclipse perspectives. Windows and wizards are accessible from Rational ClearCase toolbars (which can be added to any Eclipse perspective that supports a team provider) and the Eclipse Team context menu.
31
For more information about Eclipse, see the Eclipse Web site at http://www.eclipse.org.
32
Glossary A
activity. A Rational ClearCase UCM object that tracks the work required to complete a development task. An activity includes a text headline, which describes the task, and a change set, which identifies all versions that developers create or modify while working on the activity. When working on a version, developers must associate that version with an activity. If your project is configured to use the UCM integration with Rational ClearQuest, a corresponding Rational ClearQuest record stores additional activity information, such as the state and owner of the activity. administrative VOB. A VOB that contains global type objects. Local copies of global type objects can be created in any VOB that has an AdminVOB hyperlink to the administrative VOB that defines the global type object. See also auto-make-type, global type, local copy.
C
change set. A list of related versions associated with a UCM activity. The versions that developers create while working on an activity are recorded. An activity uses a change set to record the versions of files that are delivered, integrated, and released together. checkout/checkin. (1) The two-part process that extends a branch of an elements version tree with a new version. The first part of the process, checkout, expresses your intent to create a new version at the current end of a particular branch. (This is sometimes called checking out a branch.) The second part, checkin, completes the process by creating the new version. (2) For file elements, the checkout process creates an editable version of the file in the view with the same contents as the version at the end of the branch. Typically, a user edits this file, then checks it back in. (3) For directory elements, the checkout process allows file elements, subdirectory elements, and VOB symbolic links to be created, renamed, moved, and deleted. (4) Performing a checkout of a branch does not necessarily guarantee you the right to perform a subsequent checkin. Many users can check out the same branch, as long as they are working in different views. At most one of these can be a reserved checkout, which guarantees the users right to check in a new version. An unreserved checkout does not. If several users have unreserved checkouts on the same branch in different views, the first user to check in creates the next version. ClearCase administrators group. (Windows platforms only) A special group, usually created in the Windows NT domain when Rational ClearCase is installed. Only Rational ClearCase administrative accounts and the login account for the ALBD Service should be members of this group. ClearCase registry. A set of files on the registry server host that map logical VOB and view names (VOB tags and view tags) to physical storage locations (VOB storage directories and view storage directories). component. A Rational ClearCase object that you use to group a set of related directory and file elements within a UCM project. Typically, the elements that make up a component are developed, integrated, and released together. A project must contain at least one component, and it can contain multiple components. Projects can share components. config spec. A set of rules that specify which versions of VOB elements a view selects. The config spec for a
B
baseline. A Rational ClearCase UCM object that typically represents a stable configuration for one or more components. A baseline identifies activities and one version of every element visible in one or more components. Developers can create a development stream or rebase an existing development stream from a baseline. branch. An object that specifies a linear sequence of versions of an element. The entire set of versions of an element is called a version tree; it always has a single main branch and may also have subbranches. Each branch is an instance of a branch type object. build. The process during which a Rational ClearCase build program (clearmake, clearaudit, or omake) produces one or more derived objects. This may involve actual translation of source files and construction of binary files by compilers, linkers, text formatters, and so on. A system build consists of a combination of actual target rebuilds and build avoidance. See also express build. build avoidance. The ability of a Rational ClearCase build program to fulfill a build request by using an existing derived object instead of creating a new one by executing a build script. The build program can reuse a derived object currently in the view or wink in a derived object that exists in another view. The process by which the build program decides how to produce a derived object is called configuration lookup.
33
snapshot view also specifies which elements to load into the view. See also scope, version selector, version-selection rule, and load rule.
access any version of any element, independently of (and overriding) version selection by views. Derived objects also have extended pathnames, which include DO IDs.
D
deliver. A Rational ClearCase operation in which developers merge the work from their own development streams to the projects integration stream or to a feature-specific development stream. If required, the deliver operation invokes the Merge Manager to merge versions. derived object (DO). An MVFS file produced by a clearmake or omake build or a clearaudit session. Each derived object is associated with the configuration record that is created by the Rational ClearCase build program to document the build. A shareable DO can be winked in by other views; a nonshareable DO cannot be winked in unless you explicitly make it available. development stream. A Rational ClearCase UCM object that determines which versions of elements appear in a development view and maintains a list of a developers activities. The development stream configures the development view to select the versions associated with the foundation baselines plus any activities and versions that developers create after they join the project or rebase their development stream. dynamic view. A view that is always current with the VOB (as specified by the config spec). Dynamic views use the MVFS to create and maintain a directory tree that contains versions of VOB elements and view-private files. Dynamic views are not supported on all Rational ClearCase platforms.
F
fire a trigger. The process by which verification is made that the conditions defined in a trigger are satisfied and the associated trigger actions are performed. foundation baseline. A property of a stream. Foundation baselines specify the versions and activities that appear in your view. As part of a rebase operation, foundation baselines of the target stream are replaced with the set of recommended baselines from the source stream.
H
hijacked file. A version in a snapshot view that is modified but not checked out. By default, a non-checked-out version in a snapshot view is given the file attribute of read-only. If you change this attribute and modify the file, you have hijacked the file by taking it out of direct Rational ClearCase control. history. Metadata in a VOB, consisting of event records for that VOBs objects. The history of a file element includes the creation event of the element itself, the creation event of each version of the file, the creation event of each branch, the attributes assigned to the element and/or its versions, the hyperlinks attached to the element and/or its versions, and so on.
E
eclipsed. A VOB object that is not visible because another object with the same name is currently selected by the view. element. An object that encompasses a set of versions, organized into a version tree. element type. A class of versioned file or directory objects. Predefined element types are supported in the Rational ClearCase environment. Users can define additional types that are refinements of the predefined types. When an element is created, it is assigned one of the currently defined element types in its VOB. Each user-defined element type is implemented as a separate VOB object. extended namespace. The Rational ClearCase extension of the standard file system pathname hierarchy. Each host has a view-extended namespace, which allows a pathname to access VOB data using any view that is active on that host. Each VOB has a VOB-extended namespace, which allows a pathname to
L
label. An instance of a label type object, supplying a user-defined name for a version. See also object, metadata. label type. A type object that defines a version label for use within a VOB. load. To copy a version of an element to a snapshot view and keep track of the checkins, updates, and other Rational ClearCase operations that affect the element. load rule. A statement in the config spec that specifies an element or subtree to load into a snapshot view. Config specs can have more than one load rule. See also version-selection rule. lost+found. A subdirectory of a VOBs top-level directory, to which elements are moved if they are no longer cataloged in any version of any directory element.
34
M
main branch. The starting branch of an elements version tree. The default name for this branch is main. master replica. (Rational ClearCase MultiSite) The master replica of a Rational ClearCase object is the only replica at which the object can be modified or instances of the object can be created. mastership. (Rational ClearCase MultiSite) The ability to modify an object or to create instances of a type object. metadata. The data associated with an object that supplements its file system data. Some of this data is created by users; some of it is created during Rational ClearCase operations on the object. multiversion file system (MVFS). A directory tree that, when activated (mounted as a file system of type MVFS), implements a VOB. To standard operating system commands, a VOB appears to contain a directory hierarchy; Rational ClearCase commands can also access the VOBs metadata. Also, MVFS file system refers to a file system extension to the operating system, which provides access to VOB data. The MVFS file system is not supported on all Rational ClearCase platforms.
multiple development streams, which configure views that allow developers to work in isolation from the rest of the project team. project VOB (PVOB). A VOB that stores UCM objects, such as projects, streams, activities, and change sets. Every UCM project must have a PVOB. Multiple projects can share the same PVOB.
R
rebase. A Rational ClearCase operation that makes a development work area current with the set of versions represented by a more recent baseline in another stream, usually the projects integration stream or a feature-specific development stream. replica. (Rational ClearCase MultiSite) An instance of a VOB, located at a particular site. A replica consists of the VOBs database, along with all of the VOBs data containers.
S
scrubbing. The removal of objects that are no longer used to free storage space: v The scrubber utility discards data container files from cleartext pools and derived object storage pools. v The vob_scrubber utility discards event records and Rational ClearCase MultiSiteoplog entries from a VOB database. v The view_scrubber utility removes derived object containers from the view storage directory. snapshot view. A view that contains copies of Rational ClearCase elements and other file system objects in a directory tree. You use the Update Tool to keep the view current with the VOB (as specified by the config spec). stream. A Rational ClearCase UCM object that determines which versions of elements appear in any view configured by that stream. Streams maintain a list of baselines and activities. A project contains one integration stream and typically multiple development streams.
O
object. An item stored in a VOB. An object can be identified by an object-selector string, which includes a prefix that indicates the kind of object, the objects name, and a suffix that indicates the VOB in which the object resides. Examples: lbtype:REL1@/vobs/vega on Linux or the UNIX system and lbtype:REL1@\vega on Windows object registry. A networkwide database that records the storage locations of all VOB storage directories and all view storage directories. The mktag, rmtag, mkview, rmview, mkvob, rmvob, register, and unregister commands add, delete, or modify registry file entries. orphaned element. An element that is no longer cataloged in any version of any directory. Such elements are moved to the VOBs lost+found directory.
T
trigger. A monitor that specifies one or more standard programs or built-in actions to be executed whenever a certain Rational ClearCaseoperation is performed. See also preoperation trigger, postoperation trigger, trigger type. type. An object that defines a Rational ClearCase data structure. Users can create instances of these structures: metadata annotations are placed on objects by creating instances of label types, attribute types, and hyperlink
P
project. A Rational ClearCase UCM object that contains the configuration information needed to manage a significant development effort, such as a product release. A project includes one integration stream, which configures views that select the latest versions of the projects shared elements, and typically
Glossary
35
types. Each file and directory is an instance of an element type; each branch is an instance of a branch type.
actually located in a VOBs derived object storage pool. 2) To convert a nonshareable derived object to a shared derived object.
U
Unified Change Management (UCM). A process, layered on base ClearCase and Rational ClearQuest functionality, for organizing software development teams and their work products. Members of a project team use activities and components to organize their work.
V
version. An object that implements a particular revision of an element. The versions of an element are organized into a version tree structure. Also: checked-out version can refer to the view-private file that corresponds to the object created in a VOB database by the checkout command. version tree. The hierarchical structure in which all the versions of an element are (logically) organized. The version tree display also shows merge operations. view. A Rational ClearCase object that provides a work area for one or more users. For each element in a VOB, a views config spec selects one version from the elements version tree. Each view can also store view-private files and view-private directories, which do not appear in other views. There are two kinds of views: snapshot views and dynamic views. view-private object. A file or directory that exists only in a particular view. View-private objects are not version controlled. VOB (versioned object base). A repository that stores versions of file elements, directory elements, derived objects, and metadata associated with these objects. With Rational ClearCase MultiSite, a VOB can have multiple replicas, at different sites. VOB database. The part of a VOB storage directory in which Rational ClearCase metadata and VOB objects are stored. This area is managed by the database management software embedded in Rational ClearCase. The actual file system data is stored in the VOBs storage pools. VOB family. (Rational ClearCase MultiSite) The set of all replicas of a particular VOB. All the replicas share the same VOB family UUID; each replica has its own VOB replica UUID.
W
wink in. 1) To cause a shareable derived object to appear in a view, even though its file system data is
36
Appendix. Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created
37
programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Department BCFB 20 Maguire Road Lexington, MA 02421 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBMs application programming interfaces. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (c) IBM 2006. Portions of this code are derived from IBM Corp. Sample Programs. (c) Copyright IBM Corp. 2006. All rights reserved. Additional legal notices are described in the legal_information.html file that is included in your Rational software installation. Trademarks
38
ClearCase, ClearCase MultiSite, ClearQuest, and Rational are trademarks of International Business Machines Corporation in the United States, other countries, or both. Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product or service names may be trademarks or service marks of others.
Appendix. Notices
39
40
Index B
branches glossary definition 33 Rational ClearCase (continued) installing on clients 24 installing server software 23 overview 1 planning issues 21 hardware and software requirements 22 site preparation 22 Project manager considerations 25 Rational ClearCase MultiSite 19 user interfaces command-line interface 28 Rational ClearCase Remote Client 31 Rational ClearCase Web interface 30 using base ClearCase 13 integrating with Rational ClearQuest 19 using Unified Change Management (UCM) 5 integrating with Rational ClearQuest 12 working in an IDE 29 Rational ClearCase MultiSite planning issues 22 Rational ClearCase Remote Client 31 Rational ClearCase Web interface 30 Rational ClearCase LT differences from Rational ClearCase 4 VOB (versioned object base) glossary definition 36
C
ccase-home-dir directory xiv Changes since last edition xvii cleartool 28 Command-line interface using cleartool 28 config specs glossary definition 33 conventions, typographical xiv cquest-home-dir directory xiv customer support xv
D
development policies implementing 12
E
eclipsed glossary definition 34 elements glossary definition 34 types glossary definition 34
F
fire a trigger glossary definition 34
S
Summary of changes xvii
T
typographical conventions xiv
H
history glossary definition 34
U
Unified Change Management (UCM) integrating with Rational ClearQuest 12 using 5 using base ClearCase 13 Using base ClearCase integrating with Rational ClearQuest 19
M
MultiSite 19 planning issues 22
N
namespace extended glossary definition 34
V
version control labels types, glossary definition views glossary definition 36 34
R
Rational ClearCase Developer considerations 26 Copyright IBM Corp. 1992, 2006
41
42
Readers Comments Wed Like to Hear from You

ClearCase and ClearCase LT Introduction Version 7.0.0 Publication No. GI11-6360-00 Overall, how satisfied are you with the information in this book? Very Satisfied Overall satisfaction h Satisfied h Neutral h Dissatisfied h Very Dissatisfied h
How satisfied are you that the information in this book is: Very Satisfied Accurate Complete Easy to find Easy to understand Well organized Applicable to your tasks h h h h h h Satisfied h h h h h h Neutral h h h h h h Dissatisfied h h h h h h Very Dissatisfied h h h h h h
Please tell us how we can improve this book:
Thank you for your responses. May we contact you?
h Yes
h No
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you.
Name Company or Organization Phone No.
Address
___________________________________________________________________________________________________
Readers Comments Wed Like to Hear from You

GI11-6360-00
Cut or Fold Along Line
Fold and _ _ _ _ _ _ _ _ _ _Fold and_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Tape _ _ _ _ _ _ _ _ Tape _ _ _ _ do not _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE
IBM Corporation Attn: Dept CZLA 20 Maguire Road Lexington, MA 02421-3112
_________________________________________________________________________________________ Please do not staple Fold and Tape Fold and Tape
GI11-6360-00
Cut or Fold Along Line
Printed in USA
GI11-6360-00

CC Intro

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CC Intro

Hochgeladen von

Copyright:

Verfügbare Formate

Rational ClearCase and ClearCase LT

Rational ClearCase and ClearCase LT

Chapter 2. Planning for and installing Rational ClearCase . . . . . . . . . 21

Summary of changes . . . . . . . . xvii Chapter 1. Overview of Rational ClearCase . . . . . . . . . . . . . . 1

Chapter 3. Working in Rational ClearCase . . . . . . . . . . . . . 25

Glossary . . . . . . . . . . . . . . 33 Appendix. Notices . . . . . . . . . . 37 Index . . . . . . . . . . . . . . . 41

Copyright IBM Corp. 1992, 2006

IBM Rational ClearCase and ClearCase LT: Introduction

Copyright IBM Corp. 1992, 2006

IBM Rational ClearCase and ClearCase LT: Introduction

Copyright IBM Corp. 1992, 2006

IBM Rational ClearCase and ClearCase LT: Introduction

Copyright IBM Corp. 1992, 2006

IBM Rational ClearCase and ClearCase LT: Introduction

About this book

User Roles and the Rational ClearCase Documentation Set

Who should read this book

Copyright IBM Corp. 1992, 2006

Related information Rational ClearCase documentation roadmap

Software Development Developing Software (online help)

Build Management Guide to Building Software OMAKE Guide (Windows platforms)

Guide to Deployment Tracking (Rational ClearCase/Rational ClearQuest)

IBM Rational ClearCase and ClearCase LT: Introduction

Rational ClearCase LT documentation roadmap

Project Management Guide to Managing Software Projects

Developing Software (online documentation)

More Information Command Reference Online documentation Help files

Installation and Upgrade Guide Administrator's Guide

About this book

Rational ClearQuest documentation roadmap

Designer tutorials (See online documentation)

IBM Rational ClearCase and ClearCase LT: Introduction

Contacting IBM Customer Support for Rational software products

Downloading the IBM Support Assistant

IBM Rational ClearCase and ClearCase LT: Introduction

Copyright IBM Corp. 1992, 2006

IBM Rational ClearCase and ClearCase LT: Introduction

Chapter 1. Overview of Rational ClearCase

Benefits of using Rational ClearCase

Basic terminology of Rational ClearCase

Copyright IBM Corp. 1992, 2006

IBM Rational ClearCase and ClearCase LT: Introduction

Figure 2. Storing elements in a versioned object base (VOB)

Checking out the version

Checking in the version

Chapter 1. Overview of Rational ClearCase

Name View Activities (UCM only)

Versions of file elements

Versions of directory elements

Figure 4. Using a view to see shared elements

Differences between Rational ClearCase and Rational ClearCase LT

IBM Rational ClearCase and ClearCase LT: Introduction

Using Unified Change Management

Chapter 1. Overview of Rational ClearCase

Fixing bug 2144 Creator: pat lib.c, version 4 prog.c, version 5

Headline Activity creator Change set

Fixing bug 2144 l prog.c, version 5 l lib.c, version 4

IBM Rational ClearCase and ClearCase LT: Introduction

Chapter 1. Overview of Rational ClearCase

Baseline Baseline BL2

Figure 8. Composite baseline

IBM Rational ClearCase and ClearCase LT: Introduction