Comments below:

theju wrote:

Following (first 3 points below) are mentioned in the CC Connector
online help:

1)CC connector can't be installed on CC server?
Theju>> Why is this? I have CC connector on a CC server and it
still works!

In which doc section did you find this? Installing the CC connector on
a CC server is a good place to install it, so you did the right thing.
You want the CC connector to be installed wherever it has fastest access
to ClearCase. And it's a configuration that gets lots of testing, since
that's what I do for all my demos (where I have everything running on
one machine).

2)cleartool (C:\Program Files\IBM\RationalSDLC\ClearCase\bin) and
ratlperl (C:\Program Files\IBM\RationalSDLC\common) executables
should be in the default path.
Theju>> What if they are in different locations. Where do I tell
the CC connector to pick up the cleartool and ratlperl?

Set your path environment variable to include the directories where they
live.

3)Because time-based rules are used when synchronizing with base
Rational ClearCase, the synchronization host and the VOB server hosts
it accesses should use a common time source if the ClearCase
Synchronized Stream includes files and folders from base Rational
ClearCase.

Theju>>Which time-based rules? Is it something internally stored
the last successful run?

Yes.

4)What is the relation between merge workspace and clone workspace?
Theju>> Why do clone workspace required? Is merge workspace
alone not enough to resolve the sync merge conflicts?

The CLONE workspace and the INTERNAL workspace are private workspaces
used to remember the last configurations that were successfully sync'ed
with ClearCase. So you should follow the guidance in the on-line doc,
and just ignore them (and never try to modify or do anything with them).

In contrast, the "merge workspace" is owned by the developer, and is
just provided as a convenience to give you a standard workspace to
resolve merge conflicts that result from the sync (in particular it is
set up with the right flow targets, which happen to be the Jazz stream
and the CLONE workspace).

5)Why do I sometimes get - "Synchronization exception: Runtime
Error" while syncing?

Can someone please shed some light on this?

That means a bug was encountered during the sync. Please submit a
workitem with the logs from the sync run (minimally there should be two
.... one log with the events from the sync run, and another with the
stack trace for the exception.

Cheers,
Geoff