Connect windows VOBs from solaris: Clear Case

Not sure whether this is will be a everyday requirement, but this one popped in front us some time back. Like all other things we kept this so called idea on the shelf and kept watching. At last we decided to try this out so that we can implement this setup. Rolled up our sleeves and got it to action

First downloaded the clear case solaris installation passport advantage. Download the clear case as per our requirement check before downloading whether it's for Intel (X86) or for SPARC.
After downloading copy those file to target machine where installation needs to be done.
Make sure you have enough space on the target machine (preferably free space 2GB)
Check whether you have root user access before starting the installation
From the downloaded installation copy you will find cc_ms_install.pdf keep that open you might need that for reference and Google at standby ;-)
We followed this technote which worked
Add the machine name and IP in the hosts file in both the machines (UNIX & windows vice versa) to identify in the network

Installation

Run the site_prep script which will prepare the environment before installation, will ask about the registry server and license server.
Note: The registry & License server should be common one for windows for Linux
Enter the details which you know, skip the other details or confirm it twice before entering.
After that completion of script run install_script file for installing actual clear case
Select standard installation, since you have already entered the necessary data in site_prep it will ask for confirmation. So keep going

Clear Case Setup

Create a UNIX region in solaris machine using the clear case command for creating region
After region creation, make sure the region created is visible on windows machine & solaris machine
Here After follow whatever given in the article which you have opened
Create the UNIX snapshot view (check the article)
Create the VOB tag for the UNIX region (check the article)
Load the VOB

Pitfalls

While creating snapshot view, check the option carefully there is value "-tmode strip_cr" which will make your files loading will be slow and may not load some of the files which are not compatible to UNIX.
Loading the VOB, if you loading ends up only top level folder, follow this
Here is small trick if you follow the article the clear case will be loaded but only the top level folders will be loaded., You are correct this behaviour is not common if you face this. We have a solution. create a snapshot view in windows using that view open the edcs, copy the contents in that and use the same in your UNIX machine. There goes all your files will start loading.

I'm not a SCM guy and many thanks to subbu who ran the show and for PS & naveen for helping and guiding to make this happen.

There was not enough material on this topic, so thought of my 2 cents contributions to the SCM community. ... :-)

WID+ClearCase (Killer Combination)

Yes exactly its a Killer Combination WID+Clearcase (WebSphere Integeration Developer+ClearCase). It can easily take away all of your development time by making some wild assumptions !!!!. I think when these guys get togther they have AI (Artifical Inteligence) or the Seventh Sense. My God ... no even god can't save you. We have been using this combination WID+Clearcase for the past two years.In a way its good b'coz its good CM(Configuration Management) tool.


For us it started with one fine day, when i started my machine and opened my WID did a clean Build (Alt+p+n). I see hell lot of errors. I got scared b'coz we were in middle of our testing cycle. I started checking am i the culprit. All the error was leading to XSD file. when i opened the file it had .............. I am not adding etc.. dots here guys. Its the dot(.) character i see at the end of the file. Hurray i can find who did this checked in clearcase about the history no one has edited the file from the creation date. I got confused and deleting the unwanted character did Alt+p+n.

Everything was normal. Couple of days gone, the monster returns back this time not only in machine space, couple of other machines too faced but with different files. S...t i had this bug did the same thing and cleaned it. From that day still we are getting this issue. Earlier it was only on XSD file It has grown and it managed to spread to .java, .mon , .bpel, .import, .sca module ...... yes all the project files.

One improvement with the issue, it started adding some other characters other than dot to the file. But it has been consistent it adds only at the last

The only solution for this is to checkout the file delete the character and check in again. we have raised a PMR a longgggggggg back. IBM as usual started asking all the log files and their list of documents. We have provided them but they say they are not able reproduce this.

Hope they never. So the only solution is the above one.

Its weekend guys enjoy.... take a break from work ....