Managing change and releases Learn how to manage change and release in the product. Managing software projects Workflow for creating projects Workflow for making baselines Workflow for recommending baselines IBM Rational® ClearCase® Guide to Building Software (Linux/UNIX) IBM Rational ClearCase Guide to Building Software (Windows)Managing software projectsManaging software projectsAbout the project manager and project integrator helpCreating the directory structureAssociating child activity records with a parent activity recordAssigning state types to the states of a record typeSetting up the base ClearCase integration with Rational ClearQuestAbout integrating changesAdding Rational ClearCase definitions to a Rational ClearQuest schemaThe construct_version method source codeCreating and using a test elementAbout Diff MergeCreating a new type managerCreating a test element typeOther applications of element typesProcessing files by element typeElement types and type managersUsing element types to configure a viewWriting a type manager program (Linux or the UNIX system)Exit status of a type manager methodAbout element types and file processingFile types in a typical projectHow element types are assignedIcon use by GUI browsersPredefined and user-defined element typesPredefined and user-defined type managersHow merging worksInstalling triggers in a VOB on Linux and the UNIX systemSetting policies and installing triggers in a Rational ClearCase VOBCommon merge scenariosAll project work isolated on a branchAll project work isolated in a viewUsing the command line to merge elementsMerging directory versionsMerging all project workAbout the Merge ManagerMerging a new release of an entire source treeUsing the GUI to merge elementsUsing other merge toolsRemoving the contributions of some versionsSelective merge from a subbranchThe construct_version methodThe create_version methodUsing different paths or different scriptsUsing the same scriptType manager for manual page source filesCreating the type manager directoryImplementing a new compare methodInheriting methods from another type managerScript for compare methodTesting the type managerAbout the Version Tree BrowserEnabling and disabling automatic associationsUsing automatic associationsHandling an incomplete postingRequesting confirmation of batch completionAbout code page conversionConfiguration parameters for code page conversionThe integration code page conversion processThe contents of the configuration fileChecklist of configuration stepsConfiguration file use and formatLocating the configuration fileOverview of the configuration fileSummary of configuration parametersUsing a shared configuration file and triggersConnecting Rational ClearCase clients and a Rational ClearQuest user databasePolicy regarding customization and supportDefining the Rational ClearQuest user database and database setDebugging and analyzing operationsGenerating operational informationControlling logged outputProducing timing informationDefining a batchEditing the configuration fileEstablishing the Rational ClearQuest Web interfaceAbout locally stored informationAbout the Integration Query wizardEstablishing Rational ClearCase MultiSite supportOverview of the base ClearCase integration with Rational ClearQuestAbout the configuration fileHow the integration worksAbout the integration packageAbout enabling a VOB and installing triggersWhat the integration doesEnhancing performanceCustomizing the integrationPlanning for the base ClearCase integration with Rational ClearQuestForcing checkin success before committing associationsAllowing use of the graphic user interface (GUI)Allowing multiple associationsControlling query usageMaking policy choicesUsing the association batch featureControlling and using automatic associationsSpecifying associations in comment patternsQuick start for evaluationsQuery supportEstablishing the schemasOverview of DefineCQSchemaSharing a CQSchemaSetting up the Rational ClearQuest user database for base ClearCaseTesting the integrationTesting the configured connectionsTroubleshooting the configured connectionsTuning automatic association featuresAbout trigger versionsAbout defining project viewsConfig spec include filesDefining project viewsDefault config specHow config specs workProject environment for sample config specsThe standard configuration rulesOmitting the standard configuration rulesViews for project buildsView that uses results of a nightly buildVariations that select versions of project librariesView that selects versions that built a particular programConfiguring the makefileFixing bugs in the programSelecting versions that built a set of programsView that selects versions of application subsystemsViews for project developmentView to implement multiple-level branchingView to modify an old configurationOmitting the /main/LATEST ruleVariation that uses a time ruleView for new development on a branchView to restrict changes to a single directoryView that uses a time ruleSharing config specs among Linux, the UNIX system, and the Windows systemConfig spec compilationPaths in config spec element rulesPath separatorsPitfalls for development of using attributes to select versionsHistorical view defined by a version labelHistorical view defined by a time ruleView that shows changes of one developerViews to monitor project statusView that uses attributes to select versionsComparing baselinesAbout building componentsBuilding and testing the componentsIntegrating changesAbout base Rational ClearCase project managementBranches and Rational ClearCase MultiSiteBranch namesManaging projects in base ClearCaseCreating and populating VOBsCreating shared views and standard config specsUsing attributes, hyperlinks, triggers, and locksGlobal typesGenerating reportsUsing labelsImplementing development policiesIntegrating changesPlanning a branching strategySetting up the projectRecommendations for view namesAbout using Rational ClearCase throughout the development cycleUsing Rational ClearCase throughout the development cycleIntegration and testCreating baseline 1Creating Baseline 2Final validation: creating Release 2.0Development beginsCreating branch typesCreating, configuring, and registering viewsCreating standard config specsCreating project viewsProject manager and Rational ClearCase administratorDevelopment strategyUse of branchesFixing a final bugTechniques for isolating your workLabeling sourcesLabeling sourcesDecommissioning the major branchRestricting use of the main branchMerging from the major branchMerging from the r1_fix branchIntegration and testMerging ongoing development workPreparing to merge from the major branchMerging two branchesMerging workProject overviewRebuilding from labelsRemoving the integration viewSetting up the test viewWrapping up the projectAbout implementing project development policiesAssociate changes with change ordersAssociate project requirements with source filesImplementing project development policiesDeny access to project data when necessaryGood documentation of changes is requiredIsolate work on release bugs to a branchLabel all versions used in key configurationsAvoid disrupting the work of other developersNotify team members of relevant changesPrevent use of certain commandsCertain branches are shared among Rational ClearCase MultiSite sitesSharing triggers among different types of platformAll source files must meet project standardsAll source files require a progress indicatorRational ClearCase integrations with Rational ClearQuestManaging coexisting integrationsPresentationSchema usage with both integrationsUnderstanding the Rational ClearCase integrations with Rational ClearQuestBranching and creating viewsUsing components to organize filesCreating and using baselinesDifferences between UCM and base ClearCaseManaging activitiesEnforcing development policiesChoosing between UCM and base ClearCaseAbout the Compare Baselines windowCreating and maintaining credentials for Rational ClearQuest database setsAbout creating feature-specific development streamsCreating a feature-specific development streamAbout deleting activitiesAbout deleting baselinesAbout deleting componentsAbout deleting projectsAbout deleting streamsDescription specificationUndoing a deliver operationFixing problems in baselinesFields specificationHelp filesInterface specification for All_Views.prlImporting directories and files from outside Rational ClearCase version controlLocking the shared streamLocking and making obsolete the project and streamsAbout making a baselineMaking baselines of newly populated componentsParameter choosersParameters specificationBootstrap projectsComposite baselines in component-oriented projectsComponent-oriented ProjectsRelease-oriented projectsE-mail notification postoperation trigger scriptRightclick specificationUsing Rational ClearCase Reports (Windows systems only)Configuring shared report directoriesCustomizing Rational ClearCase ReportsDefault directory structure for Rational ClearCase ReportsDate/time chooserExample 1: Adding a column to report outputInterface specificationModified report procedureProcessing logicExample 2: changing directory organization, description, and outputInterface specificationModified report procedureProcessing logicExample 3: changing description, parameter types, and outputInterface specificationModified report procedureProcessing logicExample 4: changing the pop-up menu for right-click handlingChanges requiredInterface specificationModified report procedureExample 5: adding a new command to Report Viewer pop-up menuInterface specificationModified report procedurefield_type conventionsHow Rational ClearCase Reports worksPopulating the Report Builder tree panePath chooserReport Procedure interface specificationsReport programming examplesRun-time processing sequence for Reports programming interfaceSaving report dataTroubleshooting customizationErrors in the interface specificationText chooserType chooserUCM targets chooserViewing the reportWhat you can customize in Rational ClearCase ReportsE-mail notification setup scriptTips for sharing scriptsAdding UCM support to an existing schemaSetting up a Rational ClearQuest user database for UCMCreating users and adding credentialsUsing parent and child controlsSetting the environment (Linux and the UNIX system)Customizing Rational ClearQuest project policiesRequirements for enabling custom record typesState transition default action requirements for record typesUpgrading your schema to the latest UCM packageSetting state typesAbout setting up a Rational ClearQuest user databaseQueries in a Rational ClearQuest schema enabled for UCMSchema enabled for UCMState typesCreating and setting an activity in the integration stream (Linux and the UNIX system only)Adding componentsResolving baseline conflictsCreating a new baselineMonitoring project statusAbout managing a projectRecommending the baselineTesting the baselineViewing baseline historiesBuilding componentsCleaning up the projectQuerying Rational ClearQuest user databasesFinding work that is ready to be deliveredRemoving unused objectsRebasing the test development streamAssociating UCM and Rational ClearQuest objectsAfter making a baselineComposite baselinesMaking a baselineRecommended baselinesBaselines and streamsBaselines and their usesUnderstanding UCMBuilding componentsCreating the projectCreating a PVOBRational ClearCase MultiSite considerationOrganizing directories and files into componentsSetting policiesSingle-stream projectsAdvance rebase operationsDirections of rebase operationsOverview of the UCM integration with Rational ClearQuestSetting up the UCM integration with Rational ClearQuestCreating a testing streamStream hierarchiesAssigning workShared and private work areasAmount of integrationCreation of composite baseline descendantsIdentifying the initial baselineMaking a new descendant baselineDefining a baseline naming conventionOngoing baselinesChanging to a pure composite baselineDependency relationships in pure composite baselinesSpecifying a baseline strategyWhether to use pure composite baselinesIdentifying a project baselinePlanning the projectIdentifying additional componentsOrganizing componentsIdentifying read-only componentsSimplify a deliver operation with a rebase operationDefining the directory structureDefining the scope of element typesIntegration requirement for Rational ClearQuest MultiSiteRational ClearQuest MultiSite requirementMapping components to projectsMapping system architecture to componentsOverview of the UnifiedChangeManagement schemaIdentifying promotion levels to reflect state of developmentUsing the system architecture as the starting pointThe basic multiple-stream projectSingle-stream projectsNeed for parallel releasesPlanning PVOBsDeciding how many PVOBs to useMapping PVOBs to Rational ClearQuest user databasesEnabling a schema for UCMDeciding which schema to useSharing changes by a deliver operationSharing changes by a rebase operationPlanning how to use the UCM integration with Rational ClearQuestAlternate targets in the same projectStream configurations and baseline contentsDevelopment stream configurationsStream hierarchiesStream hierarchy and default targetsThe integration stream configurationStream relationshipsRead-only streamsCoordinating development streams in the same projectChoosing a stream strategyAlternate target streamsUnderstanding the role of the administrative VOBDeciding how many VOBs to useDeciding what to place under version controlPerform ClearQuest action after changing activityPerform ClearQuest action before changing activityTransition to complete after changing activitySetting policiesModifiable componentsPerform ClearQuest action after deliveryPerform ClearQuest action before deliveryDeliver changes from the foundation in addition to changes from the streamAllow interproject deliver to project or streamAllow deliveries that contain changes to missing or non-modifiable componentsPolicies for deliver operations to nondefault targetsRequire that all source components are visible in the target streamDo not allow deliver to proceed with checkouts in the development streamPolicies and interproject deliveriesDefault promotion level for recommending baselinesAllow all users to modify the projectRebase before deliveryAllow all users to modify the stream and its baselinesTransfer ClearQuest mastership after deliveryTransfer ClearQuest mastership before deliveryTransition to complete after deliveryAssigning activitiesCapturing final baselines in a composite baselineCreating the dependency relationships for composite baselines in the projectMaking a baseline from a labelSetting a baseline naming templateSetting up the projectCreating components for storing baseline dependenciesCreating components for storing elementsMaking components from existing VOBsCreating the projectCreating a project based on an existing Rational ClearCase configurationCreating a project based on an existing projectCreating a project from scratchCreating the projectCreating the project from another projectCreating an integration viewCreating an integration viewDisabling the link between a project and a Rational ClearQuest user databaseFixing projects that contain linked and unlinked activitiesDetecting unlinked activitiesCorrecting unlinked activitiesDefining promotion levelsCreating the project VOBCreating the PVOB from an existing Rational ClearCase configurationAbout setting up the projectMigrating activitiesChanging the project to a different Rational ClearQuest user databaseEnabling use of the UCM integration with Rational ClearQuestSetting project policiesCreating a development stream for testing baselinesWorking with IBM Rational Suite (Windows)Sharing baselines between sibling streams in different projectsManaging multiple projectsComposite baselines in release-oriented projectsUsing a mainline projectMerging from a project to a non-UCM branchDelivering work from an integration stream to another projectAbout managing multiple projectsManaging a current project and a follow-on project simultaneouslyIncorporating a patch release into a new version of the projectProject usesMigrating unfinished work to a follow-on projectMixing project organizationsUsing attributes with triggersUsing triggers to enforce UCM development policiesDelivery setup scriptDo not allow activities to be created on the integration streamOverview of triggersPreoperation and postoperation triggersDelivery preoperation trigger scriptDelivery postoperation trigger scriptScope of triggersEnforce serial deliver operationsSend mail to developers on deliver operationsSupported triggersWhen to use Rational ClearQuest scripts instead of UCM triggersConflicts between composite baselinesConflicts between a composite baseline and an ordinary baselineUse of multiple user databasesFinishing the project configurationIdentifying special element typesUsing mergetype to manage merge behaviorDependency relationships in composite baselines of ordinary componentsPure composite baselinesPolicies for the UCM integration with Rational ClearQuestComponents and baselines policiesComponent modifiability and visibilityDefault view typesPolicies for all deliver operationsPermissions to modify projects and streamsNaming projects that are linked to same user databaseRecommending a baseline for new componentsFor changing activitiesPerform ClearQuest action before work onFor deliveryDisallow submitting records from ClearCase clientAllowed record typesFor submitting records from a Rational ClearCase clientFor WorkOnUsing the predefined UCM-enabled schemasStarting from a baselineElement relocationOverview of the UCM processMonitoring project statusThe rebase operationLateral rebase operationsRevert rebase operationsSummary of rules for rebasing a streamRecommending the baselineMultiple PVOBs and a common administrative VOBMultiple PVOBs and feature levelsPlanning how to test baselinesWhen to create baselinesUsing multiple PVOBsLinking activities to Rational ClearQuest recordsTransferring mastership of the projectChanging the project nameChanging project policy settingsHow the UCM integration with Rational ClearQuest is affected by Rational ClearQuest MultiSiteReplica and naming requirementsAdditional uses for UCM triggersImplementing a role-based access control systemRole-based preoperation trigger scriptUsing different paths or different scriptsUsing the same scriptSharing triggers among different types of platformBranches and streamsMoving from view profiles to UCMCheckpoints and baselinesFeature comparisonMoving view profile information to UCMMoving work among branches or streamsPreparing your view profile projectVOBs and componentsView profiles and UCMChangeFieldMapCQCC_QUERY_ENABLECQCC_QUERY_FILTERDefineCQSchemaSetQuerySetResultSetTo add a component to a streamTo add a directory element to a component (Linux and the UNIX system)To add a directory element to a component (Windows)To add Rational ClearCase definitions to and upgrade a Rational ClearQuest schemaTo start Diff MergeTo start the Rational ClearQuest Integration Configuration toolTo start the Merge ManagerTo install and use the type managerTo start the Version Tree BrowserTo start the Integration Query wizardTo list triggers installed in a VOBTo specify multiple record typesTo reconfigure your view with the modified config specTo compare two baselinesTo compare baselines in Component Tree BrowserTo prepare to mergeSetting up the trigger to monitor bug-fixingTo change a baseline promotion levelTo complete remote deliver operations for a development streamTo create a composite baselineTo create Rational ClearQuest user account profilesTo delete an unused objectTo deliver work between integration streamsTo find all deliver operations that are in the posted stateTo edit the view load rulesTo fix a problem in a new baselineTo lock a streamTo view baseline history (Linux and the UNIX system)To map record states to state typesTo make a component modifiable within the projectTo modify the behavior of a policyTo enable a schema to work with UCMTo rebase the development streamTo rebase an integration stream to baselines of another projectTo recommend a baseline or set of baselinesTo add a column of report outputTo add report procedures to source controlTo change report conditions and add to outputTo change reports for parametersTo add a new command to reportsTo set the Report Builder to the customized directoryTo set default actions for statesTo synchronize a child stream with project modifiable componentsTo synchronize a view with a new configurationTo synchronize a child stream view with new parent stream configurationTo attach triggers to existing elementsTo upgrade the schemaTo view baseline history (Windows)To make a baselineTo make a baseline of one componentTo make new baselines for all components in the streamTo make a baseline for a set of activitiesTo test in a separate development streamTo lock and hide an objectTo see objects that are obsoleteTo create and assign activities in a Rational ClearQuest user databaseTo create and set an activityTo create a baseline by label typeTo set a baseline naming templateTo create a pure composite baseline from existing approved baselinesTo set policies from the Rational ClearQuest clientTo start a Rational ClearQuest clientTo create a projectTo create a project based on an existing projectTo create an integration viewTo disable the project and user database linkTo link unlinked activities at a remote siteTo make a directory tree within a VOB into a componentTo define the promotion levels that your project usesTo create a PVOBTo create a PVOBTo migrate source files into a componentTo enable a project to work with a Rational ClearQuest user databaseTo determine policies in Rational ClearCase controlTo create a feature-specific development streamTo create a development streamTo make a VOB into a componentTo create a component and store it in the VOBTo create a multiple-component VOBTo start the VOB Creation Wizard (the Windows system)To create a multiple-component VOB (Linux and the UNIX system)To create one component per VOB (Linux and the UNIX system)To create one component per VOB (Windows)To start the VOB Creation Wizard (the Windows system)To start Project ExplorerTo set up a Rational ClearQuest user database to work with UCMTo create a component without a VOB root directoryTo relocate elementsTo unlock the streamMoving the view profile informationWorkflow for creating projectsWorkflow for making baselinesWorkflow for recommending baselinesRational ClearCase Guide to building softwareRational ClearCase Guide to building software