The Base ClearCase Process

Here is the process of the Base ClearCase,

1. Project managers setup the project environment. The project environment setup including

• Create and populate the VOBs.
• Define the branching strategy. A typical branching strategy is to create an integration branch and multiple development branches. Developers do their work on development branches and then merge their changes to the integration branch so other team members can see them
• Create shared views and standard config specs. Based on the branch strategy, project managers will create shared view attached the branch to let the developers to work.
• Make recommendations for view names.

2. Project managers implement development policies

• Define Labels. A label is a user-defined name that can be attached to a version.
• Define Attributes. Attributes are name/value pairs that let you capture information about the state of a version from various perspectives.
• User Hyperlinks. Hyperlinks let you identify and preserve relationships between elements in one or more VOBs.
• Use Triggers. Triggers let you control the behavior of cleartool commands and ClearCase operations by running a specific program or executable script before or after the command runs.
• Use Locks. A lock on an object prevents all developers from modifying it.

3. Define global types. This facility makes it easy to ensure that the branch, label,attribute,hyperlink, and elements types the global types need are present in all the VOBs your project uses.

4. Establish a merging policy.

5. Development is ongoing.

6. Developers merge work to the integration branch

7. Integrators build the product.

8. Project managers labels the source files.

9. Developers merge the labeled sources to their development branches.

 

    

ClearCase UCM Process

In a UCM project, work typically progresses as follows,

1. ClearCase administrators create the VOBs
    VOB means Versioned Object Base. VOB contains all the files and directories.

2. Project Managers create the UCM projects
    UCM includes VOBs and Components. Components is a group of related direcotry and file elements with same baseline.

3. Developers join the UCM project

4. Development is ongoing.
    Developers are assigned to activities to check-out and check-in the source code

5. Developers delivery work to shared work area
    Before delivery to integration stream, developers should test and build their work in the private area.

6. Integrators build the product in shared work area

7. Project managers craete new baselines

8. Project managers promote the specific baselines(Build,Test,Released) to reflect a particular project milestone.
   After the new baseline passes a sufficient testing, project managers designate them as the recommended set of baselines

9. Developers adjust their private work areas to the latest avaiable baselines

Rename Clan Name

Here is the article for clan rename from IBM tech note

http://publib.boulder.ibm.com/infocenter/cqhelp/v7r0m1/index.jsp?rcss=isacq&topic=/com.ibm.rational.clearquest.ms_admin.doc/c_rename_db_replica.htm

Move Shipping Server From One Host to Another

Move Shipping Server From One Host to Another

Assume we have a CQ multisite and now we want to move the shipping server for site Q3 in OL clan from qatest03 to zha-qalab02, here are the steps,

1. In site Q3, run the below command
       multiutil chreplica -cl OL -site Q3 -u admin -p adminpwd -hostname zha-qalab02 Q3
2. Run the sync jobs to sync the updated shipping server to all sibling sites.

If need to update shipping server in multiple sites, updated the site name, new shipping server host and run the above steps.

"Not Associated with a trusted SQL Server Connection" Error Solution

"Not Associated with a trusted SQL Server Connection"  Error Solutin

When users create schema repository with MSSQL server in ClearQuest Maintainence Tool, he/she may meet the error message as below,

Connection failed:
SQL Server Error: Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'username'. Reason: Not associated with a trusted SQL Server connection

Here is the solution
http://www-1.ibm.com/support/docview.wss?uid=swg21119906

The key point is to set the authentication to mixed mode (SQL Server and Windows Authentication Mode)

Schema DB or User DB move error when destination DB is SQL2005

Schema Repository could not be created with SQL Server 2005

When move schema db and user db from SQL2000 to SQL2005, may meet error as below,

SQLExecDirect: RETCODE=-1, State=37000, Native Error=-3504 SQL statement='select from master_global' [Microsoft][ODBC Microsoft Access Driver]The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect.

Here is the solution provided by IBM,
http://www-1.ibm.com/support/docview.wss?uid=swg21239777

Move Schema Repository or User DB

Move Schema Repository or User DB

We can use the ClearQuest tool to move the schema/user db to another physical db (same vendor or different vendor). Here are the details

Using ClearQuest Maintenance Tool to move the schema db and CQ designer for user db. Before start, new empty db should be created accordingly. Click menu Move under Schema Repository in CQ Maintenance Tool to move schema db. Click Move User Database under Database in CQ Designer to move user database. It is easy to do and understand with the action wizard except following attentions,

1.  The moved db(s) should be empty. If the db has the replica of the user db or schema db, you can use Update function in CQ designer and CQ Maintenance Tool.

2.  Notify all users logoff the user db
3.  Backup all schema db and user dbs for uncertain things happened.
4.  Export the updated connection file to other site and import the file if multisite.
5.  Moving schema db and user db do not change the oplog.